NTA experienced a major incident on December 31, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Dec 31, 2025, 01:39 PM UTC
Type: Incident Duration: 2 hours and 7 minutes Affected Components: Outbound Calls, Inbound Calls, Dialer, Bubble Integration, API, Web Interface, No Service Impact Expected, Handset Provisioning, Busy Lamps Dec 31, 13:39:22 GMT+0 - Investigating - We have become aware of an outage on one of the upstream providers. We are currently investigating this incident. Dec 31, 13:51:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 31, 13:55:11 GMT+0 - Investigating - We are currently investigating this incident. Dec 31, 14:21:47 GMT+0 - Investigating - We are currently investigating this incident. Dec 31, 14:45:22 GMT+0 - Identified - While the service is now working, we are continuing to work on a fix for this incident. Dec 31, 15:21:56 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 31, 15:46:07 GMT+0 - Resolved - This incident has been resolved. The system is now up and working. A reason for outage will be issued after a thorough investigation Jan 2, 14:30:35 GMT+0 - Postmortem - **RFO – Wednesday 31st December** At **13:39**, our primary service provider experienced extremely high latency on the connections supplying our network. While this caused service degradation, the connections did not go fully offline, which prevented automatic disaster recovery from initiating. At **13:51**, we manually shut down the affected interfaces, allowing disaster recovery procedures to begin. Due to the nature of the fault, services on the impacted connections then had to be manually terminated in order to fully restore service. At **14:21**, we identified that the primary impact was on call completion. One service was becoming stuck as SIP signalling was adversely affected by the high latency, preventing calls from completing successfully. By **14:35**, all services were fully restored and operating normally. Jan 2, 08:46:59 GMT+0 - Resolved - This incident has been resolved.