Landbot Outage History

Landbot is up right now

Landbot had 4 outages in the last 2 years totaling 38h 17m of downtime — averaging 0.2 incidents per month.

There were 4 Landbot outages since August 25, 2025 totaling 38h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.landbot.io

Major May 4, 2026

Technical issues affecting our Services

Detected by Pingoru
May 04, 2026, 08:11 AM UTC
Resolved
May 04, 2026, 08:55 AM UTC
Duration
43m
Affected: WhatsApp services
Timeline · 3 updates
  1. investigating May 04, 2026, 08:11 AM UTC

    We are currently investigating this issue.

  2. monitoring May 04, 2026, 08:35 AM UTC

    A fix has been implemented and we are monitoring results.

  3. resolved May 04, 2026, 08:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 15, 2025

Degraded Bot Conversations Using Agent Knowledge Bases

Detected by Pingoru
Dec 15, 2025, 01:06 PM UTC
Resolved
Dec 16, 2025, 07:03 AM UTC
Duration
17h 56m
Affected: landbotsWhatsApp bots
Timeline · 3 updates
  1. monitoring Dec 15, 2025, 01:06 PM UTC

    We are experiencing degraded performance in bot conversations that rely on Agent Knowledge Bases due to an ongoing incident with our upstream vector database provider: https://status.pinecone.io/incidents/ksj7pvjgtjlj. As a result, operations involving Knowledge Bases — including uploading, updating, deleting, and querying content — may fail or return incomplete results. This may cause agents to retrieve incorrect or missing information and respond inconsistently to end users. We are actively monitoring the situation and will provide updates as soon as the upstream service is restored.

  2. monitoring Dec 15, 2025, 08:55 PM UTC

    Our upstream vector database provider identified the issue 6 hours ago, we are actively monitoring the status in order to provide updates as soon as the upstream service is restored: https://status.pinecone.io/incidents/ksj7pvjgtjlj

  3. resolved Dec 16, 2025, 07:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Cloudflare Global Network experiencing issues - Still monitoring

Detected by Pingoru
Nov 18, 2025, 11:53 AM UTC
Resolved
Nov 19, 2025, 07:30 AM UTC
Duration
19h 36m
Affected: BuilderlandbotsEmail notificationsWebhooksWhatsApp botsChatsWhatsApp servicesZapierMessenger botsGoogle SheetsMetrics
Timeline · 6 updates
  1. investigating Nov 18, 2025, 11:53 AM UTC

    Cloudflare Global Network experiencing issues, causing Landbot.io to fail. For more details please see https://www.cloudflarestatus.com/

  2. investigating Nov 18, 2025, 12:22 PM UTC

    Cloudfare continues to investigate: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. investigating Nov 18, 2025, 02:34 PM UTC

    Cloudfare continues to work on a fix for this issue. More information here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  4. monitoring Nov 18, 2025, 02:55 PM UTC

    Monitoring - A fix has been implemented by Cloudfare and confirm incident is now resolved. They continue to monitor for errors to ensure all services are back to normal.

  5. monitoring Nov 18, 2025, 04:59 PM UTC

    Cloudfare continues to see errors drop as they work through services globally and clearing remaining errors and latency. Landbot is working as expected. More details here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  6. resolved Nov 19, 2025, 07:30 AM UTC

    Cloudflare has marked the incident as resolved. Nov 18, 2025 - 19:28 UTC https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Read the full incident report →

Notice August 25, 2025

DDoS attack detected and mitigated

Detected by Pingoru
Aug 25, 2025, 12:09 PM UTC
Resolved
Aug 25, 2025, 12:09 PM UTC
Duration
Affected: landbots
Timeline · 1 update
  1. resolved Aug 25, 2025, 12:09 PM UTC

    This incident has already been resolved ✅ During the incident, we experienced degradation of services in web page, lasting from 12:35PM to 12:41PM

Read the full incident report →