ManyChat Outage History

ManyChat is up right now

ManyChat had 11 outages in the last 2 years totaling 78h 1m of downtime — averaging 0.5 incidents per month.

There were 11 ManyChat outages since June 17, 2025 totaling 78h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.manychat.com

Minor June 12, 2026

Meta platform is down (FB, IG, WA)

Detected by Pingoru
Jun 12, 2026, 01:46 PM UTC
Resolved
Jun 12, 2026, 07:06 PM UTC
Duration
5h 20m
Affected: 3rd party: Facebook API3rd party: Instagram API3rd party: WhatsApp API
Timeline · 3 updates
  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 →

Minor May 26, 2026

Unable to publish Instagram Comment Trigger Automations connected to specific posts/reels

Detected by Pingoru
May 26, 2026, 02:23 PM UTC
Resolved
May 27, 2026, 09:57 AM UTC
Duration
19h 33m
Affected: Manychat: Web Application
Timeline · 3 updates
  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 →

Minor May 22, 2026

Partial Web/Mobile App & Landing Page Unavailability

Detected by Pingoru
May 22, 2026, 05:28 PM UTC
Resolved
May 24, 2026, 08:50 AM UTC
Duration
1d 15h
Affected: Manychat: Web Application
Timeline · 3 updates
  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 →

Minor May 21, 2026

Technical difficulties with manychat.com

Detected by Pingoru
May 21, 2026, 11:06 PM UTC
Resolved
May 22, 2026, 12:51 PM UTC
Duration
13h 45m
Affected: Manychat: Web Application
Timeline · 4 updates
  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 →