Status - Oct8ne

SERVICE STATUS

USA

EUROPE

All systems are operational

Past Events

23/7/2026 – AZURE Network Connectivity issue (WEST US)

On 23/7, AZURE experienced a series of connectivity issues, which caused high latency and difficulties accessing its services in the US West region. The impact was limited to network traffic entering or leaving the region; traffic that remained entirely within the region was not affected. The outage affected many customers in USA, and lasted approximately 3 hours. From 14:45h to 19h aprox. (Spanish time – UTC+2) Additional information: Already solved. *More info: https://azure.status.microsoft/en-us/status/history/

12/6/2026 – META high global disruptions

On 12/6, META experienced a degradation of its services that indirectly affected our customers. Meta experienced a global outage (major disruptions) across several of its services. This primarily affected messaging services due to issues with the META – Cloud API. The outage affected many customers worldwide, not just Oct8ne, and lasted approximately 3 hours. From 16h to 19h aprox. (Spanish time – UTC+2) Additional information: Already solved. *More info: https://status.360dialog.com/history/1 *More info: https://metastatus.com/whatsapp-business-api

20/1/2026 – 360Dialog services degradation

On 20/1, 360Dialog experienced a degradation of its services that indirectly affected our customers. Two incidents occurred in quick succession. According to ‘360Dialog’, the first incident caused the messaging system to crash, which meant that messages were not working in real time. This incident affected our customers (Eu & USA) for approximately one hour. From 13:45h to 14:45h aprox (Spanish time – UTC+1). The second incident, once the first had been resolved, only affected the sending of multimedia files for certain users. According to 360Dialog, the total issue had an impact from 13:45h to 22:30h aprox (Spanish time – UTC+1). Additional information: Already solved. *More info: https://status.360dialog.com/history/1

29/10/2025 – Azure’s services degradation

On 29/10, Azure experienced a degradation of its services that indirectly affected our customers. Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. According to Azure, the issue had an impact from 16:45h to 00:00h aprox (Spanish time – UTC+1). Additional information: Already solved. (Azure Track Id: YKYN-BWZ) *More info: https://azure.status.microsoft/en-us/status/history

09/10/2025 – Partial degradation of services

On 9/10, Azure experienced a partial degradation of its services that indirectly affected our customers. Affected customers experienced intermittent delays or wait times when accessing our services. According to Azure, the issue had an impact from 8:00h to 17:00h (Spanish time – UTC+1). Additional information: Already solved. (Azure Track Id: QKNQ-PB8) *More info: https://azure.status.microsoft/en-us/status/history

07/10/2025 – Degradation on Databases.

On 07/10 we experienced abnormal activity in our databases, which caused a degradation in the performance of some services. The issue had an impact from 17:00h to 19:30h (Spanish time – UTC+1). Additional information: Already solved

22/07/2025 – Degradation on EU servers.

On 22/07 we experienced two periods of instability in our EU servers, due to provider migration processes. It was fixed the same day at 13:00h. The issue had an impact from 11:50h to 12:05h and from 12.30h to 13.00h (Spanish time – UTC+2). Additional information: Already solved

05/02/2025 – Some disruption to Cloud API messaging

On 05/02, our partner 360Dialog detected an issue affecting Cloud API numbers. They quickly alerted Meta, who indeed confirmed the malfunction on their side. After a few hours Meta reported that it was resolved. It was fixed the same day at 15:30h PM. The issue had an impact from 1:00h AM to 15.30h AM. (Spanish time – UTC+2). Additional information: Already solved

30/07/2024 – Delivery API Service failed

On 30/07 we detected a failure in the template Delivery Service via API, due to a change in the delivery parameters. It was fixed the same day at 20h PM (Spanish time – UTC+2). Additional information: Already solved

16/07/2024 – Service partially disrupted, affecting web livechat.

There were interruptions of ‘livechat web’ service, from 8h AM to 14.30AM, due to an update of the software. (Spanish time – UTC+2). Additional information: Already solved

05/07/2024 – Bot Service Degradation

Bot service disrupted, from 5h AM to 8.30h AM. (Spanish time – UTC+2). Additional information: Already solved