Twilio incident: Unable to save Phone Numbers with Studio Flow

1. resolvedJul 24, 2026, 13:30 UTC

   We are no longer experiencing generic errors when saving phone number configurations assigned to a Studio Flow in the Console. This incident has been resolved.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Render: Service Disruption in OregonCritical · Jul 24, 2026, 11:16 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident NotificationMajor · Jul 23, 2026, 19:14 UTC
• Grafana Cloud: Errors creating new Slack integration for Grafana IRMMajor · Jul 24, 2026, 09:17 UTC
• npm: Publish and Install failuresMajor · Jul 24, 2026, 11:08 UTC
• Notion: Notion is downMajor · Jul 24, 2026, 11:24 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• SendGrid: Voice Call Failures from Twilio Phone Numbers to Reliance Jio IndiaMinor · Jul 17, 2026, 15:54 UTC
• Plaid: Transaction Updates DelayedMinor · Jul 22, 2026, 14:58 UTC
• Snyk: Partial Test DegradationMinor · Jul 23, 2026, 19:59 UTC
• Notion: Automation processing delaysMinor · Jul 24, 2026, 07:20 UTC

How often does Twilio have incidents?

Twilio reported 501 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 49m. See Twilio's uptime and incident history