<?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>BizMagnets Status - Incident history</title>
    <link>https://bizmagnets.instatus.com</link>
    <description>BizMagnets</description>
    <pubDate>Wed, 5 Feb 2025 00:02:00 +0000</pubDate>
    
<item>
  <title>Some disruptions to Cloud API messaging</title>
  <description>
    Type: Incident
    Duration: 15 hours and 9 minutes

    Affected Components: 360Dialogbox API, Meta Cloud API
    Feb 5, 00:02:00 GMT+0 - Investigating - We are aware of an issue affecting Cloud API numbers, specifically impacting the messaging service for incoming messages.

Our engineering team working closely with 360dialogbox team in investigating the root cause. We will share an update as soon as more information becomes available. Feb 5, 08:31:57 GMT+0 - Identified - We have identified the cause of message delays affecting Cloud API numbers as a Meta issue and we’re awaiting their response.

Meta have acknowledged this issue on [**their status page**](https://metastatus.com/whatsapp-business-api) _&quot;Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix and the expected deployment time is in 8hours. We will provide another update within 4 hours or sooner if additional information is available.&quot;_

Our engineering team is preparing a workaround to mitigate the issue for WhatsApp Business Accounts with a single number until Meta resolves the issue on their side. Feb 5, 15:10:42 GMT+0 - Resolved - Meta has resolved the issue: &quot;We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused.&quot; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:02:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of an issue affecting Cloud API numbers, specifically impacting the messaging service for incoming messages.

Our engineering team working closely with 360dialogbox team in investigating the root cause. We will share an update as soon as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:31:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the cause of message delays affecting Cloud API numbers as a Meta issue and we’re awaiting their response.

Meta have acknowledged this issue on [**their status page**](https://metastatus.com/whatsapp-business-api) _&quot;Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix and the expected deployment time is in 8hours. We will provide another update within 4 hours or sooner if additional information is available.&quot;_

Our engineering team is preparing a workaround to mitigate the issue for WhatsApp Business Accounts with a single number until Meta resolves the issue on their side..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:10:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Meta has resolved the issue: &quot;We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused.&quot;.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 5 Feb 2025 00:02:00 +0000</pubDate>
  <link>https://bizmagnets.instatus.com/incident/cm6rgst6p002tmimg6hxp92ng</link>
  <guid>https://bizmagnets.instatus.com/incident/cm6rgst6p002tmimg6hxp92ng</guid>
</item>

<item>
  <title>Media Services Disruption</title>
  <description>
    Type: Incident
    Duration: 47 minutes

    Affected Components: BizMagnets Web Application, BizMagnets Mobile Application, BizMagnets Developer API
    Sep 17, 04:51:49 GMT+0 - Investigating - We are currently experiencing an issue with our media services. While existing media content remains accessible, new media or media messages cannot be sent or received at this time. Our team is actively investigating the problem and working to resolve it as quickly as possible.

We will provide further updates as soon as we have more information. Thank you for your patience and understanding. Sep 17, 05:38:46 GMT+0 - Resolved - We are pleased to inform you that the issue affecting our media services has been resolved. You should now be able to send and receive new media messages as well as access existing media content without any issues.

We apologize for any inconvenience this disruption may have caused and appreciate your patience while we worked to resolve the problem.

If you encounter any further issues or have any questions, please don’t hesitate to reach out to our support team.

Thank you for your understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 47 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:51:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing an issue with our media services. While existing media content remains accessible, new media or media messages cannot be sent or received at this time. Our team is actively investigating the problem and working to resolve it as quickly as possible.

We will provide further updates as soon as we have more information. Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:38:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We are pleased to inform you that the issue affecting our media services has been resolved. You should now be able to send and receive new media messages as well as access existing media content without any issues.

We apologize for any inconvenience this disruption may have caused and appreciate your patience while we worked to resolve the problem.

If you encounter any further issues or have any questions, please don’t hesitate to reach out to our support team.

Thank you for your understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Sep 2024 04:51:49 +0000</pubDate>
  <link>https://bizmagnets.instatus.com/incident/cm15yiv3h004r14fbowukyxl2</link>
  <guid>https://bizmagnets.instatus.com/incident/cm15yiv3h004r14fbowukyxl2</guid>
</item>

<item>
  <title>Application request limit reached</title>
  <description>
    Type: Incident
    Duration: 23 hours and 11 minutes

    Affected Components: 360Dialogbox API
    Sep 16, 08:20:08 GMT+0 - Identified - We are aware of an Application request limit reached issue that is impacting some activities on the 360dialog Hub and API. Our engineering team is currently investigating it. We do not currently have a resolution ETA but we&#039;ll update again as soon as possible. Sep 16, 08:20:08 GMT+0 - Monitoring - The issue is now mitigated and we are monitoring the situation. Sep 17, 07:30:57 GMT+0 - Resolved - The issue has been mitigated with no re-occurrence since 14:48 GMT+1 on 16/09/2024. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are aware of an Application request limit reached issue that is impacting some activities on the 360dialog Hub and API. Our engineering team is currently investigating it. We do not currently have a resolution ETA but we&#039;ll update again as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The issue is now mitigated and we are monitoring the situation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:30:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been mitigated with no re-occurrence since 14:48 GMT+1 on 16/09/2024..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 16 Sep 2024 08:20:08 +0000</pubDate>
  <link>https://bizmagnets.instatus.com/incident/cm14qiwz7000gb5ywdi78a3ah</link>
  <guid>https://bizmagnets.instatus.com/incident/cm14qiwz7000gb5ywdi78a3ah</guid>
</item>

<item>
  <title>Application request limit reached</title>
  <description>
    Type: Incident
    Duration: 1 day, 10 hours and 15 minutes

    Affected Components: 360Dialogbox API
    Sep 13, 08:20:00 GMT+0 - Identified - We are aware of an issue impacting some activities on the 360dialog Hub and API. Our engineering team is currently investigating it. We do not currently have a resolution ETA but we&#039;ll update again as soon as possible. Sep 14, 17:29:46 GMT+0 - Monitoring - API requests should no longer receive rate limit errors.  
WABA management operations have been restored.   Sep 14, 08:22:14 GMT+0 - Identified - In the meantime, we recommend using Meta Business Manager as a workaround for creating and submitting templates. Additionally, we advise refraining from performing migrations, onboarding, and template-related actions for now. This will help prevent the limit from being reached immediately once the issue is resolved and ensure a smoother experience when the systems are fully operational again.

We greatly appreciate your patience and understanding during this time, and we will continue to provide updates as soon as we have more information. Sep 14, 18:35:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 10 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are aware of an issue impacting some activities on the 360dialog Hub and API. Our engineering team is currently investigating it. We do not currently have a resolution ETA but we&#039;ll update again as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:29:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  API requests should no longer receive rate limit errors.  
WABA management operations have been restored.  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:22:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  In the meantime, we recommend using Meta Business Manager as a workaround for creating and submitting templates. Additionally, we advise refraining from performing migrations, onboarding, and template-related actions for now. This will help prevent the limit from being reached immediately once the issue is resolved and ensure a smoother experience when the systems are fully operational again.

We greatly appreciate your patience and understanding during this time, and we will continue to provide updates as soon as we have more information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:35:00&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, 13 Sep 2024 08:20:00 +0000</pubDate>
  <link>https://bizmagnets.instatus.com/incident/cm11vp2cx009660uhbcz7a4g2</link>
  <guid>https://bizmagnets.instatus.com/incident/cm11vp2cx009660uhbcz7a4g2</guid>
</item>

<item>
  <title>Major disruptions: WhatsApp Flows</title>
  <description>
    Type: Incident
    

    Affected Components: Meta Whatsapp Flows
    Aug 28, 17:30:00 GMT+0 - Resolved - We have resolved the issue impacting Flows sending and management on WhatsApp Flows. The service is now fully operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have resolved the issue impacting Flows sending and management on WhatsApp Flows. The service is now fully operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 28 Aug 2024 17:30:00 +0000</pubDate>
  <link>https://bizmagnets.instatus.com/incident/cm0dn77mn000jy8m0dhmaoz6m</link>
  <guid>https://bizmagnets.instatus.com/incident/cm0dn77mn000jy8m0dhmaoz6m</guid>
</item>

  </channel>
  </rss>