Helicone outage history

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

Uptime & history

Tracking since Jun 22, 2026
Currently up for 22d 5h 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.51%
0 incidents · ≈3h 30m degraded
8638 checks
Operational · since Jun 22, 2026
91.00%
0 incidents · ≈6h 45m down · ≈12d 16h degraded
41552 checks

% of our checks that found Helicone 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 Helicone fails

Since Jun 27, 2026, Helicone's status page has marked 4 Helicone components as impaired, across 4,123 of our five-minute readings. api.hconeai.com accounts for the most: 2,463 readings (about 205 hours) on 15 days, 2,463 of them marked as an outage rather than degraded, most recently on Oct 27, 2026. Next is eu.api.helicone.ai, with 1,654 readings on 13 days.

ComponentOutageDegradedMaint.DaysLast
api.hconeai.com2463——15Oct 27, 2026
eu.api.helicone.ai1654——13Oct 27, 2026
EU dashboard data3——1Oct 27, 2026
US dashboard data3——1Oct 27, 2026

Counts are five-minute readings of Helicone'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 Helicone's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Helicone.