Struck in red is what ElevenLabs removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Multiple US endpoints experiencing timeouts and latency
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-13 09:21 UTC
AddedResolved time#5
Before: not present
After: 2026-10-13 14:18 UTC
AddedUpdateinvestigating#6
Before: not present
After: We are investigating elevated latency and timeouts affecting multiple endpoints, including some Elevenagents endpoints. Some requests may be slow or fail. Our team is actively looking into the cause.
AddedUpdateresolved#7
Before: not present
After: Error rates have returned to normal. We are currently still investigating the cause of this downtime and will update the status page with an RCA as soon as possible.
AddedUpdateidentified#8
Before: not present
After: We’re seeing error rates rise again, so calls may still fail or experience increased latency.
AddedUpdatemonitoring#9
Before: not present
After: Error rates are still flaky. We are monitoring the affected endpoints to confirm stability and are working with our data provider on a root cause analysis.
AddedUpdateidentified#10
Before: not present
After: We are still seeing elevated errors and timeouts on the affected endpoints, and requests may continue to fail. We are actively working with our data provider to restore full service and bring the endpoints back online.
AddedUpdateidentified#11
Before: not present
After: We are actively working with our data service provider to ensure endpoint stability. We will update the status page as soon as we have received confirmation that all our endpoints are back to normal.
AddedUpdatemonitoring#12
Before: not present
After: Error rates have continued to stabilize. We are continuing to monitor the affected endpoints to ensure service remains steady.
AddedUpdateresolved#13
Before: not present
After: The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete.
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.