<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Manychat Status - Incident history</title>
    <link>https://status.manychat.com</link>
    <description>Manychat</description>
    <pubDate>Fri, 12 Jun 2026 13:46:33 +0000</pubDate>
    
<item>
  <title>Meta platform is down (FB, IG, WA)</title>
  <description>
    Type: Incident
    Duration: 5 hours and 20 minutes

    Affected Components: 3rd party: Facebook API, 3rd party: Instagram API, 3rd party: WhatsApp API
    Jun 12, 13:46:33 GMT+0 - Investigating - 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. Jun 12, 15:41:13 GMT+0 - Monitoring - 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. Jun 12, 19:06:44 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:46:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:41:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:06:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 12 Jun 2026 13:46:33 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmqazcr3900otphm1w9k34dkw</link>
  <guid>https://status.manychat.com/incident/cmqazcr3900otphm1w9k34dkw</guid>
</item>

<item>
  <title>Unable to publish Instagram Comment Trigger Automations connected to specific posts/reels</title>
  <description>
    Type: Incident
    Duration: 19 hours and 34 minutes

    Affected Components: Manychat: Web Application
    May 26, 14:23:13 GMT+0 - Investigating - When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the &quot;Couldn&#039;t create Automation&quot; 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 &quot;Any post or reel&quot;, or  
  
2\. In the Automations tab, go through the following options: &quot;+ New Automation&quot; -&gt; &quot;+ Start From Scratch&quot; -&gt; &quot;Start from a blank canvas&quot; -&gt; &quot;+ New Trigger&quot; -&gt; &quot;User comments on your Post or Reel&quot; Trigger.  
From there, you can choose the &quot;Specific Post or Reel&quot; option without issues. May 26, 14:58:48 GMT+0 - Investigating - When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the &quot;Couldn&#039;t create Automation&quot; 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 &quot;Any post or reel&quot;, or  
  
2\. In the Automations tab, go through the following options: &quot;+ New Automation&quot; -&gt; &quot;+ Start From Scratch&quot; -&gt; &quot;Start from a blank canvas&quot; -&gt; &quot;+ New Trigger&quot; -&gt; &quot;User comments on your Post or Reel&quot; Trigger.  
From there, you can choose the &quot;Specific Post or Reel&quot; option without issues. May 27, 09:57:12 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:23:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the &quot;Couldn&#039;t create Automation&quot; 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 &quot;Any post or reel&quot;, or  
  
2\. In the Automations tab, go through the following options: &quot;+ New Automation&quot; -&gt; &quot;+ Start From Scratch&quot; -&gt; &quot;Start from a blank canvas&quot; -&gt; &quot;+ New Trigger&quot; -&gt; &quot;User comments on your Post or Reel&quot; Trigger.  
From there, you can choose the &quot;Specific Post or Reel&quot; option without issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:58:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  When publishing a quick Automation with a Comment Trigger connected to a specific Post/Reel, the &quot;Couldn&#039;t create Automation&quot; 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 &quot;Any post or reel&quot;, or  
  
2\. In the Automations tab, go through the following options: &quot;+ New Automation&quot; -&gt; &quot;+ Start From Scratch&quot; -&gt; &quot;Start from a blank canvas&quot; -&gt; &quot;+ New Trigger&quot; -&gt; &quot;User comments on your Post or Reel&quot; Trigger.  
From there, you can choose the &quot;Specific Post or Reel&quot; option without issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:57:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 14:23:13 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmpmq6f3o0dhvnrm0y76x6gxc</link>
  <guid>https://status.manychat.com/incident/cmpmq6f3o0dhvnrm0y76x6gxc</guid>
</item>

<item>
  <title>Partial Web/Mobile App &amp; Landing Page Unavailability</title>
  <description>
    Type: Incident
    Duration: 1 day, 15 hours and 22 minutes

    Affected Components: Manychat: Web Application
    May 22, 17:28:15 GMT+0 - Investigating - 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. May 22, 21:23:15 GMT+0 - Monitoring - 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. May 24, 08:50:27 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 15 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:28:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:23:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:50:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 22 May 2026 17:28:15 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmph70ykd008mqgawids81cfm</link>
  <guid>https://status.manychat.com/incident/cmph70ykd008mqgawids81cfm</guid>
