Live

Flex Agent Copilot Note Generation Issues

This incident has been consolidated into https://status.twilio.com/incidents/pq17rz6sfhj3 The impact to Flex Agent Copilot observed on October 20, 2026, at 9:53 AM PDT has been completely resolved. There is no active customer impact. For the complete incident details review and event timeline, refer to the status page link: https://status.twilio.com/incidents/pq17rz6sfhj3

The latest update from Twilio.

State

Resolved

Started

3 d ago

2026-10-29 03:50 UTC

Lasted

1 h 30 min

until 2026-10-29 05:20 UTC

Worst impact

Degraded

Timeline

2 updates
03:5004:1204:3504:5705:20
DegradedUpdate postedTimes in UTC

Investigating

1 h 30 min 100%

Updates

Times in UTC

As posted by Twilio

Resolved2026-10-29 05:20 UTC

This incident has been consolidated into https://status.twilio.com/incidents/pq17rz6sfhj3 The impact to Flex Agent Copilot observed on October 20, 2026, at 9:53 AM PDT has been completely resolved. There is no active customer impact. For the complete incident details review and event timeline, refer to the status page link: https://status.twilio.com/incidents/pq17rz6sfhj3

Investigating2026-10-29 03:50 UTC

We are investigating an issue affecting Flex Agent Copilot, where auto-generation of notes is currently failing for a subset of customers. Other Flex features remain operational, and our engineering team is actively working to resolve the failure. We will provide our next update in 1 hour or as soon as more details become available.

Affected components

2
Flex Agent CopilotFLEX - Flex Agent Copilot

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

37

Median duration

9 h 43 min

This incident

85% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 9 h 43 min
90 days agoToday

Other Twilio incidents

All incidents

Follow Twilio

Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane