Uptimy

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 uptime
7d uptime
30d uptime
  • Website
    100% uptime, 30 days
    5 regions, 29 to 1049 ms
    Checking
    p50
    744 ms
    Median response
    p95
    899 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Cloud API
    100% uptime, 30 days
    6 regions, 50 to 1723 ms
    Checking
    p50
    950 ms
    Median response
    p95
    1176 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Cloud Console
    99.79% uptime, 30 days
    6 regions, 28 to 1133 ms
    Checking
    p50
    569 ms
    Median response
    p95
    1523 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • DNS Console
    99.59% uptime, 30 days
    6 regions, 50 to 2456 ms
    Checking
    p50
    1247 ms
    Median response
    p95
    2105 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Falkenstein (FSN1)
    99.95% uptime, 30 days
    6 regions, 18 to 1064 ms
    Checking
    p50
    527 ms
    Median response
    p95
    544 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Nuremberg (NBG1)
    99.98% uptime, 30 days
    6 regions, 13 to 1058 ms
    Checking
    p50
    517 ms
    Median response
    p95
    531 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Helsinki (HEL1)
    99.94% uptime, 30 days
    6 regions, 67 to 1105 ms
    Checking
    p50
    570 ms
    Median response
    p95
    585 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Ashburn (ASH)
    99.97% uptime, 30 days
    6 regions, 270 to 724 ms
    Checking
    p50
    492 ms
    Median response
    p95
    584 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Hillsboro (HIL)
    99.98% uptime, 30 days
    6 regions, 77 to 938 ms
    Checking
    p50
    510 ms
    Median response
    p95
    596 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Singapore (SIN)
    99.93% uptime, 30 days
    6 regions, 6 to 1003 ms
    Checking
    p50
    586 ms
    Median response
    p95
    632 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Object Storage Falkenstein
    100% uptime, 30 days
    6 regions, 32 to 1298 ms
    Checking
    p50
    657 ms
    Median response
    p95
    953 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Object Storage Nuremberg
    99.76% uptime, 30 days
    6 regions, 37 to 1352 ms
    Checking
    p50
    675 ms
    Median response
    p95
    955 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Object Storage Helsinki
    100% uptime, 30 days
    6 regions, 80 to 1354 ms
    Checking
    p50
    710 ms
    Median response
    p95
    995 ms
    Slowest 5% of checks
    1000 ms5000
    24 h ago12 h agonow
  • Documentation
    100% uptime, 30 days
    5 regions, 60 to 1781 ms
    Checking
    p50
    1260 ms
    Median response
    p95
    1402 ms
    Slowest 5% of checks
    2000 ms10000
    24 h ago12 h agonow
  • Status page
    99.99% uptime, 30 days
    6 regions, 67 to 1737 ms
    Checking
    p50
    1100 ms
    Median response
    p95
    1294 ms
    Slowest 5% of checks
    5000 ms25000
    24 h ago12 h agonow
  • DNS
    100% uptime, 30 days
    6 regions, 5 to 199 ms
    Checking
    p50
    114 ms
    Median response
    p95
    214 ms
    Slowest 5% of checks
    200 ms1000
    24 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.

Notify me about Hetzner

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.

CheckTargetExpectsInterval
Website
hetzner.com is unreachable.
httpwww.hetzner.comHTTP 2001 min
Cloud API
The Hetzner Cloud API is not answering. hcloud, Terraform, and autoscalers fail.
httpapi.hetzner.cloud/v1/serversHTTP 4012 min
Cloud Console
The Cloud Console is unreachable.
httpconsole.hetzner.comHTTP 2001 min
DNS Console
Hetzner DNS console is unreachable.
httpdns.hetzner.comHTTP 2002 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.comHTTP 2001 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.comHTTP 2001 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.comHTTP 2001 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.comHTTP 2001 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.comHTTP 2001 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.comHTTP 2001 min
Object Storage Falkenstein
The Falkenstein Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable.
httpfsn1.your-objectstorage.comHTTP 2002 min
Object Storage Nuremberg
The Nuremberg Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable.
httpnbg1.your-objectstorage.comHTTP 2002 min
Object Storage Helsinki
The Helsinki Object Storage endpoint is not answering. S3-compatible buckets in that location are unreachable.
httphel1.your-objectstorage.comHTTP 2002 min
Documentation
Hetzner's documentation is unreachable.
httpdocs.hetzner.comHTTP 2005 min
Status page
Hetzner's own status page is unreachable.
httpstatus.hetzner.comHTTP 2005 min
DNS
hetzner.com is not resolving.
dnshetzner.comA record resolves1 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

Hetzner status

Markdown

[![Hetzner status](https://www.upti.my/status/hetzner/badge.svg)](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 monitoring

SSL certificates on self-managed servers

Self-hosting means certificate renewal is your problem. Get warned before a cert expires.

SSL certificate monitoring

Hetzner 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.

23:00 · goodnight

All systems operational

Stop wondering if production is okay.

Tonight, if something breaks, you will know first — with the context to fix it and a status page that keeps customers informed. And if nothing breaks, you get to sleep.

Free plan available · No credit card required · Cancel anytime