</item>

<item>
  <title>Technical difficulties with manychat.com</title>
  <description>
    Type: Incident
    Duration: 13 hours and 45 minutes

    Affected Components: Manychat: Web Application
    May 21, 23:06:00 GMT+0 - Investigating - We are currently investigating this incident. May 22, 00:42:43 GMT+0 - Identified - We&#039;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&#039;ll share updates here as soon as we have more information.

We truly appreciate your patience while we work through this. May 22, 04:37:56 GMT+0 - Monitoring - 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. May 22, 12:51:01 GMT+0 - Resolved - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:42:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;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&#039;ll share updates here as soon as we have more information.

We truly appreciate your patience while we work through this..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:37:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:51:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 23:06:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmpg4zc3i0088p598ubiqs3f7</link>
  <guid>https://status.manychat.com/incident/cmpg4zc3i0088p598ubiqs3f7</guid>
</item>

<item>
  <title>Disruption in the WhatsApp sign-up process </title>
  <description>
    Type: Incident
    Duration: 6 hours and 57 minutes

    Affected Components: 3rd party: WhatsApp API
    Apr 10, 07:59:07 GMT+0 - Identified - 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. &lt;https://metastatus.com/whatsapp-business-api&gt; Apr 10, 14:56:10 GMT+0 - Resolved - The Meta downtime affecting WhatsApp signup has been resolved, and services have been restored in the WhatsApp API  
  
Source: &lt;https://metastatus.com/whatsapp-business-api&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:59:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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. &lt;https://metastatus.com/whatsapp-business-api&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:56:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The Meta downtime affecting WhatsApp signup has been resolved, and services have been restored in the WhatsApp API  
  
Source: &lt;https://metastatus.com/whatsapp-business-api&gt;.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 10 Apr 2026 07:59:07 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmnsm7b2b08xcnebye6o4qowv</link>
  <guid>https://status.manychat.com/incident/cmnsm7b2b08xcnebye6o4qowv</guid>
</item>

<item>
  <title>Delays and failures in Follow to DM (Say Hi to New Followers) automation on Instagram</title>
  <description>
    Type: Incident
    

    Affected Components: 3rd party: Instagram API
    Mar 24, 15:19:00 GMT+0 - Identified - The issue affecting the Instagram “Say hi to new followers” automation has been identified as a Meta-side bug and is currently under active investigation. We&#039;re closely monitoring the situation with Meta. Mar 17, 03:00:00 GMT+0 - Investigating - We are aware of reports of the Follow to DM automation not triggering or behaving inconsistently for some Instagram accounts. Affected users may experience delayed or no message delivery, despite the automation being correctly configured and eligible. Our team is actively investigating. We will provide updates as new information becomes available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue affecting the Instagram “Say hi to new followers” automation has been identified as a Meta-side bug and is currently under active investigation. We&#039;re closely monitoring the situation with Meta..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of the Follow to DM automation not triggering or behaving inconsistently for some Instagram accounts. Affected users may experience delayed or no message delivery, despite the automation being correctly configured and eligible. Our team is actively investigating. We will provide updates as new information becomes available..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Mar 2026 03:00:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmmxljn3s01ntuud42lsa7zud</link>
  <guid>https://status.manychat.com/incident/cmmxljn3s01ntuud42lsa7zud</guid>
</item>

<item>
  <title>Delivery issues for some accounts with Messenger channel connected</title>
  <description>
    Type: Incident
    Duration: 6 days, 6 hours and 14 minutes

    Affected Components: 3rd party: Facebook API
    Feb 18, 06:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 22, 09:34:52 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 24, 12:14:15 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 6 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:34:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:14:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 18 Feb 2026 06:00:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmlxld7sz071tkscobg015xk3</link>
  <guid>https://status.manychat.com/incident/cmlxld7sz071tkscobg015xk3</guid>
</item>

