Observed incident recordDetected by RELIASTRA probes

Official status page failure window - Sentry

Incident ff64e8be-8c06-4349-924a-161da6fd0e25 - endpoint status.sentry.io, 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: 22 Oct 2026 20:50:27 UTC
Confirmed: 22 Oct 2026 20:55:04 UTC - the run that made the failure count reach the threshold; this record did not exist before it
Recovered: 22 Oct 2026 21:03:21 UTC
Duration: 12m (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.sentry.io
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: probe timeouts
Observation references: first 6d83bf6d-9809-4f85-803b-95a33a10cea6 last 0fc1c0af-c43c-49c5-9275-84086fc824ce

The claim, in full

Between 2026-10-22T20:50:27.090534+00:00 and 2026-10-22T20:55:04.434331+00:00, RELIASTRA probes in us-east recorded 2 consecutive failed observations against https://status.sentry.io (the observed Sentry target). Failure class: timeout; 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/ff64e8be-8c06-4349-924a-161da6fd0e25/evidence - JSON, served byte-for-byte as stored
Content hash: sha256: 6a5a77d0d2d095a25b9a72c9c480feb4675be1f9a384795eed99423f4af115ec
Freeze: version 2, taken while the incident was resolved (22 Oct 2026 21:08:14 UTC); later freezes supersede, never edit, and each stays at its own versioned URL
Coverage: 5 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: Sentry 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

Sentry - current recordLive observatory
All observed incidents - sentryIncident search
Cross-vendor observed incident searchIncident search
How RELIASTRA measures vendor reliabilityMethodology