Skip to content
RELIASTRAObservatory
Monitor your dependencies

Observed incident recordDetected by RELIASTRA probes

Official status page failure window - Stripe

Incident f8f68fb6-a82e-4d4e-8473-15c087f5573d - endpoint status.stripe.com, measured from us-east. Confirming rule: 2 consecutive failed observations counted 2 of them.

ResolvedSeverity: MajorStatus: ResolvedAttribution: OBSERVED by RELIASTRA

Observed window

Every timestamp is a stored field of this record, printed in UTC. The window begins at the first failure the rule counted and ends, for a resolved record, at the observation run whose consecutive successes closed it.
Opened
25 Oct 2026 20:36:36 UTC
Confirmed
25 Oct 2026 20:41:21 UTC - the run that made the failure count reach the threshold; this record did not exist before it
Recovered
25 Oct 2026 20:52:39 UTC
Duration
16m (from the stored window)

What was measured

The record is a summary of an observation run set. The referenced observation ids resolve to stored probe entries inside the retention window; the detector keeps no second, narrative version of them.
Endpoint observed
Official status page - https://status.stripe.com
Measured from
us-east - the only observation region named in this record; nothing about other regions is claimed or inferred
Failed observations
2, consecutive through the trigger set
Failure shape
mixed failure modes
Observation references
first 15cb80aa-832d-4feb-9b1a-73cd0dcaf8ef last 168a5d73-6408-4705-942e-622833c3ba1f

The claim, in full

Between 2026-10-25T20:36:36.450794+00:00 and 2026-10-25T20:41:21.590514+00:00, RELIASTRA probes in us-east recorded 2 consecutive failed observations against https://status.stripe.com (the observed Stripe target). Failure class: mixed; observed status: no HTTP response. This record describes the observed endpoint only and is not a statement about the vendor's services as a whole. That is all of it. Nothing about the vendor as a whole, nothing about other regions, nothing about your requests - the record you are reading is the measurement, not a narration of it.

Evidence artifact

A frozen, hashed document of this record's window: the claim, the detection rule, and every observation row it rests on. Deterministic, reproducible from stored data, immutable once written.
Artifact
/api/v1/public/incidents/f8f68fb6-a82e-4d4e-8473-15c087f5573d/evidence - JSON, served byte-for-byte as stored
Content hash
sha256: 5b6d38e9ef2f75566e87198c8d29b7f123cfc3ded924ba368b36ecbd3546d721
Freeze
version 2, taken while the incident was resolved (25 Oct 2026 21:16:32 UTC); later freezes supersede, never edit, and each stays at its own versioned URL
Coverage
6 observations in the window
Verification
Remove the "verification" key from the document, re-serialise with sorted keys and compact separators, and SHA-256 the UTF-8 bytes: the digest must equal the hash above. The recipe ships inside every artifact.

What this record does not establish

The boundaries are part of the record, not a disclaimer under it.
Causation
Not established. A 5xx can be the vendor, a shared middle path, or the probe's own egress - the record reports what came back, not why.
Vendor acknowledgement
Stripe may have recorded this window differently, later, or not at all. RELIASTRA does not ingest vendor-reported status, so no reconciliation is offered either way.
Global reach
This window is named for us-east. A record from one observation region never settles the question in another.
Customer impact
Whether your requests were affected is your measurement to make - this record carries only RELIASTRA's own probes.

Where this fits