<item>
  <title>Scheduled broadcasts triggering simultaneously</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    
    Jan 30, 03:00:00 GMT+0 - Investigating - We&#039;re investigating an issue where all scheduled broadcasts are being sent at the same time when one scheduled broadcast is triggered.

We recommend avoiding scheduling new broadcasts until this is resolved.

Updates will be posted here as we make progress. Jan 31, 15:23:25 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re investigating an issue where all scheduled broadcasts are being sent at the same time when one scheduled broadcast is triggered.

We recommend avoiding scheduling new broadcasts until this is resolved.

Updates will be posted here as we make progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:23:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 30 Jan 2026 03:00:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cml2g7i1s0506faom6qih4se1</link>
  <guid>https://status.manychat.com/incident/cml2g7i1s0506faom6qih4se1</guid>
</item>

<item>
  <title>[Instagram] Comment to DM automations not working</title>
  <description>
    Type: Incident
    Duration: 11 hours and 26 minutes

    Affected Components: 3rd party: Instagram API
    Nov 20, 00:33:30 GMT+0 - Identified - 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. Nov 20, 10:42:56 GMT+0 - Resolved - According to our most recent tests, the Meta team has fixed the issue.  Nov 19, 23:23:23 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 19, 23:16:45 GMT+0 - Investigating - 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&#039;ll share updates here as soon as more information is available.

Thank you for your patience. Nov 19, 23:27:53 GMT+0 - Identified - We are continuing to work to provide an update an soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:33:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:42:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  According to our most recent tests, the Meta team has fixed the issue. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:23:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:16:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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&#039;ll share updates here as soon as more information is available.

Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:27:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work to provide an update an soon as possible..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 19 Nov 2025 23:16:45 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmi6mgelw00fr11g0a3iyugo0</link>
  <guid>https://status.manychat.com/incident/cmi6mgelw00fr11g0a3iyugo0</guid>
</item>

<item>
  <title>[Instagram] Automations Webhooks Missing Issue</title>
  <description>
    Type: Incident
    Duration: 21 days, 21 hours and 15 minutes

    Affected Components: 3rd party: Instagram API
    Oct 3, 15:00:00 GMT+0 - Investigating - We’re aware of an issue where webhooks are not being delivered for some Instagram accounts. This may cause **automations to fail to trigger or stop when a button is clicked**. The issue has been reported to Meta, and we’re monitoring it while awaiting their response.

We’ll share updates here as soon as more information is available. Thank you for your patience. Apr 24, 12:15:29 GMT+0 - Resolved - This incident has been resolved. Apr 24, 12:15:44 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 days, 21 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We’re aware of an issue where webhooks are not being delivered for some Instagram accounts. This may cause **automations to fail to trigger or stop when a button is clicked**. The issue has been reported to Meta, and we’re monitoring it while awaiting their response.

We’ll share updates here as soon as more information is available. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:15:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:15:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 3 Oct 2025 15:00:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmh44imm700cmdq2ahtgp7h86</link>
  <guid>https://status.manychat.com/incident/cmh44imm700cmdq2ahtgp7h86</guid>
</item>

<item>
  <title>WhatsApp Message Delivery Errors</title>
  <description>
    Type: Incident
    Duration: 2 days, 7 hours and 10 minutes

    Affected Components: 3rd party: WhatsApp API
    Aug 20, 00:00:00 GMT+0 - Investigating - We’re currently seeing elevated sending errors on the WhatsApp channel, mainly affecting Interactive Message Blocks (messages with buttons or Message Lists). Regular message blocks without buttons appear to be sending as expected. The issue originates on Meta’s side and has already been reported to them. Our team is actively monitoring and will share updates as soon as more information is available. Aug 21, 10:54:33 GMT+0 - Monitoring - We are now observing a decrease in these errors, and our team continues to monitor the situation closely. Aug 22, 07:09:42 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 7 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We’re currently seeing elevated sending errors on the WhatsApp channel, mainly affecting Interactive Message Blocks (messages with buttons or Message Lists). Regular message blocks without buttons appear to be sending as expected. The issue originates on Meta’s side and has already been reported to them. Our team is actively monitoring and will share updates as soon as more information is available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:54:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are now observing a decrease in these errors, and our team continues to monitor the situation closely..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:09:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmek5x5hz0024s53sgn0a2azq</link>
  <guid>https://status.manychat.com/incident/cmek5x5hz0024s53sgn0a2azq</guid>
