<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:engatiai.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://engatiai.instatus.com/history.atom"/>
  <title>engati Status - Incident history</title>
  <updated>2026-06-16T09:34:27.305+00:00</updated>
  <author>
    <name>engati</name>
  </author>
  
<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmqgg3y9q0m2w2jqjk6jk3res</id>
  <published>2026-06-16T09:34:27.305+00:00</published>
  <updated>2026-06-16T09:34:27.305+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmqgg3y9q0m2w2jqjk6jk3res"/>
  <title>Regional Outage on WhatsApp Calling</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 17 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> Whatsapp Calling API</p>
    <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>09:34:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing an issue affecting WhatsApp Calling services. Based on the information available, the issue appears to be on Meta&#039;s end and is impacting users in Uttar Pradesh (UP), Delhi, and the NCR region.

Meta&#039;s team is actively investigating the issue. Meanwhile, our team is closely following up with the provider and monitoring the situation to ensure we receive updates and resolution timelines at the earliest.

We will keep you informed as soon as we receive further updates..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The Meta team has implemented a fix and now the issue has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmqb09z5l0bpvqrdgrxsor477</id>
  <published>2026-06-12T14:12:23.639+00:00</published>
  <updated>2026-06-12T18:32:56.102+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmqb09z5l0bpvqrdgrxsor477"/>
  <title>Meta Incident - Messaging not working</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> Whatsapp Cloud API</p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:32:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  Meta has resolved issues affecting this. .</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>14:12:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  Meta is returning a 500 Internal Server Error while sending messages via the Meta API.  
  
We have reported the issue to the Meta Engineers to investigate it. We will provide an update as soon as we hear from Meta Engineers.  
  
We are monitoring the situation closely and waiting on Meta..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmpdlaakc05g9nrnaa6zghsfk</id>
  <published>2026-05-19T13:30:00.000+00:00</published>
  <updated>2026-05-19T13:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmpdlaakc05g9nrnaa6zghsfk"/>
  <title>AI Agent Search Responses</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> Bots (All channels)</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue affecting some text-agents where RAG-based searches may return empty responses.

This issue is impacting only a subset of customers and not all bots. Our engineering team is actively working on a fix and monitoring the affected flows closely..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>05:53:17</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>06:40:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmp5k8lkw00djqllp8pnkkyy3</id>
  <published>2026-05-14T14:04:49.200+00:00</published>
  <updated>2026-05-14T14:04:49.200+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmp5k8lkw00djqllp8pnkkyy3"/>
  <title>WhatsApp Messaging Service issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> Whatsapp Calling API</p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>14:04:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently aware of an issue impacting WhatsApp messaging due to an endpoint issue on our BSP provider’s end.

Our engineering team is actively investigating the issue and working closely with the provider to resolve it as quickly as possible. We’ll share another update as soon as we have more information..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>14:07:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmp417oo908cbpfd4kvm79mzr</id>
  <published>2026-05-13T12:24:30.782+00:00</published>
  <updated>2026-05-13T12:24:30.782+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmp417oo908cbpfd4kvm79mzr"/>
  <title>Voice Call Service Update</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 16 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> Whatsapp Calling API</p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>12:24:30</var> GMT+0</small><br /><strong>Investigating</strong> -
  Voice calling is currently not working due to ongoing maintenance on Dialog 360’s end.

Our team is actively checking with their support team and monitoring the situation closely. We’ll keep you updated as soon as we have more information.

Thank you for your patience and understanding..</p>
<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>05:04:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Maintenance/cmnznme0y02gvp74ejqie2sts</id>
  <published>2026-05-08T23:30:00.000+00:00</published>
  <updated>2026-05-08T23:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/maintenance/cmnznme0y02gvp74ejqie2sts"/>
  <title>Engati: Scheduled Maintenance </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> Admin Portal (agents.engati.ai), Bots (All channels)</p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  To improve platform reliability and performance, we will be conducting **scheduled maintenance** during the window below:

  
**Time:** 8th May 2026, 11:30 PM – 9th May 2026, 4:30 AM UTC (5:00 AM - 10:00 AM IST, 9th May)

### Impact during the maintenance window

During this time, the **Engati web portal and all bots/assistants will be unavailable** for agents, customers, and end users.

### What you can expect

* **Web Portal:** A maintenance page will be displayed when users attempt to access or sign in to the application
* **Mobile App:** The Engati app will not be accessible for support agents during sign-in
* **Website Widget (Website Agent):** The widget will not be visible to website visitors
* **Other Channels (Agents/Assistants):** Bots will not respond, and messages sent by end users during this window will not be stored

We apologize for the temporary inconvenience and appreciate your patience.

