ManyChat Outage History

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.

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.

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.

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.

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.

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.

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.

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.