Manychat - Notice history

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

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!

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

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.

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.

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.

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.

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.

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.

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.