For any questions, please contact [**support@engati.ai**](mailto:support@engati.ai)..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>23:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmov167cf00nnznbdwo7tzahz</id>
  <published>2026-05-07T05:13:22.650+00:00</published>
  <updated>2026-05-27T05:48:26.867+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmov167cf00nnznbdwo7tzahz"/>
  <title>RCS Channel Template Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 days and 35 minutes</p>
    <p><strong>Affected Components:</strong> RCS Template</p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>05:48:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>05:13:22</var> GMT+0</small><br /><strong>Investigating</strong> -
  RCS templates created before 7 April 2026 may be affected due to a recent revamp deployment on the RBM provider side for the RCS channel. We are actively working with the provider to resolve the issue..</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>08:13:43</var> GMT+0</small><br /><strong>Identified</strong> -
  The RCS team has identified the issue affecting this. We are continuously following up with the provider for resolution and further updates..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmnsp5hdt011hwdiiavtzhnu4</id>
  <published>2026-04-10T09:21:42.349+00:00</published>
  <updated>2026-04-10T09:21:42.349+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmnsp5hdt011hwdiiavtzhnu4"/>
  <title>Embedded Signup issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> META infrastructure</p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>09:21:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  Meta has reported an issue causing significant disruptions impacting Embedded Signup.

Their engineering teams have identified the root cause and are currently deploying a fix. We will share another update as soon as more information becomes available.