</item>

<item>
  <title>[WhatsApp] Deteriorated Message sending</title>
  <description>
    Type: Incident
    Duration: 1 hour and 18 minutes

    Affected Components: 3rd party: WhatsApp API
    Jul 21, 22:01:22 GMT+0 - Investigating - We are currently investigating this incident. Jul 21, 23:19:47 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:01:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:19:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 21 Jul 2025 22:01:22 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmddnhdzj001aupoa55k3pw3g</link>
  <guid>https://status.manychat.com/incident/cmddnhdzj001aupoa55k3pw3g</guid>
</item>

<item>
  <title>[Messenger] Messages fail to send for some accounts. Disabling any running campaigns is recommended</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    Affected Components: Manychat: Message sending
    Jun 17, 16:32:58 GMT+0 - Resolved - This incident has been resolved. Jun 17, 15:35:42 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:32:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:35:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Jun 2025 15:35:42 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmc0oqga40007143gr1wce61i</link>
  <guid>https://status.manychat.com/incident/cmc0oqga40007143gr1wce61i</guid>
</item>

<item>
  <title>[Instagram] Automation Webhooks Issue</title>
  <description>
    Type: Incident
    Duration: 3 days, 20 hours and 13 minutes

    Affected Components: 3rd party: Instagram API
    May 25, 18:55:00 GMT+0 - Investigating - We&#039;re aware that Instagram automation webhooks may not be received, causing automations to fail to trigger as expected. Our team is actively investigating whether the issue stems from our side or Meta&#039;s. May 26, 17:03:09 GMT+0 - Identified - We&#039;re currently aware of an issue affecting the reception of webhooks for some Instagram channel accounts. This may result in delays or interruptions in automations, Live Chat updates, and other real-time features linked to Instagram. Our team has reported the issue to Meta and is actively monitoring the situation while awaiting their response. 

We’ll keep you updated here as soon as we have more information. Thank you for your patience and understanding. May 29, 15:07:32 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 20 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re aware that Instagram automation webhooks may not be received, causing automations to fail to trigger as expected. Our team is actively investigating whether the issue stems from our side or Meta&#039;s..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:03:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re currently aware of an issue affecting the reception of webhooks for some Instagram channel accounts. This may result in delays or interruptions in automations, Live Chat updates, and other real-time features linked to Instagram. Our team has reported the issue to Meta and is actively monitoring the situation while awaiting their response. 

We’ll keep you updated here as soon as we have more information. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:07:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 25 May 2025 18:55:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cmb40p7qa000xivtixiokefxe</link>
  <guid>https://status.manychat.com/incident/cmb40p7qa000xivtixiokefxe</guid>
</item>

<item>
  <title>Unable to Link Manychat App to Meta Ads / Facebook Ads Manager</title>
  <description>
    Type: Incident
    Duration: 5 days, 6 hours and 32 minutes

    Affected Components: 3rd party: Instagram API, 3rd party: Facebook API
    Apr 23, 16:30:00 GMT+0 - Investigating - We’re aware of an issue where users cannot link the Manychat app to Meta Ads and Facebook Ads Manager. Our team is actively investigating the root cause in collaboration with Meta to determine whether the problem lies on their side or ours. We’ll share updates as soon as we have more information. Thank you for your patience. Apr 28, 23:02:07 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 6 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We’re aware of an issue where users cannot link the Manychat app to Meta Ads and Facebook Ads Manager. Our team is actively investigating the root cause in collaboration with Meta to determine whether the problem lies on their side or ours. We’ll share updates as soon as we have more information. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:02:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 23 Apr 2025 16:30:00 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm9u62p7g001gkbbpyyp18hi4</link>
  <guid>https://status.manychat.com/incident/cm9u62p7g001gkbbpyyp18hi4</guid>
</item>

