Cloud & hosting
Is Hetzner down?
Live Hetzner status, measured independently. We probe 16 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.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.98% uptime, 30 days5 regions, 28 to 1050 msCheckingp50738 msMedian responsep95886 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Cloud API99.99% uptime, 30 days6 regions, 52 to 1893 msCheckingp50971 msMedian responsep951126 msSlowest 5% of checks2000 ms1000024 h ago12 h agonow
- Cloud Console99.98% uptime, 30 days6 regions, 29 to 1181 msCheckingp50564 msMedian responsep95943 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- DNS Console99.97% uptime, 30 days6 regions, 51 to 2662 msCheckingp501244 msMedian responsep951574 msSlowest 5% of checks2000 ms1000024 h ago12 h agonow
- Falkenstein (FSN1)99.96% uptime, 30 days6 regions, 18 to 1120 msCheckingp50533 msMedian responsep95555 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Nuremberg (NBG1)99.98% uptime, 30 days6 regions, 13 to 1116 msCheckingp50527 msMedian responsep95559 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Helsinki (HEL1)99.96% uptime, 30 days6 regions, 67 to 1129 msCheckingp50573 msMedian responsep95592 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Ashburn (ASH)99.98% uptime, 30 days6 regions, 178 to 714 msCheckingp50475 msMedian responsep95495 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Hillsboro (HIL)99.98% uptime, 30 days6 regions, 72 to 938 msCheckingp50504 msMedian responsep95516 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Singapore (SIN)99.91% uptime, 30 days6 regions, 5 to 993 msCheckingp50595 msMedian responsep95627 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Object Storage Falkenstein99.99% uptime, 30 days6 regions, 27 to 1518 msCheckingp50717 msMedian responsep95985 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Object Storage Nuremberg99.59% uptime, 30 days6 regions, 29 to 1422 msCheckingp50666 msMedian responsep95979 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Object Storage Helsinki99.99% uptime, 30 days6 regions, 76 to 1488 msCheckingp50733 msMedian responsep951027 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Documentation99.98% uptime, 30 days5 regions, 56 to 1771 msCheckingp501243 msMedian responsep951341 msSlowest 5% of checks2000 ms1000024 h ago12 h agonow
- Status page100% uptime, 30 days6 regions, 66 to 1833 msCheckingp501021 msMedian responsep951105 msSlowest 5% of checks2000 ms1000024 h ago12 h agonow
- DNS100% uptime, 30 days6 regions, 13 to 327 msCheckingp50164 msMedian responsep95266 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Hetzner goes down
Follow these 16 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 each Hetzner location directly: Falkenstein, Nuremberg, Helsinki, Ashburn, Hillsboro, and Singapore each have a probe against a host inside that data centre, plus the Object Storage endpoint in the three European locations. A red location means servers there are unreachable from the public internet, not that Hetzner's website has a problem.
Alongside the locations 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 Uptimy, 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 |
Falkenstein (FSN1) Servers in Hetzner's Falkenstein datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httpfsn1-speed.hetzner.com | HTTP 200 | 1 min |
Nuremberg (NBG1) Servers in Hetzner's Nuremberg datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httpnbg1-speed.hetzner.com | HTTP 200 | 1 min |
Helsinki (HEL1) Servers in Hetzner's Helsinki datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httphel1-speed.hetzner.com | HTTP 200 | 1 min |
Ashburn (ASH) Servers in Hetzner's Ashburn, Virginia datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httpash-speed.hetzner.com | HTTP 200 | 1 min |
Hillsboro (HIL) Servers in Hetzner's Hillsboro, Oregon datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httphil-speed.hetzner.com | HTTP 200 | 1 min |
Singapore (SIN) Servers in Hetzner's Singapore datacenter are unreachable from the public internet. Cloud servers, dedicated servers and load balancers hosted there are affected. | httpsin-speed.hetzner.com | HTTP 200 | 1 min |
Object Storage Falkenstein The Falkenstein Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable. | httpfsn1.your-objectstorage.com | HTTP 200 | 2 min |
Object Storage Nuremberg The Nuremberg Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable. | httpnbg1.your-objectstorage.com | HTTP 200 | 2 min |
Object Storage Helsinki The Helsinki Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable. | httphel1.your-objectstorage.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.
Embed a live Hetzner badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/hetzner?utm_source=badge)HTML
<a href="https://www.upti.my/status/hetzner?utm_source=badge"><img src="https://www.upti.my/status/hetzner/badge.svg" alt="Hetzner status"></a>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
Check the probe for your server's location first. If Falkenstein, Nuremberg, Helsinki, Ashburn, Hillsboro, or Singapore is red from every region, that data centre is unreachable and Hetzner is having a network incident there. If your location is green along with the website, API, and console, the problem is specific to your server, its firewall, or its network configuration; a ping and a TCP check on your own host will confirm it.
Every Hetzner location runs a public host inside that data centre, and we request it every minute from our regions on several continents. Object Storage in Falkenstein, Nuremberg, and Helsinki has its own endpoint per location, so it is probed separately. A location only turns red when every one of our regions fails to reach it, which rules out a routing problem between one of our regions and Hetzner.
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 Uptimy 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
Uptimy 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.