In the meantime, please refer to the [Meta Status Page](https://metastatus.com/whatsapp-business-api) and subscribe for real-time updates..</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>14:44:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmnpw4kxe0q30hz61f3fvu7ca</id>
  <published>2026-04-08T10:13:39.051+00:00</published>
  <updated>2026-04-08T10:13:53.280+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmnpw4kxe0q30hz61f3fvu7ca"/>
  <title>Issue Affecting RCS Broadcast Messages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> RCS messaging</p>
    <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:13:53</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>12:49:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:13:39</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently facing a problem with sending broadcast messages via the RCS channel, caused by an issue with the VI APIs we rely on. Our team is working to resolve this as quickly as possible. Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmn3lgpm301akc5v24uhsjo5m</id>
  <published>2026-03-23T19:44:13.443+00:00</published>
  <updated>2026-03-23T19:44:13.443+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmn3lgpm301akc5v24uhsjo5m"/>
  <title>Portal login issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 12 minutes</p>
    <p><strong>Affected Components:</strong> Admin Portal (agents.engati.ai)</p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>19:44:13</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>20:54:10</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>20:55:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00ay4oqv0hhjb1yd</id>
  <published>2026-02-11T08:43:00.000+00:00</published>
  <updated>2026-02-11T08:43:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00ay4oqv0hhjb1yd"/>
  <title>Email Delivery Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>08:43:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing issues with email services. This is due to a problem with our email integration partner, SendGrid.

Our team is actively working with the partner to resolve the issue as quickly as possible. We will share updates as soon as more information becomes available..</p>
<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>18:44:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00av4oqvdiqqfz4x</id>
  <published>2026-02-04T08:00:00.000+00:00</published>
  <updated>2026-02-04T08:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00av4oqvdiqqfz4x"/>
  <title>Issues with contact list upload</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing an issue affecting contact list uploads.  

Our team is investigating and working to resolve the issue as quickly as possible. We’ll share updates here as we have more information..</p>
<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>09:21:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00as4oqvbknac11g</id>
  <published>2026-01-20T12:44:00.000+00:00</published>
  <updated>2026-01-20T12:44:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00as4oqvbknac11g"/>
  <title>Some disruptions to WhatsApp API Messaging Service</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>12:44:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently checking with our business service provider, dialog 360. They are actively investigating the matter, we will get back with updates.</p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>13:24:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00ap4oqv73avgoq6</id>
  <published>2026-01-08T14:30:00.000+00:00</published>
  <updated>2026-01-08T14:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00ap4oqv73avgoq6"/>
  <title>Chat Visibility Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue where chats are not currently visible. Our technical team is reviewing the situation and taking steps to resolve it. Further updates will be provided shortly..</p>
<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>05:29:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00am4oqv6ntqfhbk</id>
  <published>2025-11-21T05:46:00.000+00:00</published>
  <updated>2025-11-21T05:46:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00am4oqv6ntqfhbk"/>
  <title>Broadcast Analytics Service Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>05:46:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re currently experiencing an outage affecting the Broadcast Analytics service. Our technical team is actively investigating the issue. We&#039;ll share updates as soon as more information becomes available.

Thank you for your patience..</p>
<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>06:20:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00aj4oqvf3grgwcs</id>
  <published>2025-11-18T12:38:00.000+00:00</published>
  <updated>2025-11-18T12:38:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00aj4oqvf3grgwcs"/>
  <title>Service Downtime due to file service provider: Cloudflare</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:38:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing issues with the file upload feature, AI agents (voice/text) due to a partial outage with our file upload provider, Cloudflare.

If you are affected by this, please reach out to us at support@engati.com for assistance..</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>05:17:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00ah4oqv0z6l9orq</id>
  <published>2025-09-17T04:17:00.000+00:00</published>
  <updated>2025-09-17T04:17:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00ah4oqv0z6l9orq"/>
  <title>Portal downtime</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>04:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The portal and bot functionalities were temporarily impacted due to downtime at our cloud service provider (AWS). 

The issue has now been resolved, and all services are running normally..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00af4oqv7lufdtqe</id>
  <published>2025-09-16T12:40:00.000+00:00</published>
  <updated>2025-09-16T12:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00af4oqv7lufdtqe"/>
  <title>Messages tab loading</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>12:40:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We noticed that the messages tab was temporarily not loading user chat history. 

This was due to our weekly deployment. The issue has now been resolved, and you should be able to access the chat history without any further disruptions..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00ad4oqv2dbg2sja</id>
  <published>2025-09-09T13:30:00.000+00:00</published>
  <updated>2025-09-09T13:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00ad4oqv2dbg2sja"/>
  <title>Downtime on website bots</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The website bots were not functioning.

We have implemented a fix to address the issue and it is resolved now..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00ab4oqva49369nc</id>
  <published>2025-07-16T05:30:00.000+00:00</published>
  <updated>2025-07-16T05:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00ab4oqva49369nc"/>
  <title>Experiencing delay in Broadcast</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are experiencing some issue where the broadcast triggered from the portal are getting delivered after some delay. The team is actively checking this and we will update on the status..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bjv00a84oqv4jvz46en</id>
  <published>2025-06-10T10:10:00.000+00:00</published>
  <updated>2025-06-10T10:10:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bjv00a84oqv4jvz46en"/>
  <title>Open AI incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>10:10:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Open AI has reported partial degradation on the performance of their APIs.

Status page: https://status.openai.com/.</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>05:10:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bju00a44oqvhiq43qu3</id>
  <published>2025-05-28T09:42:00.000+00:00</published>
  <updated>2025-05-28T09:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bju00a44oqvhiq43qu3"/>
  <title>Meta incident: Message delivery of carousel templates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>09:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue that impacts the sending of carousel templates.

The error message is:

&quot;Carousel template messages require interactive template to be enabled.&quot;

We are monitoring the situation closely and awaiting Meta&#039;s response.

Meta status page: https://metastatus.com/whatsapp-business-api.</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>12:52:18</var> GMT+0</small><br /><strong>Resolved</strong> -
  META has confirmed that the issue has been resolved, as updated on their status page: https://metastatus.com/whatsapp-business-api..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>12:50:03</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Meta Engineering team has identified the root cause of the issue and is diligently working towards a solution.
We will provide another update as soon as additional information is available from Meta..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bju00a14oqv4q6q9zvf</id>
  <published>2025-03-26T09:28:00.000+00:00</published>
  <updated>2025-03-26T09:28:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bju00a14oqv4q6q9zvf"/>
  <title>Template creation issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>09:28:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue that is impacting the creation of message templates. Dialog 360 is currently investigating it. 
We&#039;ll update again as soon as we have more information..</p>
<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>11:54:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bju009y4oqv6aglfcni</id>
  <published>2025-03-12T06:46:00.000+00:00</published>
  <updated>2025-03-12T06:46:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bju009y4oqv6aglfcni"/>
  <title>Slight or intermittent disruption - Incoming messages issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>06:46:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  META is currently experiencing some disruptions that impact receiving incoming messages on WhatsApp Cloud API. This issue started on March 5th at 8 AM GMT, and their engineering teams are investigating it. 

We will provide an update if additional information is available.

Meta status page: https://metastatus.com/whatsapp-business-api.</p>
<p><small>Mar <var data-var='date'> 13</var>, <var data-var='time'>04:37:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bju009v4oqv35loasud</id>
  <published>2025-02-06T09:22:00.000+00:00</published>
  <updated>2025-02-06T09:22:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bju009v4oqv35loasud"/>
  <title>File Upload Service Downtime</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>09:22:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing issues with the file upload feature due to a partial outage with our file upload provider, Cloudflare.

If you are affected by this, please reach out to us at support@engati.com for assistance..</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>10:47:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:engatiai.instatus.com,2005:Incident/cmmud5bju009r4oqv663bh76b</id>
  <published>2025-02-05T05:05:00.000+00:00</published>
  <updated>2025-02-05T05:05:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://engatiai.instatus.com/incident/cmmud5bju009r4oqv663bh76b"/>
  <title>[Investigating]​ 360dialog - Some disruptions to Cloud API messaging</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>05:05:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of an issue affecting Cloud API numbers, specifically impacting the messaging service for incoming messages.
Dialog 360&#039;s engineering team is actively investigating the root cause. We will share an update as soon as more information becomes available..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>10:56:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  We would like to inform that the outage has now been addressed for the most part, and the API numbers have resumed functioning.

We also want to provide you with a clear understanding of what happened and how 360Dialog is handling the situation.

What Happened:
Around 12:00 AM GMT, Meta switched from per-number webhooks to per-WABA webhooks without prior notice.
360Dialog identified the issue, alerted Meta, and began working to minimize the impact.
Meta is still finalizing a permanent fix.
For more details, you can refer to Meta’s official status page: Meta Status - WhatsApp Business API..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>08:43:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dialog 360 has 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 &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 8 hours. We will provide another update within 4 hours or sooner if additional information is available.&quot;

They will try and do a fix from their end in the next 1-2 hrs while Meta figures out a long-term fix..</p>

        ]]>
  </content>
</entry>

</feed>