ManyChat Outage History

Started Sep 03, 2026, 05:05 PM UTC· resolved Sep 03, 2026, 06:27 PM UTC

1. investigating Sep 03, 2026, 05:05 PM UTC

   We're aware of an increase in WhatsApp message delivery failures due to a message-processing issue on Meta's side. Some outgoing messages may fail or remain undelivered, while others continue to be delivered normally. This issue is not related to your Manychat account, automations, or WhatsApp number. Our team is monitoring the situation and will share updates as they become available.

2. resolved Sep 03, 2026, 06:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 30, 2026, 11:15 PM UTC· resolved Aug 31, 2026, 12:41 AM UTC

1. investigating Aug 30, 2026, 11:15 PM UTC

   We're currently experiencing a technical incident affecting access to the platform. We sincerely apologize for the disruption this is causing. Our engineering team is actively investigating the situation and working to restore access as quickly as possible. We'll share updates here as soon as we have more information. We truly appreciate your patience while we work through this.

2. monitoring Aug 31, 2026, 12:09 AM UTC

   We implemented a fix and are currently monitoring the result. Thank you for your patience!

3. resolved Aug 31, 2026, 12:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 02:08 PM UTC· resolved Jul 23, 2026, 12:06 AM UTC

1. investigating Jul 22, 2026, 02:08 PM UTC

   We are noticing degraded performance across the Meta platform. We are monitoring the issue and waiting for the information from Meta. So far, message delivery is confirmed to be affected. This is a Meta-side outage and is not specific to Manychat. Meta is currently experiencing degraded service across its messaging platforms.

2. monitoring Jul 22, 2026, 04:20 PM UTC

   According to our data, the errors have diminished. The exact status of the issue is still being investigated.

3. resolved Jul 23, 2026, 12:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 19, 2026, 09:17 AM UTC· resolved Jul 19, 2026, 10:49 AM UTC

1. investigating Jul 19, 2026, 09:17 AM UTC

   We're aware of an ongoing incident on Meta's platforms (Facebook, Instagram, WhatsApp) affecting message delivery and Manychat features. This is a Meta-side outage and is not specific to Manychat. Meta is currently experiencing degraded service across its messaging platforms. **What we recommend:** * **Pause paid ad campaigns** that drive traffic into Instagram/Messenger/WhatsApp automations until the incident is resolved, to avoid paying for clicks that may not convert. * No action is needed inside Manychat — messages and flows will resume automatically as Meta recovers. We're monitoring the situation and will update this page as we learn more.

2. monitoring Jul 19, 2026, 09:53 AM UTC

   Meta has begun recovering. Message delivery is returning to normal — we're monitoring to confirm full recovery before closing this incident.

3. resolved Jul 19, 2026, 10:49 AM UTC

   Meta's platform incident has been fully resolved, and message delivery on Instagram, Messenger, and WhatsApp is now functioning smoothly again. You can safely resume your campaigns. Thanks so much for your patience and understanding!

Read the full incident report →

Started Jun 23, 2026, 09:47 PM UTC· resolved Jun 23, 2026, 10:58 PM UTC

1. investigating Jun 23, 2026, 09:47 PM UTC

   We are currently investigating the incident with Facebook, Instagram, and WhatsApp outage. We are waiting for info from the Meta team at the time. Thank you for your understanding.

2. monitoring Jun 23, 2026, 10:15 PM UTC

   Meta services are back online, and platforms such as Instagram, WhatsApp, and Facebook are accessible again. We are continuing to monitor the situation and will share further updates as more information becomes available. Thank you for your understanding.

3. resolved Jun 23, 2026, 10:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 01:46 PM UTC· resolved Jun 12, 2026, 07:06 PM UTC

1. investigating Jun 12, 2026, 01:46 PM UTC

   Facebook, Instagram, and WhatsApp are currently down. We are waiting for info from the Meta team at the time. No info on Meta Status Pages yet.

2. monitoring Jun 12, 2026, 03:41 PM UTC

   Meta services are no longer fully unavailable, and platforms such as Instagram, WhatsApp, Facebook, and Threads can now be accessed again. However, performance remains degraded, and we are still observing high error rates for API actions. This may continue to impact actions that rely on Meta APIs, including channel connections, messaging, and other Meta-related features. We are continuing to monitor the situation and will share further updates as more information becomes available.

3. resolved Jun 12, 2026, 07:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 26, 2026, 02:23 PM UTC· resolved May 27, 2026, 09:57 AM UTC

1. investigating May 26, 2026, 02:23 PM UTC

   When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the "Couldn't create Automation" error message pops up, preventing the publishing. We are investigating the matter to identify the root cause. For the time being, we suggest using one of two workarounds: 1\. Switch the trigger settings from a specific post to "Any post or reel", or 2\. In the Automations tab, go through the following options: "+ New Automation" -> "+ Start From Scratch" -> "Start from a blank canvas" -> "+ New Trigger" -> "User comments on your Post or Reel" Trigger. From there, you can choose the "Specific Post or Reel" option without issues.

