Problems with MT (Outgoing) SMS

Update timeline

1. investigating Nov 02, 2026, 03:31 PM UTC

   We are investigating an issue affecting outgoing (MT) SMS. Messages may be delayed. Our team are working to identify the cause. We will post an update as soon as we have new information.

2. investigating Nov 02, 2026, 04:43 PM UTC

   We are still investigating the issue affecting outgoing (MT) and (MO) SMS traffic. Messages is still delayed. Our team is working to find the cause and restore normal delivery. We will post another update once we have more information.

3. investigating Nov 02, 2026, 05:01 PM UTC

   We are still working on the issue affecting outgoing (MT) SMS on gatewayapi.com. While the incident is ongoing, we recommend sending your SMS through our EU platform at https://gatewayapi.eu/, which is running normally.

4. monitoring Nov 02, 2026, 05:20 PM UTC

   We are seeing outgoing (MT) SMS traffic starting to recover. Messages queued during the incident are now being processed, so some customers may still see delays and late delivery reports for a while. We continue to monitor the situation. We will post another update once the queue is processed.

5. resolved Nov 02, 2026, 05:35 PM UTC

   Message processing on GatewayAPI.com is back to normal, and all queued messages have been delivered. We’re keeping a close eye on the platform. What happened From 16:02 CET (15:02 UTC) to about 18:15 CET, outbound messages from GatewayAPI.com were delayed. Our API was up the whole time and accepted every message sent to it. Some messages waited in our queue longer than usual before going out to the networks. Impact Only GatewayAPI.com customers were affected. Other GatewayAPI platforms were not. No messages were lost. Every accepted message was queued and delivered, some with a delay. No data was exposed or breached. This was a performance problem, not a security incident. What we’ve done We traced the problem to how our internal message-processing workers pick up messages from the queue. We changed that setting, and normal processing resumed right away. As a precaution, we’re running with extra processing capacity and have added more monitoring while we confirm the root cause. Next steps We’re still looking into the underlying cause, including a suspected problem in one of the software components our processing workers depend on. We’ll publish a full post-incident review here within 48 hours with the root cause and the steps we’re taking to stop this from happening again. We’re sorry for the disruption and thank you for your patience. If you have questions about specific messages, please contact our support team.