<?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>WeSpeak Status - Incident history</title>
    <link>https://wespeak.instatus.com</link>
    <description>WeSpeak</description>
    <pubDate>Sat, 10 Oct 2026 14:00:00 +0000</pubDate>
    
<item>
  <title>Delays in WhatsApp message processing</title>
  <description>
    Type: Incident
    Duration: 1 hour and 23 minutes

    Affected Components: Asistente Virtual, Panel CRM
    Oct 10, 15:23:26 GMT+0 - Resolved - Our follow-up checks confirm that WhatsApp message processing and Virtual Assistant replies have recovered. The delayed messages we were tracking have been processed, and recent replies have been confirmed delivered. This incident is now resolved. Thank you for your patience. Oct 10, 15:05:10 GMT+0 - Monitoring - Our latest checks show that incoming WhatsApp messages and Virtual Assistant replies are processing normally again. The delayed messages we were tracking have been processed, and recent replies have been confirmed delivered. We are monitoring recovery and checking for any remaining delays before marking this incident resolved. Thank you for your patience. Oct 10, 14:00:00 GMT+0 - Investigating - We are investigating delays affecting incoming WhatsApp messages and Virtual Assistant replies. Some messages are waiting to be processed, which may cause conversations in the CRM panel to update late.

Delays were observed from approximately 14:00 UTC on October 10, 2026. In the cases reviewed, waiting times exceeded 20 minutes. Processing has partially resumed, but our latest checks still show messages waiting to be processed; full recovery has not been confirmed.

The CRM panel remained accessible during our checks. The cause of the processing delays is still under investigation. We apologize for the inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:23:26</var> GMT+0</small><br><strong>Resolved</strong> -
  Our follow-up checks confirm that WhatsApp message processing and Virtual Assistant replies have recovered. The delayed messages we were tracking have been processed, and recent replies have been confirmed delivered. This incident is now resolved. Thank you for your patience..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:05:10</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our latest checks show that incoming WhatsApp messages and Virtual Assistant replies are processing normally again. The delayed messages we were tracking have been processed, and recent replies have been confirmed delivered. We are monitoring recovery and checking for any remaining delays before marking this incident resolved. Thank you for your patience..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating delays affecting incoming WhatsApp messages and Virtual Assistant replies. Some messages are waiting to be processed, which may cause conversations in the CRM panel to update late.

Delays were observed from approximately 14:00 UTC on October 10, 2026. In the cases reviewed, waiting times exceeded 20 minutes. Processing has partially resumed, but our latest checks still show messages waiting to be processed; full recovery has not been confirmed.

The CRM panel remained accessible during our checks. The cause of the processing delays is still under investigation. We apologize for the inconvenience..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 14:00:00 +0000</pubDate>
  <link>https://wespeak.instatus.com/incident/cmv2i95j8072g1bno4ll4uzm3</link>
  <guid>https://wespeak.instatus.com/incident/cmv2i95j8072g1bno4ll4uzm3</guid>
</item>

