1What changed since the last material update?
Compared with brief revision 1 (incident revision 1):
- New provider update (no material change) · incident revision 2
- Status changed: investigating → identified · incident revision 3
- Impact changed: minor → major · incident revision 3
- More services affected: Functions · incident revision 3
- More regions affected: us-east-1 · incident revision 3
| Field | Before | Now | |
|---|---|---|---|
| status | investigating | identified | changed |
| provider impact | minor | major | changed |
| services | Compute | Compute, Functions + Functions | changed |
| regions | none named | us-east-1 + us-east-1 | changed |
| mitigation or recovery | the provider is investigating | the provider has identified the issue and is working on a fix 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 | identified | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Provider impact level | major | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Services named | Compute, Functions | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Regions named | us-east-1 | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Latest provider update | Error rates also affect Functions in us-east-1. | Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · 来源 ↗ |
| Severity used for sorting | 2 | 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.
| Began (provider) | 2026-01-15 14:00 UTC |
| Published by Northwind Cloud (synthetic) | 2026-01-15 14:20 UTC |
| Observed and published by Spike | 2026-01-15 14:21 UTC |
| Delivered | 2026-01-15 14:23 UTC (accepted on attempt 2) |
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).
| 商业 service | Assessment | Why it matched |
|---|---|---|
| Card authorization high criticality | Direct match | Northwind Cloud (synthetic) is on your list (Functions) in us-east-1; the provider names Compute, Functions. |
| Payroll high criticality | Possible exposure | Acme Payroll runs on Northwind Cloud (synthetic), which reports this incident. Acme Payroll has not confirmed any effect. |
Entered scope at this revision: Card authorization
Customer impact: Not confirmed by your team. Customer impact needs your own evidence.
4What did we know then?
Revision 3 uses only what Spike had recorded by 2026-01-15 14:21 UTC: incident revisions 1, 2, 3. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 3a7969112ffb4506).
Known later, at brief revision 5 (2026-01-15 14:48 UTC): New provider update; Status changed: identified → monitoring; Fewer services affected: Functions. Open revision 5
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 |
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