Orbital WatchtowerPublic Status JournalAll times UTC

Availability history

Thirty days of published service state.

The availability window keeps one daily classification per monitored surface and preserves shorter degraded intervals in the incident archive.

Window30 days
Services5
Degraded intervals1
Disruptions0

Availability by service

Daily cells describe the published classification for that UTC day. A degraded cell can represent a shorter event and does not mean the service was degraded for the entire day.

Public website
30 daily readings
100%
Status page
30 daily readings
100%
Status API
30 daily readings
99.90%
Records archive
30 daily readings
100%
Contact page
30 daily readings
100%
OperationalDegradedDisruptionMaintenanceNo data
Published through Jul 10

How availability is classified

Observed surface

Each service is a public page or endpoint that can be checked directly.

Daily state

The most significant reliable state for the UTC day is retained.

Short events

Exact start and end times live in the incident record.

Missing evidence

Unknown intervals are marked No data instead of assumed healthy.

Maintenance

Planned work is classified separately from incidents.

Availability calculation

The percentage is the published successful availability across the five public surfaces during the stated window. Daily cells are a readable classification layer; they are not a raw request log or a service-level guarantee.

Recorded interval

Jun 22: Status API degraded

Increased response latency was published for 24 minutes. The service remained reachable and returned to normal at 10:02 UTC. Read OW-2026-0622 →