Is Hetzner down?
For agents
proceed
Proceed.
GET upbutler.com/status/hetzner/status.agent.json
MCP: upstream_status {"service":"hetzner"}
Hetzner Cloud and dedicated servers.
What Hetzner reports
Operational
Taken as is from Hetzner's own incident feed. Incident titles and component names below are theirs.
Open status.hetzner.comUpButler's independent probe
There is no keyless endpoint of Hetzner that says anything useful, so UpButler does not probe it. To check your own Hetzner account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Hetzner incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Object Storage in location HEL1 partially degraded | minor | under a minute | |
| New vSwitch IP/MAC Limits | minor | under a minute |
Tell your outage from Hetzner's
Declare that your project depends on Hetzner. When one of your monitors fails while Hetzner 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:
- hetznercurl -s https://upbutler.com/status/hetzner/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "hetzner",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Hetzner down right now?
- No. As of 2026-10-10 05:07 UTC, Hetzner is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Hetzner's own incident feed at https://status.hetzner.com. 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 Hetzner's words.
- How can my agent or app check Hetzner status?
- Fetch https://upbutler.com/status/hetzner/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":"hetzner"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Hetzner's?
- Add "hetzner" to the dependencies of your UpButler workspace. When one of your monitors fails while Hetzner 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 cloud and edge
UpButler is not affiliated with Hetzner. Status and incident text belong to Hetzner and are read from their public status source; the probe result is UpButler's own measurement.