Landbot Outage History
10 incidents recorded over the last 365 days, 5 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 Landbot Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Intermittent latency affecting our ServicesWe experienced periods of elevated latency and occasional timeouts affecting conversations with agents, along with other types of requests. The issue has since been fully resolved and all systems are operating… | -964 min | Resolved |
| Jun 23, 2026 | Google Database Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 8, 2026 | Urgent Scheduled Maintenance – Knowledge Base Infrastructure OptimizationThe scheduled maintenance has been completed successfully. | 1h 0m | Scheduled |
| May 4, 2026 | Technical issues affecting our ServicesThis incident has been resolved. | 43 min | Resolved |
| Apr 23, 2026 | Technical issues affecting our ServicesThis incident has been resolved. | 24 min | Resolved |
| Feb 24, 2026 | Google Database Scheduled MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Dec 15, 2025 | Degraded Bot Conversations Using Agent Knowledge BasesThis incident has been resolved. | 17h 56m | Resolved |
| Nov 18, 2025 | Cloudflare Global Network experiencing issues - Still monitoringCloudflare has marked the incident as resolved. Nov 18, 2025 - 19:28 UTC https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 | 19h 36m | Resolved |
| Nov 18, 2025 | Google Database Scheduled MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Nov 11, 2025 | Internal tool maintenance updateScheduled maintenance completed with no issues | 1h 0m | Scheduled |
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 Landbot 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 Landbot 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 Landbot 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 Landbot outage in this window ran 19h 36m, against a mean recovery of 4h 41m. If you depend on Landbot 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.