1What changed since the last material update?
Compared with brief revision 3 (incident revision 3):
- New provider update (no material change) · incident revision 4
- Status changed: identified → monitoring · incident revision 5
- Fewer services affected: Functions · incident revision 5
| Field | Before | Now | |
|---|---|---|---|
| status | identified | monitoring | changed |
| provider impact | major | major | same |
| services | Compute, Functions | Compute | changed |
| regions | us-east-1 | us-east-1 | 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 Northwind Cloud (synthetic) · published 2026-01-15 14:47 UTC · incident revision 5 · 来源 ↗ |
| Provider impact level | major | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Services named | Compute | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:47 UTC · incident revision 5 · 来源 ↗ |
| Regions named | us-east-1 | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Latest provider update | Functions has recovered. Compute errors continue in us-east-1. | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:47 UTC · incident revision 5 · 来源 ↗ |
| Severity used for sorting | 2 | Spike inference SpikeTrendWatch · incident revision 5 |
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.
Late-arriving evidence (incident revision 4): Northwind Cloud (synthetic) dated this update 2026-01-15 14:16 UTC, before Spike's previous record at 2026-01-15 14:21 UTC. It was not in the provider's feed until later, so no reader could have seen it earlier. Brief revision 3 did not include it, although the provider dates it earlier.
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.
| Began (provider) | 2026-01-15 14:00 UTC |
| Published by Northwind Cloud (synthetic) | 2026-01-15 14:47 UTC |
| Observed and published by Spike | 2026-01-15 14:48 UTC |
| Delivered | 2026-01-15 14:48 UTC |
3Which business service should I check?
Dependency list version v2-synthetic, saved 2026-01-15 14:40 UTC: the list in force at this revision (3 rows).
| 商业 service | Assessment | Why it matched |
|---|---|---|
| Payroll high criticality | Possible exposure | Acme Payroll runs on Northwind Cloud (synthetic), which reports this incident. Acme Payroll has not confirmed any effect. |
| Reporting low criticality | Direct match | Northwind Cloud (synthetic) is on your list (Compute); the provider names Compute. |
Left scope: Card authorization. No longer matched: Northwind Cloud (synthetic)'s record at incident revision 5 no longer names the service or region this dependency lists.
Customer impact: Not confirmed by your team. Customer impact needs your own evidence.
4What did we know then?
Revision 5 uses only what Spike had recorded by 2026-01-15 14:48 UTC: incident revisions 1, 2, 3, 4, 5. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 81d0cdc1dce5b7c8).
Known later, at brief revision 6 (2026-01-15 15:35 UTC): Correction: The provider removed this incident from its status page without a resolution notice. Spike marks it resolved; Compute errors were last reported in us-east-1.; Resolved. Open revision 6
5Who received the correction?
No correction has been published for this incident.
All deliveries to this workspace up to this revision
| Incident revision | Channel | Accepted | Attempts | First attempt |
|---|---|---|---|---|
| 1 | hook:demo | yes | 1 | 2026-01-15 14:03 UTC |
| 3 | hook:demo | yes | 2 | 2026-01-15 14:21 UTC |
| 5 | hook:demo | yes | 1 | 2026-01-15 14:48 UTC |
Delivery outcomes are shown as they stand now, including retries made after this revision. Not recorded. Spike records whether the receiving system accepted a delivery (HTTP 2xx). It does not record whether a person read it. A disconnected system recovers every revision, corrections included, from /api/v1/watch/changes?cursor=….
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. API contract · Open another brief