Elevated Errors Affecting On Call Central 10/20/25
Impact: Some calls and messages may fail or be delayed
Cause: An outage at Amazon Web Services is impacting Twilio (our telecom partner) and many services worldwide.
Since 3:10am ET this morning, we’re seeing intermittent errors and timeouts that affect parts of On Call Central. This is tied to a widespread cloud provider incident that’s also impacting Twilio and many other products globally. Twilio reports partial recovery in some systems; the broader issue is still being worked on by the provider.
As of now, 1:30PM ET, we are continuing to monitor a major ongoing outage at Amazon Web Services (AWS) that is impacting Twilio and other large cloud providers. Twilio reports that multiple products remain affected, and AWS continues to report degraded performance and elevated error rates in the US-EAST-1 region.
On Call Central customers may continue to experience intermittent failures or delays in call routing. This is part of a global outage affecting many services worldwide.
We are actively monitoring recovery progress and will provide further updates as new information becomes available.
What we’re doing:
This incident is expected to resolve as AWS services recover. No action is required from customers. We’ll post another update our status page the next few hours or sooner if there’s a significant change.
Provider status pages:
- Twilio: status.twilio.com
- Cloud provider: health.aws.amazon.com/health/status
- Our Status Page: on-call-central.instatus.com
-
Official comment
Service recovery continues to improve. Amazon Web Services (AWS) has reported steady progress in restoring systems within the US-EAST-1 region, and Twilio has confirmed that most products have largely recovered.
On Call Central remains stable, though some customers may still experience occasional delays or intermittent call routing issues as AWS completes its remediation work. We will continue to monitor until full resolution is confirmed.
Provider status pages:
-
Amazon has stated that this issue has been resolved as of ~6:00pm ET.
0
Please sign in to leave a comment.
Comments
2 comments