Resolved

WhatsApp session disruption

We experienced a general service disruption early this morning that impacted WhatsApp numbers' ability to send and receive messages and notify webhook events during the time numbers were not online.

The problem has been resolved and everything is back operational now.

Long story short, there was an update on WhatsApp's end that prevented numbers from properly initialising communication with WhatsApp systems in order to exchange messages.

The issue was first detected around 8.30 am and it was fully resolved around 1 pm CET. 
Some numbers may have experience downtime for a couple of hours, while others less than an hour. Unfortunately, some numbers may have lost authorization during the outage.

In that case, you simply need to reconnect the numbers by scanning the QR again. The API and Web Console services were not impacted, thus any messages pushed to the API were stored in the queue and will be delivered as soon as the number session is back online. The same applies to pending webhook events.

Finally, we have remediated the issue and implemented the needed enhancements to prevent a similar scenario to happen in the future, which was an edge-case scenario.

At the moment, no further issues have been detected, but as always, if you need any help please don't hesitate to contact us.

We sincerely apologize for any inconvenience.

Resolved

Outage in the API + Web chat

Due to a collateral side effect during an extraordinary service upgrade, the API and Web chat services were intermittently failing for about 20 minutes, during which messages ingestion and web access may have failed.

Our team has already fixed the issue and we will take the needed steps to prevent this to happen in the future.

Our sincerest apologies and thank you for your understanding.