Skip to main content
LiveChat logo

Is LiveChat Down?

No — LiveChat is up
LiveChat's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 7 of 7 regions · 864 ms

Right now

The verdict is the worse of these two. How we decide

LiveChat's status page

status.livechat.com · read · checked every 3 minutes

Operational
LiveChat's components, as its status page reports them
ComponentStatus
Chat widgetOperational
Agent appsOperational
APIOperational
IntegrationsOperational
Support chat on www.livechat.comOperational
Subprocessors' serviceOperational
Open their status page

FlareWarden checks

accounts.livechat.com from 7 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
7 of 7
Response
864 ms
Checked

By region

  • Amsterdam reachable, 2294 ms
  • Chicago reachable, 288 ms
  • San Jose reachable, 823 ms
  • Singapore reachable, 533 ms
  • Stockholm reachable, 645 ms
  • Tokyo reachable, 1078 ms
  • Toronto reachable, 393 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam675 ms106 ms216 ms2294 ms
Chicago25 ms2 ms7 ms287 ms
San Jose104 ms46 ms96 ms823 ms
Singapore76 ms2 ms7 ms533 ms
Stockholm239 ms1 ms5 ms645 ms
Tokyo296 ms1 ms6 ms1078 ms
Toronto82 ms13 ms31 ms393 ms
We check that accounts.livechat.com loads, not every feature behind it. Test it yourself

History

Incidents LiveChat reported

Since Oct 22, 15 days · from status.livechat.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

LiveChat website availability

Measured by FlareWarden · accounts.livechat.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
742ms

Last 30 days

71-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 31 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 30 checks
Oct 18: 100.00% uptime, 30 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 31 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 31 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 30 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 30 checks
Nov 4: 100.00% uptime, 29 checks
Nov 5: 100.00% uptime, 30 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of accounts.livechat.com from multiple regions every 6 hours. LiveChat's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What LiveChat does

LiveChat is a hosted customer messaging product. A JavaScript widget embedded on a company's website opens a chat window for visitors, and agents answer from a web or desktop app. Retailers and software companies use it as the front door for pre-sales questions and support, which puts it directly on the critical path of their own sites.

What an outage looks like

The chat bubble never appears on your website, or it appears and shows a spinner that never resolves. Agents find the app stuck on connecting, or see conversations that will not open. Visitors who do send a message get no reply because it never reached an agent queue. Integrations that push transcripts into a CRM or helpdesk stop firing.

What to do about it

Check status.livechat.com, which reports Chat widget, Agent apps, API and Integrations as separate components: the widget failing while agent apps are healthy is a different incident from the reverse. If the widget is the affected component, put a visible fallback such as an email address or phone number on your site, since visitors otherwise meet a broken control and leave without telling you.

Is it down for everyone, or just you?

If this page says LiveChat is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Intercom
Intercom
Zendesk
Zendesk
Front
Front
Help Scout
Help Scout

LiveChat outage FAQ

Is LiveChat down for everyone or just my site?
LiveChat's status page reports global component health, so an operational Chat widget component while your site shows no bubble usually points at your own page: a blocked script, a content security policy rule, or an ad blocker in the visitor's browser. The multi-region measurement above tests LiveChat's own hosts, which separates those two cases.
Can visitors still reach us when the chat widget is down?
Not through chat. A widget outage is silent from the visitor's side, since they see a control that does not work and most leave rather than hunt for another channel. That is why a LiveChat incident costs more than the outage window suggests, and why an email address or phone number visible without the widget is worth keeping on the page.
Do we lose messages sent during an outage?
It depends which component failed. A Chat widget failure means the visitor's message was never sent at all, so there is nothing queued anywhere to recover. An Agent apps incident is different: messages can reach LiveChat and wait in a queue that agents temporarily cannot open, and those are still there when the app recovers.
Why does LiveChat list a Subprocessors' service component?
Because it depends on outside vendors and tracks them where customers can see it. That component covers third parties inside its own delivery path, so an incident there can degrade LiveChat without anything being wrong in LiveChat's own systems. It is the same dependency problem this page measures from the outside.

How we measure this

  • We request LiveChat's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 7 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where LiveChat publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of LiveChat itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when LiveChat goes down

We check LiveChat every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required