Cloud & hosting
Is Hetzner down?
Live Hetzner status, measured independently. We probe 7 Hetzner endpoints from monitoring regions on every continent and record every outage we detect.
Hetzner is up
Our probes are reaching Hetzner normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website99.93% uptime, 30 days6 regions, 28 to 1894 msUnknownp50median response933 msp95slowest 5% of checks1094 ms2000 ms1000024 h ago12 h agonow
- Cloud API100% uptime, 30 days6 regions, 54 to 1757 msUnknownp50median response948 msp95slowest 5% of checks1100 ms2000 ms1000024 h ago12 h agonow
- Cloud Console99.99% uptime, 30 days6 regions, 28 to 1120 msUnknownp50median response563 msp95slowest 5% of checks920 ms1000 ms500024 h ago12 h agonow
- DNS Console99.96% uptime, 30 days6 regions, 53 to 2514 msUnknownp50median response1172 msp95slowest 5% of checks1516 ms2000 ms1000024 h ago12 h agonow
- Documentation99.98% uptime, 30 days6 regions, 57 to 3158 msUnknownp50median response1576 msp95slowest 5% of checks1901 ms2000 ms1000024 h ago12 h agonow
- Status page99.97% uptime, 30 days6 regions, 64 to 1806 msUnknownp50median response1010 msp95slowest 5% of checks1110 ms2000 ms1000024 h ago12 h agonow
- DNS100% uptime, 30 days6 regions, 5 to 196 msUnknownp50median response131 msp95slowest 5% of checks221 ms200 ms100024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Hetzner goes down
Follow these 7 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Hetzner goes down. They don't count against your monitor quota. Free plan, no card required.
About Hetzner outages
Hetzner offers dedicated servers, Hetzner Cloud, and storage at prices that have made it the default choice for many indie developers and cost-conscious teams. Its footprint is concentrated in a handful of European data centres plus US and Singapore cloud locations, so network incidents at one site affect many customers at once.
We probe the website, the Cloud API, the Cloud Console, the DNS Console, the documentation, and that Hetzner's own status page is reachable. The Robot panel for dedicated servers rate-limits anonymous requests, so we do not probe it.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website hetzner.com is unreachable. | httpwww.hetzner.com | HTTP 200 | 1 min |
Cloud API The Hetzner Cloud API is not answering. hcloud, Terraform, and autoscalers fail. | httpapi.hetzner.cloud/v1/servers | HTTP 401 | 2 min |
Cloud Console The Cloud Console is unreachable. | httpconsole.hetzner.com | HTTP 200 | 1 min |
DNS Console Hetzner DNS console is unreachable. | httpdns.hetzner.com | HTTP 200 | 2 min |
Documentation Hetzner's documentation is unreachable. | httpdocs.hetzner.com | HTTP 200 | 5 min |
Status page Hetzner's own status page is unreachable. | httpstatus.hetzner.com | HTTP 200 | 5 min |
DNS hetzner.com is not resolving. | dnshetzner.com | A record resolves | 1 min |
For component-level detail and incident write-ups from the vendor, see Hetzner's official status page.
Recent Hetzner outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Hetzner is up. Is your Hetzner integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Hetzner and fail quietly. Here is what teams that rely on Hetzner monitor on their side.
Servers you run on Hetzner
Hetzner monitors its network and hardware, not your processes. Probe every public service and use heartbeats for cron jobs and workers on your boxes.
HTTP, TCP, and ICMP monitoringSSL certificates on self-managed servers
Self-hosting means certificate renewal is your problem. Get warned before a cert expires.
SSL certificate monitoringHetzner status: frequently asked questions
If our probes to Hetzner's website, API, and console are green from every region, the platform is reachable and the problem is likely specific to your server, its network configuration, or your data centre. Hetzner's status page lists per-location incidents; compare it with a ping and a TCP check on your own host.
Look at the per-region results above. If our probes fail from every region, Hetzner has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Hetzner may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Hetzner" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Hetzner: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
upti.my is not affiliated with Hetzner. Hetzner and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.