2. investigating May 26, 2026, 02:58 PM UTC

   When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the "Couldn't create Automation" error message pops up, preventing the publishing. Also, Story Reply Automations may show a visual error after picking a specific Story; however, such an Automation can still be published and will be working as intended. We are investigating the matter to identify the root cause. For the time being, we suggest using one of two workarounds: 1\. Switch the trigger settings from a specific post to "Any post or reel", or 2\. In the Automations tab, go through the following options: "+ New Automation" -> "+ Start From Scratch" -> "Start from a blank canvas" -> "+ New Trigger" -> "User comments on your Post or Reel" Trigger. From there, you can choose the "Specific Post or Reel" option without issues.

3. resolved May 27, 2026, 09:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 22, 2026, 05:28 PM UTC· resolved May 24, 2026, 08:50 AM UTC

1. investigating May 22, 2026, 05:28 PM UTC

   We are experiencing another wave of large-scale DDoS attacks that have affected the availability of parts of the web application and public-facing landing pages. The attacks should not affect account automations, and we observed no impact on message processing functionality. The mitigation efforts are ongoing until all services are stabilized and fully functional.

2. monitoring May 22, 2026, 09:23 PM UTC

   From 15:56 UTC to 20:50 UTC on May 22, 2026, we experienced the 3d wave of DDoS attack that partly affected availability for the web application and public-facing landing pages. The attacks did not affect account automations, and we observed no impact on message processing functionality. The attacks have been mitigated, and all services have since remained stable and fully operational. We will continue monitoring the situation over the coming hours.

3. resolved May 24, 2026, 08:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 11:06 PM UTC· resolved May 22, 2026, 12:51 PM UTC

1. investigating May 21, 2026, 11:43 PM UTC

   We are currently investigating this incident.

2. identified May 22, 2026, 12:42 AM UTC

   We're currently experiencing a technical incident affecting access to the platform. We sincerely apologize for the disruption this is causing. Our engineering team is actively investigating the situation and working to restore access as quickly as possible. We'll share updates here as soon as we have more information. We truly appreciate your patience while we work through this.

3. monitoring May 22, 2026, 04:37 AM UTC

   The situation is now significantly more stable, and most services are operating normally again. We’re continuing to closely monitor platform performance while recovery is finalized. Some users may still experience intermittent issues during this period. Thank you again for your patience and understanding.

4. resolved May 22, 2026, 12:51 PM UTC

   From 22:58 UTC on May 21, 2026, to 06:18 UTC on May 22, 2026, we experienced several waves of large-scale DDoS attacks that affected availability for parts of the web application and public-facing landing pages. The attacks did not affect account automations, and we observed no impact on message processing functionality. The attacks have been mitigated, and all services have since remained stable and fully operational. We have deployed additional traffic filtering and infrastructure protection measures to further improve resilience and reduce the risk of similar incidents. There is no ongoing customer impact at this time.

Read the full incident report →

Started Apr 10, 2026, 07:59 AM UTC· resolved Apr 10, 2026, 02:56 PM UTC

1. identified Apr 10, 2026, 07:59 AM UTC

   WhatsApp API has detected an issue with the sign-up process, preventing most customers from connecting their WhatsApp channels to Manychat. To stay updated on further developments, please follow the link to the Meta Status page below.

2. resolved Apr 10, 2026, 02:56 PM UTC

   The Meta downtime affecting WhatsApp signup has been resolved, and services have been restored in the WhatsApp API Source:

Read the full incident report →

Started Feb 18, 2026, 06:00 AM UTC· resolved Feb 18, 2026, 06:00 AM UTC

1. identified Feb 18, 2026, 06:00 AM UTC

   We are continuing to work on a fix for this incident.

2. identified Feb 22, 2026, 09:34 AM UTC

   We are continuing to work on a fix for this incident.

3. resolved Apr 24, 2026, 12:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 11:16 PM UTC· resolved Nov 20, 2025, 10:42 AM UTC

1. investigating Nov 19, 2025, 11:16 PM UTC

   We are aware that **comments on posts are not triggering the automation**. The issue is affecting all Comment to DM automation on accounts connected **using the Meta Business connection**. DM automation is currently functioning as expected. Our team has reported the issue to Meta, and we'll share updates here as soon as more information is available. Thank you for your patience.

2. identified Nov 19, 2025, 11:23 PM UTC

   We are continuing to work on a fix for this incident.

3. identified Nov 19, 2025, 11:27 PM UTC

   We are continuing to work to provide an update an soon as possible.

4. identified Nov 20, 2025, 12:33 AM UTC

   We are aware of an issue affecting webhook reception for some Instagram accounts, which may cause disruptions in the Comment to DM feature. This issue is outside of our control and requires intervention from the Meta team. We are receiving multiple similar reports and have already escalated the problem to Meta. Our team is actively monitoring the situation. We’ll keep you updated here as soon as new information becomes available. Thank you for your patience and understanding.

5. resolved Nov 20, 2025, 10:42 AM UTC

   According to our most recent tests, the Meta team has fixed the issue.

Read the full incident report →