Sentinel incident
CallSwitch degraded performance on inbound and outbound calling
Resolved after 3 hours 13 minutes, affecting Telephone System, on January 13, 2026.
**Incident Analysis** Following our initial report regarding the incident on January 12, 2026, our Engineering team implemented several emergency infrastructure upgrades. These improvements successfully mitigated the original risk and provided the enhanced visibility required to monitor this segment of our network more closely. On the afternoon of January 14, 2026, the same Memory Cache Layer within a single zone experienced a secondary disruption. This resulted in a 40-minute service outage affecting handsets, mobile applications, and in-call media, for accounts in that zone. Thanks to the telemetry tools installed earlier this week, our team was able to rapidly isolate a specific software bug within this layer. This bug was triggered by recent increases in network traffic. We have since successfully replicated, retested, and deployed a permanent fix across all zones. We will continue to monitor the network closely to ensure continued stabilit
Affected components
Update timeline
- investigating Jan 13, 2026, 12:53 PM UTC
An issue has been identified with degraded performance on the Callswitch dashboard and issues with inbound and outbound calls. This is being investigated currently.
- identified Jan 13, 2026, 01:00 PM UTC
Call traffic has been rerouted and are monitoring the results of this.
- monitoring Jan 13, 2026, 01:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 13, 2026, 04:06 PM UTC
Incident has been confirmed resolved.
- postmortem Jan 22, 2026, 10:33 AM UTC
**Incident Analysis** Following our initial report regarding the incident on January 12, 2026, our Engineering team implemented several emergency infrastructure upgrades. These improvements successfully mitigated the original risk and provided the enhanced visibility required to monitor this segment of our network more closely. On the afternoon of January 14, 2026, the same Memory Cache Layer within a single zone experienced a secondary disruption. This resulted in a 40-minute service outage affecting handsets, mobile applications, and in-call media, for accounts in that zone. Thanks to the telemetry tools installed earlier this week, our team was able to rapidly isolate a specific software bug within this layer. This bug was triggered by recent increases in network traffic. We have since successfully replicated, retested, and deployed a permanent fix across all zones. We will continue to monitor the network closely to ensure continued stabilit
Your product runs on more than Sentinel
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services