60 Gatewayapi incidents · 2025年6月 — official updates, affected components, duration and resolution details.
我们目前正在处理与瑞典泰利亚有关的问题。 交付报告可能被推迟。 交通将受到密切监测,同时我们期望得到最新消息,而且服务将再次按计划运作.
向Telia Sweden提出的问题已经解决。 正在按预期归还交付报告。 事故期间任何延迟的德国航天飞机现在都应交付。 如果你仍然看到失踪或延迟 DLRs 对于Telia瑞典, 请联系我们的支援小组.
自动翻译自官方事件更新。
目前,向丹麦TDC发送的信息的交付报告出现延误。 消息发送不受影响 。 所有信息都作为正常方式发送给接收者,但相应的发送报告可能比通常时间晚. 我们正在同发改会合作解决这一问题,并将在我们了解更多情况后立即公布最新情况.
这个问题已经得到解决。 发往丹麦TDC的电文的交付报告(DLRs)再次被正常发送. 在整个事件中,所有信息都传达给接收者。 只有交付报告和MO(comming)消息被延迟. 谢谢你的耐心.
自动翻译自官方事件更新。
目前,向丹麦TDC发送的信息的交付报告出现延误。 消息发送不受影响 。 所有信息都作为正常方式发送给接收者,但相应的发送报告可能比通常时间晚. 我们正在同发改会合作解决这一问题,并将在我们了解更多情况后立即公布最新情况.
这个问题已经得到解决。 发往丹麦TDC的电文的交付报告(DLRs)再次被正常发送. 在整个事件中,所有信息都传达给接收者。 只有交付报告和MO(comming)消息被延迟. 谢谢你的耐心.
自动翻译自官方事件更新。
目前,我们正在监测向ICE挪威交付报告方面的延误情况。 用户可能遭遇延迟收到交付报告。 MT流量不受影响. 我们会随时通知你.
《交付报告》已恢复正常。 我们将继续监测,以便采取妥善措施.
自动翻译自官方事件更新。
目前我们正面临瑞典Tele2的问题。 交通将受到密切监测,同时我们期望得到最新消息,而且服务将再次按计划运作。 谢谢你的理解,我们为此造成的不便表示歉意.
通向Tele2的交通 瑞典现已恢复正常。 我们将继续进行良好的监测。 谢谢你的理解,我们为此造成的不便表示歉意.
自动翻译自官方事件更新。
我们正与GatewayAPI.EU发生问题,目前正在调查根源。 我们目前正在努力解决这一问题。 .COM的设置仍如所愿. 我们会随时通知你.
我们看到GatewayAPI的服务。 欧盟再次全面运作。 将对交通和服务进行良好的监测。 谢谢你的耐心 我们为此造成的不便道歉.
** 概要:延迟处理的电文在** [** GatewayAPI.eu**] (http://GatewayAPI.eu) ** 2026年9月29日** 2026年9月29日,协调世界时从18:24到20:05\(20:24–22:05 CEST\),[GatewayAPI.eu](http://GatewayAPI.eu)在消息处理中经历了101分钟的延迟. 我们的[GatewayAPI.com](http://GatewayAPI.com)平台没有受到影响. 在整个事件中,所有入境的API,包括移动通讯API,REST API和SMPP仍然可用,并继续接受消息. 然而,接受的信息被排队而不是处理和发送。 交付报告\(DLRs\)由于同样的原因被推迟. ** 没有丢失信件。 ** 一旦恢复处理,所有已排队的信息都会被发送,延迟时间可达101分钟. 客户无需重新发送在此期间提交的任何信息。 我们检测到几条消息, ** 发生了什么事** 接收了大量异常多的电文,并转交给负责处理发出电文的内部部门。 处理此音量需要比服务被允许使用的更多内存,因此平台自动停止. 当服务重启后,它接回了同样的大量积压,被再次停止. 这在循环中重复,在此期间无法处理任何消息。 ** 循环原因** 分配给我们的信息处理服务的内存没有大小,无法处理如此庞大的批量负荷。 因此,一次大爆发的流量足以使服务进入重启循环,而不是被逐渐处理. ** 检测** 我们没有在[GatewayAPI.eu](http://GatewayAPI.eu)上自动发出警报,用于这一特定情况,即我们的API在处理停止时继续接受消息. 因此,我们的监测没有发现这一事件,我们用了比它更久的时间作出反应。 我们对这一差距负有全部责任。 ** 决议** 我们的工程师识别了重启回路,增加了消息处理服务可用的内存,并将其带回了网络. 服务随后完成了排队积压的工作,并处理了所有待发信息和交付报告。 ** 我们正在做哪些工作以防止这种情况再次发生** * ** 改进监测:** 我们对[GatewayAPI.eu](http://GatewayAPI.eu)增加了一个警报,在处理后流量意外下降时触发. * 能力增加:** 消息处理服务现在拥有更高的内存分配,这降低了在大量散装货下被停止的风险. * ** 改进了负载处理\ (正在进行中):** 我们已经在努力改进内部信息排队,这将使该平台今后能更优雅地吸收类似的高峰。 我们知道及时交货对你的生意有多重要,我们为此造成的拖延表示歉意。 如果您对这起事件 如何影响您的账户有疑问, 请联系我们的支援小组.
自动翻译自官方事件更新。
目前我们正面临运输问题。 这只写在通讯上 我们目前正在努力找出根源并解决这一问题。 我们会随时通知你.
这一事件已经得到解决。 最新消息显示, 谢谢你的耐心.
** 概要:中断了在**上发来的电文[**GatewayAPI.com**](http://GatewayAPI.com)**-2026年9月23日** 2026年9月23日,从03:38到04:20 UTC\(05:38–06:20 CEST\),[GatewayAPI.com](http://GatewayAPI.com)在消息处理上经历了42分钟的中断. 所有公共服务API都受到影响,包括移动通讯API和REST API. 我们的初始状况更新仅提到REST API;我们对报告范围不足表示歉意。 客户板和我们的欧盟平台\([GatewayAPI.eu] (http://GatewayAPI.eu)\)没有受到影响. 事发期间提交的信息被API拒绝,需要备受怨恨. ** 发生了什么事** 我们的平台运行在管理好的Kubernetes服务。 在我们的云提供商进行的例行自动版本升级过程中,一个协调消息处理的内部服务未能回到网上. 每次启动时,平台的自动健康检查都会在启动完成前重启,将其放入重启回路. ** 循环原因** Kubernetes 健康检查\ (“ probes ”) 如果检查超过其设定的时限, 则重新启动服务 。 在早先的版本中,对我们类型的健康检查没有严格执行这一限制,这掩盖了我们的限制比启动期间的服务需要短的事实. 我们的云提供商宣布了这一变化,并暂停了被它确认为受影响的集群的自动升级,但我们的集群没有被确定,所以升级工作继续进行. 我们全面负责我们服务的配置。 ** 决议** 我们的工程师分析了受影响服务的启动要求,并用安全缓冲措施增加了体检时限。 随后服务正常开始,消息处理恢复. 我们知道可靠消息对你的生意有多重要 并对中断事件道歉 如果您对这起事件 如何影响您的账户有疑问, 请联系我们的支援小组.
自动翻译自官方事件更新。
目前我们正面临瑞典Tele2的延误。 交通将受到密切监测,同时我们期望得到最新消息,而且服务将再次按计划运作。 谢谢你的理解,我们为此造成的不便表示歉意.
通向Tele2的交通 瑞典现已恢复正常。 我们将继续进行良好的监测。 谢谢你的理解,我们为此造成的不便表示歉意.
自动翻译自官方事件更新。
我们目前正在监测欧盟平台的交付报告延误情况。 用户可能遭遇延迟收到交付报告。 MT流量不受影响. 我们会随时通知你.
欧盟平台的《交付报告》的拖延现已得到解决。 所有延迟交付报告都已处理完毕并正常交付。 在事件中,MT流量在任何时间都没有受到影响. 我们为造成的不便道歉。 如果你仍然看到丢失或延迟交付报告,请联系我们的支援小组.
自动翻译自官方事件更新。
我们正面临向德国移动的拖延。 交通将受到密切监测,同时我们期望得到最新消息,而且服务将再次按计划运作。 谢谢你的理解,我们为此造成的不便表示歉意.
向T-Mobile德国方向的交通现已恢复正常. 我们将继续进行良好的监测。 谢谢你的理解,我们为此造成的不便表示歉意.
自动翻译自官方事件更新。
We are currently experiencing issues with delays towards Swisscom & Sunrise in Switzerland. The traffic will be closely monitored whilst we expect an update and for the service to be functioning as intended again. Thank you for your understanding and we apologize for the inconvenience caused by this.
Traffic is now back to normal towards Swisscom & Sunrise in Switzerland. We will continue to monitor for good measure. Thank you for your understanding and we apologize for the inconvenience caused by this.
We are currently seeing a lot of rejected and enroute with the SMS service of TDC Denmark. The traffic will be closely monitored whilst we expect an update. Thank you for your understanding and we apologize for the inconvenience caused by this.
Traffic to TDC Denmark has recovered and rejected and enroute rates are back to normal. We are monitoring closely to confirm stability. Thank you for your patience, and we apologise for the inconvenience.
The traffic towards TDC Denmark/Nuuday is fully operational. We will continue to monitor the traffic for good measure. Thank you for your understanding and we apologize for the inconvenience caused by this.
We are currently monitoring the Delivery Report issue reported by Telia Norway. Users may experience a delay receiving delivery reports on messages sent to Telia Norway recipients. Messages are delivered, it is only the status reports that are delayed.
Delivery reports towards Telia Norway is now back to normal. We will keep monitoring for good measure. We are sorry for any inconveniences this may have caused.
We are seeing an unscheduled issue towards the GatewayAPI EU Dashboard and are working on resolving it. You may experience issues when trying to access the dashboard. We will keep you updated.
We are continuing to work on the issue with GatewayAPI EU Dashboard. You may currently experience delays in both MT and MO traffic. We will keep you updated and we apologize for the inconvenience caused by this.
The GatewayAPI EU Dashboard is up and running again. MT and MO traffic is back to normal. A Postmortem will follow. We will continue to monitor for good measure and we apologize for the inconvenience caused by this.
## **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.
We are currently experiencing issues with Delays towards Finland. The traffic will be closely monitored whilst we expect an update and for the service to be functioning as intended again. Thank you for your understanding and we apologize for the inconvenience caused by this.
The traffic towards Finland is back to normal. We will keep monitoring for good measure. Thanks for your patience and sorry for any inconveniences this may have caused.
We are experiencing issues with GatewayAPI.EU and are now investigating the root cause. All systems on GatewayAPI.EU are offline for the time being and we encourage you to stop all traffic on gatewayapi.eu until further notice. We are currently working on resolving the issue. The .COM setup is still working as intended. We will keep you updated.
All systems are now back online for Gatewayapi.EU. We will keep monitoring for good measure. Thanks for your patience and understanding, we are sorry for any inconvenience this may have caused.
We are currently experiencing issues with delays towards Hi3G Denmark. The traffic will be closely monitored whilst we expect an update and for the service to be functioning as intended again. Thank you for your understanding and we apologize for the inconvenience caused by this.
The traffic towards Hi3G Denmark looks to be fully operational once again. We will continue to monitor the traffic for good measure. Thank you for your understanding and we apologize for the inconvenience caused by this.
The traffic towards Hi3G Denmark looks stable. This incident has been resolved. Thank you for your understanding and we apologize for the inconvenience caused by this.
We are currently experiencing issues towards Italy. The traffic will be closely monitored whilst we expect an update and for the service to be functioning as intended again. Thank you for your understanding and we apologize for the inconvenience caused by this.
The traffic towards Italy is back to normal. We will keep monitoring for good measure. Thanks for your patience and sorry for any inconveniences this may have caused.
We are currently experiencing issues with Delayed delivery reports towards ICE Norway. The traffic is being delivered at Normal rate. We will be closely monitored whilst we expect an update and for the service to be functioning as intended again. Thank you for your understanding and we apologize for the inconvenience caused by this.
The traffic towards ICE Norway looks to be fully operational once again. We will continue to monitor the traffic for good measure. Thank you for your understanding and we apologize for the inconvenience caused by this.
We are currently seeing some issues with the Traffic log. Users may experience issues when trying to access the Traffic log. We are currently working on resolving the issue. All traffic is still being delivered accordingly. We will keep you updated.
The issue affecting the Traffic log has been resolved. Users should now be able to access the Traffic log again. Traffic delivery was unaffected throughout this incident.
