Twilio incident

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

Minor Resolved View vendor source →

Twilio experienced a minor incident on May 25, 2026 affecting Dialogflow US1, lasting 4h 50m. The incident has been resolved; the full update timeline is below.

Started
May 25, 2026, 01:30 AM UTC
Resolved
May 25, 2026, 06:21 AM UTC
Duration
4h 50m
Detected by Pingoru
May 25, 2026, 01:30 AM UTC

Affected components

Dialogflow US1

Update timeline

  1. investigating May 25, 2026, 01:30 AM UTC

    Our engineers have identified an issue with elevated latency conversing with Dialogflow CX agents via and are currently investigating. We expect to provide another update in 1h or as soon as more information becomes available.

  2. investigating May 25, 2026, 02:30 AM UTC

    We are continuing to experience latency conversing with voice Dialogflow CX agents via . Our engineers are still investigating the issue with our partner. We will provide another update in 2 hours or as soon as more information becomes available.

  3. investigating May 25, 2026, 04:21 AM UTC

    We are observing recovery and improvement in latency when conversing with Dialogflow CX agents via . We will continue monitoring the service to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.

  4. resolved May 25, 2026, 06:21 AM UTC

    We are no longer experiencing latency when conversing with Dialogflow CX agents via . This incident has been resolved.