<item>
  <title>Service disruption — Virtual Assistant &amp; CRM Panel (third-party provider)</title>
  <description>
    Type: Incident
    Duration: 5 hours and 50 minutes

    Affected Components: Panel CRM, Asistente Virtual
    Sep 18, 22:06:00 GMT+0 - Resolved - This incident has been resolved. Our infrastructure provider confirmed at 21:17 UTC that the underlying issue was fixed on their end, and our messaging pipeline has been operating normally since 18:09 UTC (15:09 Argentina time): incoming messages are reaching the platform immediately, the Virtual Assistant is replying, and agents can send replies from the CRM panel. All messages delayed during the two disruption windows (16:16–16:40 UTC and 17:51–18:09 UTC) were processed. We apologize for the inconvenience and thank you for your patience. Sep 18, 18:52:00 GMT+0 - Monitoring - Our infrastructure provider reports that a fix has been deployed on their side and that they are monitoring to confirm the system is fully operational. Since 18:09 UTC (15:09 Argentina time) our messaging pipeline has been operating normally, with no further delays: incoming messages are reaching the platform immediately, the Virtual Assistant is replying, and agents can send replies from the CRM panel. We will keep this incident in monitoring until the provider confirms full resolution, and will post a final update then. Sep 18, 18:09:00 GMT+0 - Monitoring - Service has recovered again and all messages delayed during the disruption have been processed. Today the messaging pipeline was interrupted during two windows: 16:16–16:40 UTC and 17:51–18:09 UTC (13:16–13:40 and 14:51–15:09 Argentina time). Incoming messages received during those windows reached the platform late, and the Virtual Assistant replied late. Our infrastructure provider has not yet confirmed full resolution on their side, so we are monitoring closely and will post a final update once they do. Sep 18, 17:51:00 GMT+0 - Investigating - The disruption at our infrastructure provider has recurred. Incoming messages are again delayed before reaching the platform and the Virtual Assistant is not replying while the delay lasts. Messages are queued, not lost. We are monitoring the provider&#039;s incident and will post an update as soon as service recovers. Sep 18, 16:40:00 GMT+0 - Monitoring - Service has recovered: incoming messages are reaching the platform again, the Virtual Assistant is replying, and the messages delayed during the disruption have been processed. Our infrastructure provider has not yet closed its incident, so we continue to monitor closely. Sep 18, 16:16:00 GMT+0 - Investigating - One of our infrastructure providers is experiencing degraded function execution. As a result, incoming messages are being delayed before they reach the platform, the Virtual Assistant is not replying while the delay lasts, and replies sent by agents from the CRM panel are also delayed. No messages are lost: they are queued and will be processed once the provider recovers. Our team is monitoring the provider&#039;s incident closely. We apologize for the inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>22:06:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. Our infrastructure provider confirmed at 21:17 UTC that the underlying issue was fixed on their end, and our messaging pipeline has been operating normally since 18:09 UTC (15:09 Argentina time): incoming messages are reaching the platform immediately, the Virtual Assistant is replying, and agents can send replies from the CRM panel. All messages delayed during the two disruption windows (16:16–16:40 UTC and 17:51–18:09 UTC) were processed. We apologize for the inconvenience and thank you for your patience..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>18:52:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our infrastructure provider reports that a fix has been deployed on their side and that they are monitoring to confirm the system is fully operational. Since 18:09 UTC (15:09 Argentina time) our messaging pipeline has been operating normally, with no further delays: incoming messages are reaching the platform immediately, the Virtual Assistant is replying, and agents can send replies from the CRM panel. We will keep this incident in monitoring until the provider confirms full resolution, and will post a final update then..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>18:09:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Service has recovered again and all messages delayed during the disruption have been processed. Today the messaging pipeline was interrupted during two windows: 16:16–16:40 UTC and 17:51–18:09 UTC (13:16–13:40 and 14:51–15:09 Argentina time). Incoming messages received during those windows reached the platform late, and the Virtual Assistant replied late. Our infrastructure provider has not yet confirmed full resolution on their side, so we are monitoring closely and will post a final update once they do..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>17:51:00</var> GMT+0</small><br><strong>Investigating</strong> -
  The disruption at our infrastructure provider has recurred. Incoming messages are again delayed before reaching the platform and the Virtual Assistant is not replying while the delay lasts. Messages are queued, not lost. We are monitoring the provider&#039;s incident and will post an update as soon as service recovers..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>16:40:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Service has recovered: incoming messages are reaching the platform again, the Virtual Assistant is replying, and the messages delayed during the disruption have been processed. Our infrastructure provider has not yet closed its incident, so we continue to monitor closely..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>16:16:00</var> GMT+0</small><br><strong>Investigating</strong> -
  One of our infrastructure providers is experiencing degraded function execution. As a result, incoming messages are being delayed before they reach the platform, the Virtual Assistant is not replying while the delay lasts, and replies sent by agents from the CRM panel are also delayed. No messages are lost: they are queued and will be processed once the provider recovers. Our team is monitoring the provider&#039;s incident closely. We apologize for the inconvenience..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 18 Sep 2026 16:16:00 +0000</pubDate>
  <link>https://wespeak.instatus.com/incident/cmu7aglmo0hjl1npctmd1fekv</link>
  <guid>https://wespeak.instatus.com/incident/cmu7aglmo0hjl1npctmd1fekv</guid>
</item>

<item>
  <title>Service disruption — Virtual Assistant &amp; CRM Panel (third-party provider)</title>
  <description>
    Type: Incident
    Duration: 5 hours and 17 minutes

    Affected Components: Asistente Virtual, Panel CRM
    Sep 4, 23:47:00 GMT+0 - Resolved - This incident has been resolved. Our infrastructure provider confirmed that the underlying issue was fixed on their end, and the service has been operating normally since: incoming messages are reaching the platform, the Virtual Assistant is replying, and agents can send replies from the CRM panel. Messages that were delayed during the incident have since been processed. We apologize for the inconvenience and thank you for your patience. Sep 4, 18:51:00 GMT+0 - Monitoring - Service is recovering. Messages are reaching the platform again, the Virtual Assistant is replying, and agents are able to send replies from the CRM panel. Some delays may still occur while pending messages are processed. We are monitoring closely and will post a final update once full recovery is confirmed. Sep 4, 18:49:00 GMT+0 - Investigating - The impact is broader than initially reported. The outage at one of our infrastructure providers is affecting the entire messaging pipeline: incoming messages are not reaching the platform, the Virtual Assistant is not able to reply, and agents cannot send replies to guests from the CRM panel. Our team is working to restore normal service as soon as possible, and we will post a new update as soon as we have more information. We apologize for the inconvenience. Sep 4, 18:30:00 GMT+0 - Investigating - One of our infrastructure providers is currently experiencing an outage. As a result, the Virtual Assistant is not able to reply to incoming messages. Our team is aware and working to restore normal service as soon as possible. We will share an update as soon as we have more information. We apologize for the inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>23:47:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. Our infrastructure provider confirmed that the underlying issue was fixed on their end, and the service has been operating normally since: incoming messages are reaching the platform, the Virtual Assistant is replying, and agents can send replies from the CRM panel. Messages that were delayed during the incident have since been processed. We apologize for the inconvenience and thank you for your patience..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:51:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Service is recovering. Messages are reaching the platform again, the Virtual Assistant is replying, and agents are able to send replies from the CRM panel. Some delays may still occur while pending messages are processed. We are monitoring closely and will post a final update once full recovery is confirmed..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:49:00</var> GMT+0</small><br><strong>Investigating</strong> -
  The impact is broader than initially reported. The outage at one of our infrastructure providers is affecting the entire messaging pipeline: incoming messages are not reaching the platform, the Virtual Assistant is not able to reply, and agents cannot send replies to guests from the CRM panel. Our team is working to restore normal service as soon as possible, and we will post a new update as soon as we have more information. We apologize for the inconvenience..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  One of our infrastructure providers is currently experiencing an outage. As a result, the Virtual Assistant is not able to reply to incoming messages. Our team is aware and working to restore normal service as soon as possible. We will share an update as soon as we have more information. We apologize for the inconvenience..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 4 Sep 2026 18:30:00 +0000</pubDate>
  <link>https://wespeak.instatus.com/incident/cmtnazqp10e0m13qquqb0dcp2</link>
  <guid>https://wespeak.instatus.com/incident/cmtnazqp10e0m13qquqb0dcp2</guid>