<item>
  <title>Messages fail to send for Instagram and Messenger. Disabling any running campaigns is recommended</title>
  <description>
    Type: Incident
    Duration: 18 hours and 33 minutes

    Affected Components: 3rd party: Facebook API, 3rd party: Instagram API, Manychat: Message sending
    Mar 25, 13:34:13 GMT+0 - Investigating - We are currently investigating this incident. Mar 25, 13:41:59 GMT+0 - Identified - The issue was reported to Meta engineers. Mar 25, 14:54:52 GMT+0 - Resolved - This incident has been resolved. Mar 25, 13:52:19 GMT+0 - Monitoring - The issue was reported to Meta. Mar 25, 15:14:27 GMT+0 - Identified - The issue resumed to happen and has been reported to Meta again. Mar 26, 08:07:37 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:34:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:41:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue was reported to Meta engineers..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:54:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:52:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The issue was reported to Meta..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:14:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue resumed to happen and has been reported to Meta again..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:07:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Mar 2025 13:34:13 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm8ojenxy000awymmw7efhutm</link>
  <guid>https://status.manychat.com/incident/cm8ojenxy000awymmw7efhutm</guid>
</item>

<item>
  <title>Queue overload, some accounts message sending is affected</title>
  <description>
    Type: Incident
    Duration: 23 minutes

    Affected Components: Manychat: Message sending
    Mar 11, 23:24:34 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 11, 23:47:29 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:24:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:47:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Mar 2025 23:24:34 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm854by19000169k3q1ou1q1l</link>
  <guid>https://status.manychat.com/incident/cm854by19000169k3q1ou1q1l</guid>
</item>

<item>
  <title>Planned Maintenance Notice</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Manychat: Sign In / Sign Up, Manychat: Web Application, Manychat: Growth Tools, Manychat: Message sending
    Mar 2, 14:00:00 GMT+0 - Identified - We will be performing scheduled maintenance on our underlying infrastructure on March 2nd from 6:00 AM to 7:00 AM UTC. Your account may be unavailable for a few seconds or minutes during this period. Once your account is back online, all paused automation (both inbound and outbound) will be swiftly processed.   
  
We apologize for any inconvenience and appreciate your patience as we improve our service. Mar 2, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 2, 14:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing scheduled maintenance on our underlying infrastructure on March 2nd from 6:00 AM to 7:00 AM UTC. Your account may be unavailable for a few seconds or minutes during this period. Once your account is back online, all paused automation (both inbound and outbound) will be swiftly processed.   
  
We apologize for any inconvenience and appreciate your patience as we improve our service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 2 Mar 2025 14:00:00 +0000</pubDate>
  <link>https://status.manychat.com/maintenance/cm7p7p8n3006ggjvj85en3glo</link>
  <guid>https://status.manychat.com/maintenance/cm7p7p8n3006ggjvj85en3glo</guid>
</item>

<item>
  <title>Connecting Instagram/Facebook Messenger channel returns an error</title>
  <description>
    Type: Incident
    Duration: 4 hours and 42 minutes

    Affected Components: Manychat: Sign In / Sign Up
    Feb 27, 17:13:23 GMT+0 - Identified - The issue is caused by a change on Meta&#039;s side. We&#039;re currently waiting for the fix. Feb 27, 18:59:47 GMT+0 - Identified - Meta team have identified the issue and are landing a fix. Feb 27, 21:55:05 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:13:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue is caused by a change on Meta&#039;s side. We&#039;re currently waiting for the fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:59:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Meta team have identified the issue and are landing a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:55:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 27 Feb 2025 17:13:23 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm7nlsdit005bpcq0tr9lcr3v</link>
  <guid>https://status.manychat.com/incident/cm7nlsdit005bpcq0tr9lcr3v</guid>
</item>

<item>
  <title>Instagram and Messenger messaging partial outage </title>
  <description>
    Type: Incident
    Duration: 4 hours and 47 minutes

    Affected Components: Manychat: Message sending
    Feb 26, 22:19:56 GMT+0 - Resolved - The issue has been resolved. Feb 26, 22:19:56 GMT+0 - Resolved - This incident has been resolved. Feb 26, 17:33:12 GMT+0 - Investigating - We are currently investigating this incident. Feb 26, 17:46:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:19:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:19:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:33:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:46:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 26 Feb 2025 17:33:12 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm7m7207l0019hneyetn2w2o4</link>
  <guid>https://status.manychat.com/incident/cm7m7207l0019hneyetn2w2o4</guid>
