Provider status detail
Linear
OperationalObserved brings together the current public status we can see and the limits of that collection in one place.
Status at a glance
Current status summary
Linear · Operational
- Snapshot time
- Snapshot age
- 47 seconds
- Freshness window
- 180 seconds
- Collected at
- Source
- Collected from the official Statuspage API.
- Fidelity
- Uses the status the official page directly asserts.
- Outcome
- Fetched the data without errors.
What to keep in mind
- Observed shows public status signals only.
- Official outage or maintenance notices and progress details are not mirrored here.
- Source
- Collected from the official Statuspage API.
- Fidelity
- Uses the status the official page directly asserts.
- Outcome
- Fetched the data without errors.
- Collected at
- Observed for
- 2026-08-05 15:04 UTC observed · ~21 hours
Observed change history
Recent observed changes
These rows are retained only when Observed sees an actual status-value change against the previous snapshot. This page filters this provider from the latest global retained window, so it is not complete per-provider history.
No retained transition events. An empty history is not a health guarantee; it only means no observed changes in the retained window.
Collection reality
What this page can and cannot say
Observed organizes public status signals honestly, but it is not private telemetry or an SLA adjudication system.
- Only signals visible on official public status pages and public incident feeds are used.
- Account-specific outages, private telemetry, and user-specific impact are not visible here.
- It does not guarantee uptime, SLA compliance, or availability.
- Stale, unknown, and collection failure are not healthy signals. Unobserved states are never corrected to green.
- Incident-feed “no reported incidents” means no listed incident was found; it is not an asserted-health signal.
Linear · Outcome: Fetched the data without errors. · Fidelity: Uses the status the official page directly asserts.