1What changed since the last material update?
Compared with brief revision 1 (incident revision 1):
- New provider update (no material change) · incident revision 2
| Field | Before | Now | |
|---|---|---|---|
| status | investigating | investigating | same |
| provider impact | minor | minor | same |
| services | Compute | Compute | same |
| regions | none named | none named | same |
| mitigation or recovery | the provider is investigating | the provider is investigating From the provider's status term, not from a separate statement. | same |
| cause | — | — Not stated by the provider in a structured field. | same |
2Who says so, and when?
| Claim | Value | Evidence |
|---|---|---|
| Incident status | investigating | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:01 UTC · incident revision 1 · fuente ↗ |
| Provider impact level | minor | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:01 UTC · incident revision 1 · fuente ↗ |
| Services named | Compute | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:01 UTC · incident revision 1 · fuente ↗ |
| Regions named | none named in a structured field | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:01 UTC · incident revision 1 · fuente ↗ |
| Latest provider update | We continue to investigate. | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:08 UTC · incident revision 2 · fuente ↗ |
| 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.
Conflict (incident revision 2): Northwind Cloud (synthetic)'s latest update is marked “monitoring” while the incident status is “investigating”.
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: Northwind Cloud (synthetic) names no region in a structured field.
| Began (provider) | 2026-01-15 14:00 UTC |
| Published by Northwind Cloud (synthetic) | 2026-01-15 14:08 UTC |
| Observed and published by Spike | 2026-01-15 14:09 UTC |
| Delivered | not delivered to this workspace at this revision |
3Which business service should I check?
Dependency list version v1-synthetic, saved 2026-01-14 14:00 UTC: the list in force at this revision (2 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. |
Customer impact: Not confirmed by your team. Customer impact needs your own evidence.
4What did we know then?
Revision 2 uses only what Spike had recorded by 2026-01-15 14:09 UTC: incident revisions 1, 2. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 1453587a3000d336).
Known later, at brief revision 3 (2026-01-15 14:21 UTC): Status changed: investigating → identified; Impact changed: minor → major; More services affected: Functions; More regions affected: us-east-1. Open revision 3
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 |
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