1What changed since the last material update?
Compared with brief revision 2 (incident revision 2):
- Resolved · incident revision 3
| Field | Before | Now | |
|---|---|---|---|
| status | monitoring | resolved | changed |
| provider impact | minor | minor | same |
| services | API v3 | API v3 | same |
| regions | none named | none named | same |
| mitigation or recovery | the provider reports a fix in place and is monitoring | the provider reports the incident resolved 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 | resolved | Provider statement Twilio · published 2026-11-18 15:02 UTC · incident revision 3 · fonte ↗ |
| Provider impact level | minor | Provider statement Twilio · published 2026-11-18 14:05 UTC · incident revision 1 · fonte ↗ |
| Services named | API v3 | Provider statement Twilio · published 2026-11-18 14:05 UTC · incident revision 1 · fonte ↗ |
| Regions named | none named in a structured field | Provider statement Twilio · published 2026-11-18 14:05 UTC · incident revision 1 · fonte ↗ |
| Latest provider update | Our engineers have monitored performance and mail send latency has returned to normal levels. This impacted transactional email send requests through the v3 Mail Send API in AP, while SMTP and v2 mail send continued to operate normally. This issue has been resolved and all… | Provider statement Twilio · published 2026-11-18 15:02 UTC · incident revision 3 · fonte ↗ |
| Severity used for sorting | 1 | Spike inference SpikeTrendWatch · incident revision 3 |
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 (the title names a place; Spike does not turn titles into regions).
| Began (provider) | 2026-11-18 14:05 UTC |
| Published by Twilio | 2026-11-18 15:02 UTC |
| Observed and published by Spike | 2026-11-18 15:03 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 3 uses only what Spike had recorded by 2026-11-18 15:03 UTC: incident revisions 1, 2, 3. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 0ce6c7bcc6221390).
This is the latest revision.
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