ChatBot Outage History
27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded ChatBot Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 15, 2026 | Scheduled maintenanceMaintenance has started | 28 min | Resolved |
| Sep 30, 2026 | Scheduled maintenanceMaintenance has started | 22 min | Resolved |
| Jan 29, 2026 | Knowledge Hub section - issue with uploading filesThe issue has been fully resolved and uploading files is working as expected. Thank you for your patience while we worked to restore normal service. | 1h 41m | Resolved |
| Dec 22, 2025 | Service InterruptionWe're glad to report that the issue is now resolved! We apologize for any inconveniences that you have experienced. | -3393607 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2730457 min | Resolved |
| Dec 22, 2025 | Issue with LiveChat integrationThis incident has been resolved. | -2806453 min | Resolved |
| Dec 22, 2025 | Database issueThis incident has been resolved. | -2993259 min | Resolved |
| Dec 22, 2025 | LiveChat integration issueThere was a 15-minute service interruption for the customers using LiveChat integration. As soon as we identified the issue, we contacted the LiveChat team that implemented a fix. The problem was removed. Other… | -3090382 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2580207 min | Resolved |
| Dec 22, 2025 | Issues with ChatBot applicationThis incident has been resolved. | -2590638 min | Resolved |
| Dec 22, 2025 | Server connection issuesWe've been informed about the outage in our service provider datacenter at 7:20 PM CET. At that time, our application was unavailable for about 35 minutes, until 7:55 PM CET. After that time, all our services were… | -2620377 min | Resolved |
| Dec 22, 2025 | Performance issuesWe've noticed performance issues on our servers, causing slow app loading and delays in the bot responses at 6:30 PM CET. The fix has been posted, and the issue has been resolved after 20 minutes, around 6:50 PM CET. | -2620442 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesAt 9:30 AM CET, we noticed an increased response time in our integration with the LiveChat product. Some bots used in this integration could respond with a delay. At 11:30 AM CET, we got a confirmation from the LiveChat… | -2651242 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2671363 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2691164 min | Resolved |
| Dec 22, 2025 | Issue with subscription page (subprocessor issue)We identified an issue with one of our subprocessors, which caused issues with accessing subscription pages. The incident has been resolved on 10:00 AM CET. | -2556232 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2525485 min | Resolved |
| Dec 22, 2025 | Service degradationAround 4:50 PM GMT, our Administrators noticed increased traffic on our servers. After a quick investigation, at 5:00 PM GMT, we attempted to post a first fix for the identified issue, which partially solved the… | -2539862 min | Resolved |
| Dec 22, 2025 | Network connection issuesThis incident has been resolved. | -2559778 min | Resolved |
| Dec 22, 2025 | Degraded performance of Application and APIThis incident has been resolved. | -2560112 min | Resolved |
| Dec 22, 2025 | Degraded performance of the API serviceAt 8:00 PM GMT, we noticed an increased response time in our API service. We continue to monitor this situation. The issue has been resolved around 8:15 PM GMT. | -2565577 min | Resolved |
| Dec 22, 2025 | Degraded performance of Application and APIThis incident has been resolved. | -2569843 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -1984395 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2009903 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThis incident has been resolved. | -2011275 min | Resolved |
| Dec 22, 2025 | Problems with creating new accounts and managing subscriptionThis incident has been resolved. | -2233551 min | Resolved |
| Dec 22, 2025 | LiveChat integration issuesThere was a 1-hour service interruption with the LiveChat integration. The issue has been identified at 3:00 PM GMT as an outage of one of our sub-processors responsible for our CDNs, Akamai. As soon as we identified… | -2323972 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next ChatBot incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This ChatBot Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before ChatBot acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single ChatBot outage in this window ran 1h 41m, against a mean recovery of 50 min. If you depend on ChatBot in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.