Is LiveChat Down?

No — LiveChat is up

Reachable from all 8 checked regions

Average response time: 730ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.livechat.com

LiveChat uptime

99.52%

Last 7 days

99.86%

Last 30 days

99.86%

Last 90 days

656ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

6-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

513ms

DNS 101ms TCP 2ms TLS 7ms TTFB 511ms

arn

613ms

DNS 108ms TCP 0ms TLS 5ms TTFB 611ms

bom

1080ms

DNS 127ms TCP 1ms TLS 8ms TTFB 1077ms

cdg

584ms

DNS 100ms TCP 1ms TLS 7ms TTFB 580ms

dfw

163ms

DNS 49ms TCP 0ms TLS 7ms TTFB 161ms

ewr

474ms

DNS 20ms TCP 1ms TLS 8ms TTFB 472ms

fra

707ms

DNS 328ms TCP 1ms TLS 6ms TTFB 704ms

gru

1707ms

DNS 117ms TCP 134ms TLS 272ms TTFB 1705ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 8 of them.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when LiveChat goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required