1What changed since the last material update?
Compared with brief revision 1 (incident revision 1):
- Status changed: investigating → monitoring · incident revision 2
| Field | Before | Now | |
|---|---|---|---|
| status | investigating | monitoring | changed |
| provider impact | minor | minor | same |
| services | SFO3 | SFO3 | same |
| regions | none named | none named | same |
| mitigation or recovery | the provider is investigating | 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 DigitalOcean · published 2026-11-19 04:45 UTC · incident revision 2 · source ↗ |
| Provider impact level | minor | Provider statement DigitalOcean · published 2026-11-19 04:37 UTC · incident revision 1 · source ↗ |
| Services named | SFO3 | Provider statement DigitalOcean · published 2026-11-19 04:37 UTC · incident revision 1 · source ↗ |
| Regions named | none named in a structured field | Provider statement DigitalOcean · published 2026-11-19 04:37 UTC · incident revision 1 · source ↗ |
| Latest provider update | Our Engineering team has mitigated the increased error rates impacting multiple services in the SFO3 region and is monitoring the situation. The impact was caused by a network routing issue that disrupted connectivity to one of our core database systems after a load balancer… | Provider statement DigitalOcean · published 2026-11-19 04:45 UTC · incident revision 2 · source ↗ |
| Severity used for sorting | 1 | Spike inference SpikeTrendWatch · incident revision 2 |
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: DigitalOcean names no region in a structured field (the title names a place; Spike does not turn titles into regions).
| Began (provider) | 2026-11-19 04:37 UTC |
| Published by DigitalOcean | 2026-11-19 04:45 UTC |
| Observed and published by Spike | 2026-11-19 04:45 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 2 uses only what Spike had recorded by 2026-11-19 04:45 UTC: incident revisions 1, 2. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 16dd56b942ee5ae0).
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