1What changed since the last material update?
Compared with brief revision 3 (incident revision 3):
- Status changed: identified → monitoring · incident revision 4
| Field | Before | Now | |
|---|---|---|---|
| status | identified | monitoring | changed |
| provider impact | minor | minor | same |
| services | Speech Recognition (Gather Speech) US1 | Speech Recognition (Gather Speech) US1 | same |
| regions | none named | none named | same |
| mitigation or recovery | the provider has identified the issue and is working on a fix | the provider reports a fix in place and is monitoring From the provider's status term, not from a separate statement. | changed |
| cause | — | — Not stated by the provider in a structured field. | same |
2Who says so, and when?
| Claim | Value | Evidence |
|---|---|---|
| Incident status | monitoring | Provider statement Twilio · published 2026-11-18 20:20 UTC · incident revision 4 · source ↗ |
| Provider impact level | minor | Provider statement Twilio · published 2026-11-18 16:17 UTC · incident revision 1 · source ↗ |
| Services named | Speech Recognition (Gather Speech) US1 | Provider statement Twilio · published 2026-11-18 16:17 UTC · incident revision 1 · source ↗ |
| Regions named | none named in a structured field | Provider statement Twilio · published 2026-11-18 16:17 UTC · incident revision 1 · source ↗ |
| Latest provider update | We have started seeing recovery for intermittent timeouts with ElevenLabs TTS. We will continue to monitor to ensure a full recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available. | Provider statement Twilio · published 2026-11-18 20:20 UTC · incident revision 4 · source ↗ |
| Severity used for sorting | 1 | Spike inference SpikeTrendWatch · incident revision 4 |
Independent reporting and observable signals: none attached to this incident. Only the provider's own statements are shown. Public attention (for example a search spike) shows interest only. It is not evidence of cause or impact.
Open questions
- Cause: not stated by the provider in a structured field.
- Customer impact: not established. The provider reports its own systems; impact on a specific business needs that business's own evidence.
- Region: Twilio names no region in a structured field.
| Began (provider) | 2026-11-18 16:17 UTC |
| Published by Twilio | 2026-11-18 20:20 UTC |
| Observed and published by Spike | 2026-11-18 20:20 UTC |
| Delivered | per workspace, in its private view |
3Which business service should I check?
That depends on what your business runs on. See the private view in a synthetic demo. In Spike Pro (free beta), list the providers and services you depend on; your private view of this brief then shows which business service each revision touches, whether it is a direct match or a possible exposure, and why. Customer impact always needs your own evidence.
4What did we know then?
Revision 4 uses only what Spike had recorded by 2026-11-18 20:20 UTC: incident revisions 1, 2, 3, 4. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint d30a4cd81af1ab12).
Known later, at brief revision 5 (2026-11-18 20:52 UTC): Resolved. Open revision 5
5Who received the correction?
No correction has been published for this incident.
Delivery outcomes are private to each workspace and appear in its own view of this brief.
Handoff summary
Plain text to paste into a ticket or shift handoff.
Schema spike.evidence-brief/1. A brief is built from Spike's append-only incident revisions; it adds no facts of its own beyond the labeled Spike inferences. Incident record · API contract · Open another brief