1What changed since the last material update?
Compared with brief revision 5 (incident revision 5):
- 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. · incident revision 6
- Resolved · incident revision 6
| Field | Before | Now | |
|---|---|---|---|
| status | monitoring | resolved | changed |
| provider impact | major | major | same |
| services | Compute | Compute | same |
| regions | us-east-1 | us-east-1 | 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 Northwind Cloud (synthetic) · published 2026-01-15 14:47 UTC · incident revision 6 · fuente ↗ |
| Provider impact level | major | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · fuente ↗ |
| Services named | Compute | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:47 UTC · incident revision 5 · fuente ↗ |
| Regions named | us-east-1 | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · fuente ↗ |
| 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 6 · fuente ↗ |
| 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. | Spike review decision Sección SpikeTrendWatch review · published 2026-01-15 15:35 UTC · incident revision 6 · fuente ↗ |
| Severity used for sorting | 2 | Spike inference SpikeTrendWatch · incident revision 6 |
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.
Conflict (incident revision 6): Northwind Cloud (synthetic)'s latest update is marked “monitoring” while the incident status is “resolved”.
Conflict (incident revision 5): The provider removed the incident from its status page without posting a resolution.
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.
Late-arriving evidence (incident revision 6): Northwind Cloud (synthetic) dated this update 2026-01-15 14:47 UTC, before Spike's previous record at 2026-01-15 14:48 UTC. It was not in the provider's feed until later, so no reader could have seen it earlier. Brief revision 5 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 15:35 UTC |
| Delivered | 2026-01-15 15:35 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).
| Negocios 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. |
Customer impact: Not confirmed by your team. Customer impact needs your own evidence.
4What did we know then?
Revision 6 uses only what Spike had recorded by 2026-01-15 15:35 UTC: incident revisions 1, 2, 3, 4, 5, 6. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 62231ecaf148165f).
This is the latest revision.
5Who received the correction?
Correction at 2026-01-15 15:35 UTC: incident revision 6 replaces revision 5. 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.
hook:demo · accepted by the endpoint · 1 attempt · first 2026-01-15 15:35 UTC · id d4All 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 |
| 6 | hook:demo | yes | 1 | 2026-01-15 15:35 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