User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 473 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 123 ms | 0 |
| Mon 16 | 0 | 0.0 | 354 ms | 0 |
| Mon 19 | 0 | 0.0 | 564 ms | 0 |
| Mon 21 | 0 | 0.0 | 186 ms | 0 |
| Mon 23 | 0 | 0.0 | 249 ms | 0 |
| Tue 01 | 0 | 0.0 | 224 ms | 0 |
| Tue 03 | 0 | 0.0 | 313 ms | 0 |
| Tue 05 | 0 | 0.0 | 210 ms | 0 |
| Tue 07 | 0 | 0.0 | 275 ms | 0 |
| Tue 09 | 0 | 0.0 | 230 ms | 0 |
| Tue 12 | 0 | 0.0 | 210 ms | 0 |
| Tue 14 | 0 | 0.0 | 343 ms | 0 |
| Tue 16 | 0 | 0.0 | 198 ms | 0 |
| Tue 18 | 0 | 0.0 | 154 ms | 0 |
| Tue 21 | 0 | 0.0 | 459 ms | 0 |
| Tue 23 | 0 | 0.0 | 161 ms | 0 |
| Wed 01 | 0 | 0.0 | 223 ms | 0 |
| Wed 03 | 0 | 0.0 | 208 ms | 0 |
| Wed 06 | 0 | 0.0 | 311 ms | 0 |
| Wed 08 | 0 | 0.0 | 311 ms | 0 |
| Wed 10 | 0 | 0.0 | 131 ms | 0 |
| Wed 12 | 0 | 0.0 | 307 ms | 0 |
| Wed 14 | 0 | 0.0 | 147 ms | 0 |
| Wed 16 | 0 | 0.0 | 513 ms | 0 |
| Wed 19 | 0 | 0.0 | 184 ms | 0 |
| Wed 21 | 0 | 0.0 | 295 ms | 0 |
| Wed 23 | 0 | 0.0 | 536 ms | 0 |
| Thu 01 | 0 | 0.0 | 190 ms | 0 |
| Thu 03 | 0 | 0.0 | 198 ms | 0 |
| Thu 05 | 0 | 0.0 | 279 ms | 0 |
| Thu 07 | 0 | 0.0 | 126 ms | 0 |
| Thu 09 | 0 | 0.0 | 259 ms | 0 |
| Thu 11 | 0 | 0.0 | 217 ms | 0 |
| Thu 13 | 0 | 0.0 | 295 ms | 0 |
| Thu 16 | 0 | 0.0 | 247 ms | 0 |
| Thu 18 | 0 | 0.0 | 391 ms | 0 |
| Thu 20 | 0 | 0.0 | 385 ms | 0 |
| Thu 22 | 0 | 0.0 | 274 ms | 0 |
| Fri 00 | 0 | 0.0 | 342 ms | 0 |
| Fri 02 | 0 | 0.0 | 215 ms | 0 |
| Fri 04 | 0 | 0.0 | 365 ms | 0 |
| Fri 06 | 0 | 0.0 | 165 ms | 0 |
| Fri 08 | 0 | 0.0 | 254 ms | 0 |
| Fri 10 | 0 | 0.0 | 263 ms | 0 |
| Fri 12 | 0 | 0.0 | 288 ms | 0 |
| Fri 14 | 0 | 0.0 | 187 ms | 0 |
| Fri 15 | 0 | 0.0 | 258 ms | 0 |
| Fri 17 | 0 | 0.0 | 473 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for LiveChat yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when LiveChat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send LiveChat alerts to Slack, Discord or a webhook — free.
LiveChat, at livechat.com, is one of the Productivity services we monitor. Text is live chat software for your website with an AI Agent that answers 24/7. Qualify leads and track sales from chats. Start your free 14-day trial.
LiveChat publishes an official status page at status.livechat.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 292 ms average, 165–495 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public LiveChat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
292 ms on average over the last 24 hours (165–495 ms).
Yes, at https://status.livechat.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report LiveChat here at once, the problem is on LiveChat's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with LiveChat. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.