</item>

<item>
  <title>Instagram issue: No available posts in the posts picker.</title>
  <description>
    Type: Incident
    Duration: 9 hours and 21 minutes

    Affected Components: 3rd party: Instagram API
    Feb 19, 08:24:18 GMT+0 - Resolved - This incident has been resolved. Feb 18, 23:03:14 GMT+0 - Monitoring - The issue with Instagram posts not appearing in the post picker should now be resolved. We are currently monitoring the situation to ensure everything is functioning as expected. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:24:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:03:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The issue with Instagram posts not appearing in the post picker should now be resolved. We are currently monitoring the situation to ensure everything is functioning as expected. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Feb 2025 23:03:14 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm7b3bmht0090o0zfywq6c6ny</link>
  <guid>https://status.manychat.com/incident/cm7b3bmht0090o0zfywq6c6ny</guid>
</item>

<item>
  <title>Instagram messages deliverability issue</title>
  <description>
    Type: Incident
    Duration: 2 hours and 50 minutes

    Affected Components: 3rd party: Instagram API
    Dec 17, 04:35:40 GMT+0 - Resolved - This incident has been resolved. Dec 17, 01:45:56 GMT+0 - Identified - Update: Meta has confirmed the incident on their Status Page: &lt;https://metastatus.com/ig-messenger&gt;

  
Some accounts might experience problems with sending and receiving messages on Instagram due to Meta outage.  
We are aware of the problem and are already investigating it.  
We will update you on this incident once there is any news on the subject. Dec 17, 03:17:56 GMT+0 - Monitoring - Meta reported that the issue should be fixed by now; we are currently monitoring the situation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:35:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:45:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Update: Meta has confirmed the incident on their Status Page: &lt;https://metastatus.com/ig-messenger&gt;

  
Some accounts might experience problems with sending and receiving messages on Instagram due to Meta outage.  
We are aware of the problem and are already investigating it.  
We will update you on this incident once there is any news on the subject..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:17:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Meta reported that the issue should be fixed by now; we are currently monitoring the situation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Dec 2024 01:45:56 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm4rsybwl000jejhtz1568myy</link>
  <guid>https://status.manychat.com/incident/cm4rsybwl000jejhtz1568myy</guid>
</item>

