Yellow AI Outage History

Yellow AI major outage · 1 active incident View live status →

Yellow AI had 29 outages in the last 2 years totaling 8h 21m of downtime — averaging 1.2 incidents per month.

There were 29 Yellow AI outages since August 29, 2025 totaling 8h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.yellow.ai

Major June 12, 2026

Meta Services Outage – All Regions

Detected by Pingoru
Jun 12, 2026, 02:13 PM UTC
Resolved
Jun 12, 2026, 05:40 PM UTC
Duration
3h 26m
Affected: User360 (IND)Live Agent/Inbox (IND)Analyze (IND)Voice (IND)Message Delivery (IND)AI & NLP (IND)Analytics & Insights (IND)WhatsApp (IND)User Authentication (IND)Workflow/Agent Builder (IND)Integrations (IND)Knowledge Base (IND)Web Widget (IND)Engagement (IND)Bot Executor (IND)User Authentication (JKT)Bot Executor (JKT)Analytics & Insights (JKT)AI & NLP (JKT)Voice (MEA)WhatsApp (JKT)Web Widget (JKT)Workflow/Agent Builder (JKT)Analyze (JKT)Live Agent/Inbox (MEA)Integrations (JKT)Engagement (MEA)Message Delivery (JKT)Knowledge Base (JKT)User360 (MEA)Knowledge Base (SING)Web Widget (SING)Integrations (SING)AI & NLP (MEA)WhatsApp (SING)Workflow/Agent Builder (SING)Bot Executor (SING)Message Delivery (MEA)Engagement (JKT)User Authentication (MEA)Analyze (SING)Live Agent/Inbox (JKT)Voice (JKT)Analytics & Insights (MEA)User360 (JKT)Knowledge Base (EURO)User360 (SING)Live Agent/Inbox (SING)Bot Executor (MEA)Message Delivery (SING)Workflow/Agent Builder (MEA)WhatsApp (MEA)Analytics & Insights (SING)Integrations (MEA)Analyze (EURO)AI & NLP (SING)Voice (SING)Web Widget (MEA)Engagement (SING)User Authentication (SING)User360 (USA)Bot Executor (EURO)Integrations (EURO)User Authentication (EURO)Web Widget (EURO)Live Agent/Inbox (USA)Analyze (USA)Engagement (USA)WhatsApp (EURO)AI & NLP (EURO)Analytics & Insights (EURO)Message Delivery (EURO)Knowledge Base (USA)Workflow/Agent Builder (USA)Voice (USA)Live Agent/Inbox (EURO)User360 (EURO)WhatsApp (USA)Voice (EURO)Analyze (QTR)Knowledge Base (QTR)AI & NLP (USA)Analytics & Insights (USA)Integrations (USA)Web Widget (USA)Workflow/Agent Builder (EURO)User Authentication (USA)Bot Executor (USA)Message Delivery (USA)Engagement (EURO)Analytics & Insights (QTR)Workflow/Agent Builder (QTR)Integrations (QTR)Knowledge Base (MEA)User360 (QTR)Message Delivery (QTR)Bot Executor (QTR)WhatsApp (QTR)Live Agent/Inbox (QTR)Analyze (MEA)AI & NLP (QTR)Engagement (QTR)User Authentication (QTR)Web Widget (QTR)
Timeline · 3 updates
  1. investigating Jun 12, 2026, 02:13 PM UTC

    All channels related to Meta — including WhatsApp, Instagram, and Facebook Messenger — are experiencing disruption. Our internal teams are coordinating with the concerned team to resolve the issue at the earliest. We appreciate your patience and will share the next update as soon as possible.

  2. identified Jun 12, 2026, 02:43 PM UTC

    Meta has identified high levels of disruption impacting the WhatsApp Cloud API. Their engineering teams are actively investigating the issue. They have indicated that they will provide another update within 1 hour or sooner if additional information becomes available. To track live updates directly from Meta, please refer to their status page: [Meta Status Page](https://metastatus.com/whatsapp-business-api)

  3. resolved Jun 12, 2026, 05:40 PM UTC

    Meta has confirmed that the services have now been fully restored. Bots in all regions should now be functioning as expected. We will continue to monitor the services closely to ensure platform stability. We apologize for any inconvenience this may have caused.

Read the full incident report →

Major May 17, 2026

NLP Service Degradation in JKT Region

Detected by Pingoru
May 17, 2026, 01:45 PM UTC
Resolved
May 17, 2026, 04:20 PM UTC
Duration
2h 35m
Affected: AI & NLP (JKT)
Timeline · 4 updates
  1. investigating May 17, 2026, 01:45 PM UTC

    **Incident: NLP Service Degradation in JKT Region** We are currently experiencing an issue impacting NLP services in the JKT region. **Impact:** Bots relying on NLP processing may not respond correctly or could experience delayed responses. This may impact both Virtual Agent interactions and related automation workflows. **Current Status:** Our engineering teams are actively investigating the issue and working to restore normal service as quickly as possible. We are currently investigating this incident.

  2. identified May 17, 2026, 03:46 PM UTC

    **Incident: NLP Service Degradation in JKT Region** We are currently experiencing an issue impacting NLP services in the JKT region. **Impact:** Bots relying on NLP processing may not respond correctly or could experience delayed responses. This may impact both Virtual Agent interactions and related automation workflows. **Current Status:** Our engineering teams are actively investigating the issue and working to restore normal service as quickly as possible. We are currently investigating this incident.

  3. monitoring May 17, 2026, 04:19 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved May 17, 2026, 04:20 PM UTC

    **NLP Service Degradation in JKT Region** The issue impacting NLP services in the JKT region has been resolved. Our teams identified the root cause and implemented mitigation steps to restore normal functionality. Bots in the affected region should now be responding as expected. We will continue to monitor the services closely to ensure platform stability.

Read the full incident report →

Notice April 23, 2026

Engagement Service Disruption Impacting Notification Delivery

Detected by Pingoru
Apr 23, 2026, 07:30 AM UTC
Resolved
Apr 23, 2026, 09:49 AM UTC
Duration
2h 19m
Affected: Yellow.aiEngagement (IND)
Timeline · 3 updates
  1. investigating Apr 23, 2026, 07:30 AM UTC

    We are currently experiencing a service disruption affecting our Engagement service. **Impact:** Notifications are not being delivered as expected. --- Our engineering team is actively investigating the issue and working to identify the root cause. We are prioritizing this and will share updates as soon as we have more information.

  2. identified Apr 23, 2026, 07:44 AM UTC

    We are currently experiencing a service disruption affecting our Engagement service. **Impact:** Notifications are not being delivered as expected. --- **Update** The root cause of the issue has been identified. Our team is working on implementing a fix to restore notification delivery at the earliest.

  3. monitoring Apr 23, 2026, 07:58 AM UTC

    A fix has been implemented, and notification delivery is being gradually restored. We are closely monitoring the system to ensure stability.

Read the full incident report →