Comet outage history

We record Comet's status every five minutes and have not recorded an incident from Comet's status page yet. We never invent one.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 24d 2h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
99.70%
0 incidents · ≈2h 10m degraded
8638 checks
Operational · since Jun 22, 2026
99.78%
0 incidents · ≈7h 45m degraded
41560 checks

% of our checks that found Comet fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow

How Comet fails

Since Oct 12, 2026, Comet's status page has marked 2 Comet components as impaired, across 32 of our five-minute readings. Opik Website API accounts for the most: 26 readings (about 2.2 hours) on 2 days, 26 of them marked as an outage rather than degraded, most recently on Oct 26, 2026. Next is Opik Docs, with 6 readings on 1 day.

ComponentOutageDegradedMaint.DaysLast
Opik Website API26——2Oct 26, 2026
Opik Docs6——1Oct 12, 2026

Counts are five-minute readings of Comet's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Incidents and their updates are Comet's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Comet.