Breaking
Synthetic demo. The provider, the incident, the workspace, its dependency list and its deliveries are invented to show how a Spike Pro workspace sees a brief. Nothing here is real data, nothing here can be changed, and no real workspace is read. See a brief on a real outage.

This revision as JSON · Prints cleanly from your browser's print command.

1What changed since the last material update?

Compared with brief revision 3 (incident revision 3):

  • New provider update (no material change) · incident revision 4
FieldBeforeNow
statusidentifiedidentifiedsame
provider impactmajormajorsame
servicesCompute, FunctionsCompute, Functionssame
regionsus-east-1us-east-1same
mitigation or recoverythe provider has identified the issue and is working on a fixthe provider has identified the issue and is working on a fix
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?

ClaimValueEvidence
Incident statusidentifiedProvider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · source ↗
Provider impact levelmajorProvider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · source ↗
Services namedCompute, FunctionsProvider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · source ↗
Regions namedus-east-1Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:20 UTC · incident revision 3 · source ↗
Latest provider updateCorrection to the start time: errors in us-east-1 began earlier than first reported.Provider statement Northwind Cloud (synthetic) · published 2026-01-15 14:16 UTC · incident revision 4 · source ↗
Severity used for sorting2Spike inference SpikeTrendWatch · incident revision 4

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:16 UTC
Observed and published by Spike2026-01-15 14:27 UTC
Deliverednot 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).

Business serviceAssessmentWhy it matched
Card authorization
high criticality
Direct matchNorthwind Cloud (synthetic) is on your list (Functions) in us-east-1; the provider names Compute, Functions.
Payroll
high criticality
Possible exposureAcme 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 4 uses only what Spike had recorded by 2026-01-15 14:27 UTC: incident revisions 1, 2, 3, 4. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint b4e41a863e08382f).

Known later, at brief revision 5 (2026-01-15 14:48 UTC): 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 revisionChannelAcceptedAttemptsFirst attempt
1hook:demoyes12026-01-15 14:03 UTC
3hook:demoyes22026-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