<item>
  <title>Elevated error rates for all Messenger, Instagram, and Whatsapp webhooks.</title>
  <description>
    Type: Incident
    Duration: 12 hours and 13 minutes

    Affected Components: 3rd party: Facebook API, 3rd party: WhatsApp API, 3rd party: Instagram API
    Dec 11, 22:00:00 GMT+0 - Resolved -  Dec 11, 18:04:57 GMT+0 - Investigating - We are currently investigating this incident. Dec 11, 20:02:53 GMT+0 - Monitoring - We have received confirmation from Meta and are currently monitoring the incident. We will update you as soon as there are any new developments. Please check the [Meta Status Page](https://metastatus.com/) for more information. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:04:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:02:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have received confirmation from Meta and are currently monitoring the incident. We will update you as soon as there are any new developments. Please check the [Meta Status Page](https://metastatus.com/) for more information..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 11 Dec 2024 18:04:57 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm4k7a8zd000g1kq760xi4fp4</link>
  <guid>https://status.manychat.com/incident/cm4k7a8zd000g1kq760xi4fp4</guid>
</item>

<item>
  <title>WhatsApp - Keyword Trigger may be Failing for Ad-Initiated Conversations</title>
  <description>
    Type: Incident
    Duration: 6 hours and 4 minutes

    Affected Components: 3rd party: WhatsApp API
    Nov 28, 08:26:30 GMT+0 - Identified - When a conversation is initiated through an Ad on Facebook or IG, the WhatsApp Keyword Trigger does not activate as expected, preventing the Automation from starting. Users must type the keyword again to receive the message. We are continuing to work on a fix for this incident.  Nov 28, 14:30:27 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:26:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  When a conversation is initiated through an Ad on Facebook or IG, the WhatsApp Keyword Trigger does not activate as expected, preventing the Automation from starting. Users must type the keyword again to receive the message. We are continuing to work on a fix for this incident. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:30:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 28 Nov 2024 08:26:30 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm411wat80006yqzgnpjlmwi1</link>
  <guid>https://status.manychat.com/incident/cm411wat80006yqzgnpjlmwi1</guid>
</item>

<item>
  <title>Meta issue: some of FB and IG messages fail to send on multiple accounts.</title>
  <description>
    Type: Incident
    Duration: 1 hour and 14 minutes

    Affected Components: 3rd party: Facebook API, 3rd party: Instagram API
    Oct 29, 12:38:50 GMT+0 - Investigating - Messages fail to send for Instagram and Messenger. Disabling any running campaigns is recommended.

We are currently investigating this incident.

&lt;https://downdetector.com/status/facebook/&gt;

&lt;https://downdetector.com/status/instagram/&gt; Oct 29, 13:26:06 GMT+0 - Monitoring - Meta APIs have returned to operational status; we are currently monitoring the situation. Oct 29, 13:53:10 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 14 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:38:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Messages fail to send for Instagram and Messenger. Disabling any running campaigns is recommended.

We are currently investigating this incident.

&lt;https://downdetector.com/status/facebook/&gt;

&lt;https://downdetector.com/status/instagram/&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:26:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Meta APIs have returned to operational status; we are currently monitoring the situation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:53:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 29 Oct 2024 12:38:50 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm2ufp86k000csn0n8om1zf2l</link>
  <guid>https://status.manychat.com/incident/cm2ufp86k000csn0n8om1zf2l</guid>
</item>

<item>
  <title>Messages fail to send for Instagram and Messenger. Disabling any running campaigns is recommended</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    
    Oct 17, 05:40:11 GMT+0 - Investigating - We are currently investigating this incident. Oct 17, 06:37:28 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:40:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:37:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 17 Oct 2024 05:40:11 +0000</pubDate>
  <link>https://status.manychat.com/incident/cm2cvgmi9000e3pi1afxdf3y9</link>
  <guid>https://status.manychat.com/incident/cm2cvgmi9000e3pi1afxdf3y9</guid>
</item>

<item>
  <title>Scheduled Maintenance: Sunday, 26.03.2023, from 8:00 to 8:30 am UTC</title>
  <description>
    Type: Maintenance
    Duration: 51 minutes

    Affected Components: Manychat: Web Application, Manychat: Message sending
    Mar 26, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 26, 08:00:00 GMT+0 - Identified - We inform you that there will be Scheduled Maintenance this Sunday (26.03.2023) **from 8:00 to 8:30 am UTC**.

We&#039;ll be performing major DB upgrades to ensure the speed, reliability, and security of the Platform.

During this Maintenance window, the website may be partially unavailable for some of the users for a couple of minutes. Please, note that this may cause a delay in the Bot processing for about 10 minutes.

We want to clarify that all messages and Bot replies will be processed after the end of the Scheduled Maintenance.

Thank you for understanding. Mar 26, 08:51:02 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 51 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We inform you that there will be Scheduled Maintenance this Sunday (26.03.2023) **from 8:00 to 8:30 am UTC**.

We&#039;ll be performing major DB upgrades to ensure the speed, reliability, and security of the Platform.

During this Maintenance window, the website may be partially unavailable for some of the users for a couple of minutes. Please, note that this may cause a delay in the Bot processing for about 10 minutes.

We want to clarify that all messages and Bot replies will be processed after the end of the Scheduled Maintenance.

Thank you for understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:51:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 26 Mar 2023 08:00:00 +0000</pubDate>
  <link>https://status.manychat.com/maintenance/clfmgmlv71341970vomeqqwxn41</link>
  <guid>https://status.manychat.com/maintenance/clfmgmlv71341970vomeqqwxn41</guid>
</item>

  </channel>
  </rss>