Is Helicone down?
Right now
No. Helicone is operational.
No incidents reported.
Read from status.helicone.ai · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/helicone/status.agent.json
MCP: upstream_status {"service":"helicone"}
LLM gateway and request logging. It sits on the request path, so its outages fail model calls.
What Helicone reports
Operational
Taken as is from Helicone's own status page API. Incident titles and component names below are theirs.
Open status.helicone.aiUpButler's independent probe
There is no keyless endpoint of Helicone that says anything useful, so UpButler does not probe it. To check your own Helicone account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Helicone components
3 operational
- helicone.aiNo data
- api.hconeai.comOperational
- eu.api.helicone.aiOperational
Helicone incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Helicone publishes for 90 days from the day it starts tracking a service.
Tell your outage from Helicone's
Declare that your project depends on Helicone. When one of your monitors fails while Helicone has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- heliconecurl -s https://upbutler.com/status/helicone/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "helicone",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Helicone down right now?
- No. As of 2026-10-10 05:11 UTC, Helicone is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Helicone's own status page API at https://status.helicone.ai. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Helicone's words.
- How can my agent or app check Helicone status?
- Fetch https://upbutler.com/status/helicone/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"helicone"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Helicone's?
- Add "helicone" to the dependencies of your UpButler workspace. When one of your monitors fails while Helicone has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in observability and analytics
UpButler is not affiliated with Helicone. Status and incident text belong to Helicone and are read from their public status source; the probe result is UpButler's own measurement.