Flow XO experienced a minor incident on June 12, 2026, lasting 2h 56m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 12, 2026, 02:03 PM UTC
We are monitoring and will provide more information as it becomes available.
- identified Jun 12, 2026, 02:44 PM UTC
Meta has acknowledged an issue affecting WhatsApp Business API and related messaging services. This is an upstream outage on Meta's side, not a Flow XO platform issue. You can follow Meta's status and updates here: https://metastatus.com/whatsapp-business-api We continue to monitor and will update this incident as services recover.
- identified Jun 12, 2026, 02:46 PM UTC
Meta has posted the following active service disruptions (source: https://metastatus.com/whatsapp-business-api): • WhatsApp Business Platform — Cloud API (High disruptions) We are currently experiencing high disruptions impacting WhatsApp Cloud API. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. • WhatsApp Business Platform — Coexistence - Messaging (High disruptions) We are currently experiencing high disruptions impacting WhatsApp Coexistence. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. • WhatsApp Business Platform — Coexistence - Onboarding (High disruptions) We are currently experiencing high disruptions impacting WhatsApp Coexistence. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. • WhatsApp Business Platform — Marketing Messages API for WhatsApp (High disruptions) We are currently experiencing high disruptions impacting Marketing Messages API for WhatsApp. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. • WhatsApp Business Platform — Cloud API - Calling (High disruptions) We are currently experiencing high disruptions impacting Cloud API - Calling. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. • Messenger API for Instagram — Platform Status (High disruptions) We are currently experiencing high disruptions impacting Messenger API for Instagram. Our engineering teams are investigating the issue. We will provide another update if additional information is available.
- identified Jun 12, 2026, 02:51 PM UTC
Update from Meta (Messenger Platform — Platform Status): We are currently experiencing high disruptions impacting Messenger Platform. Our engineering teams are investigating the issue. We will provide another update if additional information is available. Meta status: High disruptions Source: https://metastatus.com/whatsapp-business-api
- identified Jun 12, 2026, 04:12 PM UTC
Update from Meta (WhatsApp Business Platform — Embedded Signup): We are currently experiencing high disruptions impacting Embedded Signup. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. Meta status: High disruptions Source: https://metastatus.com/whatsapp-business-api
- identified Jun 12, 2026, 04:18 PM UTC
Update from Meta (WhatsApp Business Platform — WhatsApp Business Account Management): We are currently experiencing high disruptions impacting WhatsApp Business Account Management. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. Meta status: High disruptions Source: https://metastatus.com/whatsapp-business-api
- monitoring Jun 12, 2026, 04:45 PM UTC
Meta platform errors have subsided. We are monitoring for 15 minutes to confirm services remain stable before closing this incident.
- resolved Jun 12, 2026, 05:00 PM UTC
Meta platform services have recovered and messaging is operating normally. This incident is now resolved.