Minor impactResolvedCommunication

Twilio incident: Twilio Accounts may not be able to Connect to Dialogflow VirtualAgent for Voice

Twilio reported this minor-impact incident on its official status page on May 25, 2026, 01:30 UTC. It was resolved after 4h 51m.

Right now Twilio is operational. Live Twilio status →

🔔 Get alerted when Twilio has issuesFree · email alerts · no credit card

May 25, 2026, 01:30 UTC

started

May 25, 2026, 06:21 UTC

resolved

4h 51m

duration

Minor

impact

Timeline

updates from Twilio's status page ↗

resolvedMay 25, 2026, 06:21 UTC
We are no longer experiencing latency when conversing with Dialogflow CX agents via . 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.

Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
Snyk: Snyk Tests for Gradle projects DegradationMinor · May 22, 2026, 02:29 UTC
Linode: Service Issue - Paris (FR-PAR3)Minor · May 22, 2026, 11:22 UTC
OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 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

← Previous: SMS Delivery Delays from a Subset of Twilio Phone Numbers to TCell Tajikistan (May 23, 2026)Next: SMS Delivery Delays from Twilio Phone Numbers to Telkom South Africa (May 25, 2026) →