Ujumbe Global technical engineers resolving a service incident in the network operations centre
Services Restored – Preventive Actions in Progress

Incident transparency for every client we serve

Our technical operations team documents every Bulk SMS / Messaging API service event — what happened, why it happened, how it was recovered and what we are changing. Browse the calendar, open a report and tell us how your traffic was affected.

Reporting period

14 August 2026 – 31 August 2026

Service

Bulk SMS / Messaging API

Impact form deadline

12:00 PM EAT, 7 September 2026

Incident calendar

Only months with recorded events are shown. Select a highlighted date to open that day's report — each incident is a separate, downloadable document.

Events in 2026

2

Days since last reported event

62

Last major event

31 August 2026 — Bulk SMS API/HTTP Delivery Interruption

Reports

Data centre aisle with amber warning lights, heat haze and a temperature gauge in the red during the cooling failure

Incident #1

Phoenix Data Centre Infrastructure Outage

14 August 2026

On 14 August 2026, part of the underlying hosting infrastructure supporting the Bulk SMS and Messaging API environment experienced a temporary service interruption associated with an incident at the RadiusDC PHX-01 Data Center in Phoenix, Arizona.

Duration
Exact duration not confirmed in the available upstream incident report
Ownership
Third-Party / Upstream Data Centre
Services Restored – Further RFO pendingOpen report
Network rack with red link lights and a dashboard showing a dropped VPN tunnel and failed Bulk SMS API deliveries

Incident #2

Bulk SMS API/HTTP Delivery Interruption

31 August 2026

On 31 August 2026, the Bulk SMS API/HTTP service experienced a temporary interruption that affected message delivery and Delivery Receipt (DLR) processing.

Duration
5 hours 40 minutes
Ownership
Internal Messaging Infrastructure
Fully Resolved at 14:05 EATOpen report

Executive summary

During the reporting period, the Bulk SMS and Messaging API service experienced two separate incidents that affected service availability and message delivery. The incidents had different technical causes and were not related to one another.

Incident 1 – 14 August 2026: A third-party data-centre infrastructure event in Phoenix, Arizona affected underlying hosting services. The event involved utility disturbances and a sudden power interruption that affected the facility's cooling environment.

Incident 2 – 31 August 2026: A Bulk SMS API/HTTP delivery interruption affected message submission and Delivery Receipt (DLR) processing. The incident occurred during infrastructure improvements and was caused by disruption to the secure VPN/HTTP communication path between the messaging platform and the Mobile Network Operator (MNO) environment.

Both incidents were resolved, and service functionality was restored.

Were your messages affected?

Complete the Client Incident Impact Assessment and Recovery Request for your company. Your draft stays editable until it is finalised with a one-time SMS code — then it is locked, with the person who filled it and the person who finalised it recorded on the submission.

Open the impact form