<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:wespeak.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://wespeak.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://wespeak.instatus.com/history.atom"/>
  <title>WeSpeak Status - Incident history</title>
  <updated>2026-09-18T16:16:00.000+00:00</updated>
  <author>
    <name>WeSpeak</name>
  </author>
  
<entry>
  <id>tag:wespeak.instatus.com,2005:Incident/cmu7aglmo0hjl1npctmd1fekv</id>
  <published>2026-09-18T16:16:00.000+00:00</published>
  <updated>2026-09-18T18:52:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://wespeak.instatus.com/incident/cmu7aglmo0hjl1npctmd1fekv"/>
  <title>Service disruption — Virtual Assistant &amp; CRM Panel (third-party provider)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> Panel CRM, Asistente Virtual</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'>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'>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>
<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'>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'>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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:wespeak.instatus.com,2005:Incident/cmtnazqp10e0m13qquqb0dcp2</id>
  <published>2026-09-04T18:30:00.000+00:00</published>
  <updated>2026-09-04T18:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://wespeak.instatus.com/incident/cmtnazqp10e0m13qquqb0dcp2"/>
  <title>Service disruption — Virtual Assistant &amp; CRM Panel (third-party provider)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Asistente Virtual, Panel CRM</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>
<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: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'>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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:wespeak.instatus.com,2005:Incident/cmqgujtl100u52opcjvjcenc6</id>
  <published>2026-06-16T14:40:00.000+00:00</published>
  <updated>2026-06-16T14:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://wespeak.instatus.com/incident/cmqgujtl100u52opcjvjcenc6"/>
  <title>Issues sending messages with images</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Asistente Virtual, Panel CRM</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>
<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'>17:24:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:wespeak.instatus.com,2005:Incident/cmqb2k2l40a1onu9z06g02bnx</id>
  <published>2026-06-12T14:00:00.000+00:00</published>
  <updated>2026-06-12T16:51:34.295+00:00</updated>
  <link rel="alternate" type="text/html" href="https://wespeak.instatus.com/incident/cmqb2k2l40a1onu9z06g02bnx"/>
  <title>Whatsapp API services are down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> Panel CRM, Asistente Virtual</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>
<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>

        ]]>
  </content>
</entry>

</feed>