Twilio incident
Failing Knowledge Sources of Type 'Web' are Stuck In Progress
Twilio experienced a minor incident on July 10, 2026 affecting Enterprise Knowledge, lasting 3h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 10, 2026, 09:17 PM UTC
We are observing knowledge sources of type 'web' are stuck in progress because the status update to set them to 'Failed' is failing. We expect to provide another update in 1 hour or as soon as more information becomes available.
- investigating Jul 10, 2026, 10:17 PM UTC
We are observing knowledge sources of type 'web' are stuck in progress because the status update to set them to 'Failed' is failing. We expect to provide another update in 2 hours or as soon as more information becomes available.
- investigating Jul 11, 2026, 12:17 AM UTC
We are observing knowledge sources of type 'web' are stuck in progress because the status update to set them to 'Failed' is failing. We expect to provide another update in 4 hours or as soon as more information becomes available.
- monitoring Jul 11, 2026, 12:30 AM UTC
The issue has been identified and mitigated. All new knowledge sources for web should be process correctly now. For the affected Crawls, they are being re-processed. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.
- resolved Jul 11, 2026, 12:46 AM UTC
All Knowledge Services are Operational and the Stuck Web Crawls are also completed. The issue has been resolved and Knowledge Services are operating normally at this time.