</item>

<item>
  <title>Issues sending messages with images</title>
  <description>
    Type: Incident
    Duration: 2 hours and 45 minutes

    Affected Components: Asistente Virtual, Panel CRM
    Jun 16, 17:24:59 GMT+0 - Resolved - This incident has been resolved. Jun 16, 16:54:08 GMT+0 - Monitoring - &gt; We have identified the cause of the issue on the WhatsApp messaging provider (Meta) and are seeing a gradual recovery: sending messages with images —from the Virtual Assistant and the CRM Panel— is now working in most cases. We continue to monitor until full normalization is confirmed. Text-only messages were never affected. Jun 16, 14:40:00 GMT+0 - Investigating - &gt; We are investigating an issue that prevents sending messages containing images over WhatsApp, both from the Virtual Assistant and the CRM Panel. Text-only messages are not affected. The issue originates with the WhatsApp messaging provider (Meta), which is intermittently failing to download the attached images. We are working to mitigate the impact and restore the service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>17:24:59</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>16:54:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  &gt; We have identified the cause of the issue on the WhatsApp messaging provider (Meta) and are seeing a gradual recovery: sending messages with images —from the Virtual Assistant and the CRM Panel— is now working in most cases. We continue to monitor until full normalization is confirmed. Text-only messages were never affected..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>14:40:00</var> GMT+0</small><br><strong>Investigating</strong> -
  &gt; We are investigating an issue that prevents sending messages containing images over WhatsApp, both from the Virtual Assistant and the CRM Panel. Text-only messages are not affected. The issue originates with the WhatsApp messaging provider (Meta), which is intermittently failing to download the attached images. We are working to mitigate the impact and restore the service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 16 Jun 2026 14:40:00 +0000</pubDate>
  <link>https://wespeak.instatus.com/incident/cmqgujtl100u52opcjvjcenc6</link>
  <guid>https://wespeak.instatus.com/incident/cmqgujtl100u52opcjvjcenc6</guid>
</item>

<item>
  <title>Whatsapp API services are down</title>
  <description>
    Type: Incident
    Duration: 3 hours and 20 minutes

    Affected Components: Panel CRM, Asistente Virtual
    Jun 12, 17:19:56 GMT+0 - Resolved - This incident from meta has been resolved. Jun 12, 16:51:34 GMT+0 - Monitoring - Meta is recovering from its earlier outage.  
  
&lt;https://metastatus.com/whatsapp-business-api&gt; Jun 12, 14:00:00 GMT+0 - Identified - Several users are reporting that WhatsApp messages are neither sending nor receiving. We have confirmed that Meta itself is currently experiencing issues. The problem will be resolved once Meta fixes it.

To actively track the incident on Meta&#039;s end, here is the link: &lt;https://metastatus.com/whatsapp-business-api&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>17:19:56</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident from meta has been resolved..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>16:51:34</var> GMT+0</small><br><strong>Monitoring</strong> -
  Meta is recovering from its earlier outage.  
  
&lt;https://metastatus.com/whatsapp-business-api&gt;.</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Several users are reporting that WhatsApp messages are neither sending nor receiving. We have confirmed that Meta itself is currently experiencing issues. The problem will be resolved once Meta fixes it.

To actively track the incident on Meta&#039;s end, here is the link: &lt;https://metastatus.com/whatsapp-business-api&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 12 Jun 2026 14:00:00 +0000</pubDate>
  <link>https://wespeak.instatus.com/incident/cmqb2k2l40a1onu9z06g02bnx</link>
  <guid>https://wespeak.instatus.com/incident/cmqb2k2l40a1onu9z06g02bnx</guid>
</item>

  </channel>
  </rss>