GatewayAPI Incident Post-Mortem: Service Disruption on June 14, 2026

‌

Date of Incident: June 14, 2026

Duration: 12:33 CEST – 13:05 CEST (32 minutes)

Services Impacted: GatewayAPI EU SMS APIs & Customer Dashboard

‌

Executive Summary

On June 14, 2026, between 12:33 CEST and 13:05 CEST, GatewayAPI experienced a service disruption that temporarily impacted our EU SMS APIs and the Customer Dashboard. The core issue originated from a localized network and infrastructure outage at our cloud provider, which unexpectedly isolated our main database cluster.

While our core SMS services are architected to operate independently during database anomalies, the specific nature of this infrastructure failure triggered an unforeseen dependency that halted message-traffic processing. Our team intervened immediately, and services were fully restored within 32 minutes.

‌

Root Cause Analysis

The disruption was initiated by a hardware and network-level incident within our cloud provider's infrastructure. This failure caused our primary database cluster to become unavailable.

Although our message and SMS routing engine is designed with fail-safes to bypass database dependencies during outages, the unique state of this infrastructure failure prevented the seamless decoupling of these systems. This caused a temporary backlog, rendering both the Customer Dashboard and the EU SMS APIs unavailable during the affected window.

‌

Actions Taken & Preventive Measures

We take platform reliability incredibly seriously and have already implemented several immediate improvements to ensure this specific scenario cannot happen again:

• Decoupling & Robustness Enhancements: We have updated the message API and application routing mechanisms to ensure absolute independence from the primary database. In the event of a future database failure, core message and SMS routing will automatically fail back to decentralized, local mechanisms without interruption.
• Optimized Failover Routines: We will refine and streamline our automated failover procedures to reduce the time it takes for secondary systems to assume control during infrastructure anomalies.
• Enhanced Monitoring & Alerting: We will deploy additional high-fidelity alarms and alerting thresholds. This will grant our engineering team earlier visibility into underlying cloud provider infrastructure shifts before they impact user-facing services.

‌

Our Commitment to You

We sincerely apologize for the disruption this caused to your operations. We are fully committed to providing a highly resilient business messaging platform, and we are using the insights gained from this incident to continuously harden our infrastructure.

‌

If you have any remaining questions regarding this incident, please feel free to reach out to our support team.