Skip to main content

Is Hetzner Down?

No — Hetzner is up

Reachable from all 8 checked regions

Average response time: 609ms

Last checked · checks run every 6 hours

Official status page: https://status.hetzner.com

Backbone connection fault between Frankfurt - Helsinki

critical watching

The issue has not reoccurred over the weekend. We are continuing to monitor the situation and are still awaiting feedback from the service provider.

Components the vendor reports as affected: Cloud Server Issue Object Storage Issue Cloud Volume Issue Backbone Outage Phone system Issue

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Hetzner fail from enough regions to rule out probe noise.

Hetzner uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
735ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 9 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: 100.00% uptime, 16 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 31 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
84ms
DNS 0ms TCP 13ms TLS 15ms TTFB 57ms
arn
167ms
DNS 0ms TCP 26ms TLS 33ms TTFB 114ms
bom
742ms
DNS 0ms TCP 123ms TLS 124ms TTFB 495ms
cdg
96ms
DNS 0ms TCP 15ms TLS 17ms TTFB 65ms
dfw
767ms
DNS 0ms TCP 127ms TLS 128ms TTFB 511ms
ewr
551ms
DNS 0ms TCP 91ms TLS 93ms TTFB 369ms
syd
1866ms
DNS 0ms TCP 10ms TLS 311ms TTFB 1244ms
yyz
602ms
DNS 0ms TCP 99ms TLS 101ms TTFB 402ms

What Hetzner does

Hetzner is a German hosting provider running cloud servers, dedicated machines and colocation. Its cloud product covers shared and dedicated-vCPU instances, private networks, stateful firewalls, load balancers, volumes and object storage, from datacenters in Falkenstein, Nuremberg, Helsinki, Hillsboro, Ashburn and Singapore. Its pricing makes it a common home for side projects and for production workloads run by small engineering teams.

What an outage looks like

Cloud servers become unreachable over SSH and stop answering on their public addresses, usually confined to one location rather than all of them. Object Storage requests time out or return errors while compute keeps running. The Hetzner Console will not load or sign in, so you cannot reboot or rebuild an affected machine. Backbone or datacenter-level faults take out every service in one location at once.

What to do about it

Check status.hetzner.com, which separates ongoing Information items from Planned maintenance and Resolved incidents, and names the affected location. Confirm whether the fault is your machine or the location before rebuilding anything, because a rebuild during a network-level incident destroys a working server for no reason. Hetzner announces datacenter and backbone maintenance in advance on the same page, so check the maintenance list before assuming an unplanned outage.

Is it down for everyone, or just you?

If this page says Hetzner is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Hetzner outage FAQ

Is Hetzner down or is it just my server?
Check status.hetzner.com for an Information item naming your location, then compare the per-region measurements here. A platform incident affects a whole datacenter and is announced; a single unreachable machine with everything else in the location working is almost always your own server, usually a full disk, an out-of-memory kill or a firewall rule applied to the wrong port.
Does a Hetzner outage affect all datacenters at once?
Rarely. Hetzner's incidents are typically scoped to one location, and the status page names it, because Falkenstein, Nuremberg, Helsinki, Hillsboro, Ashburn and Singapore run as separate sites. Shared services such as the Console, billing or the ticket system are the exception: those are listed separately and a fault there affects customers everywhere, even while their servers keep running normally.
Can I reach my server when the Hetzner Console is down?
Yes, if the server itself is healthy. The Console is a management surface, so an outage there stops you rebooting, resizing or rebuilding, but running machines keep serving traffic and SSH keeps working. This is the argument for configuring out-of-band access and keeping infrastructure changes scripted through the API, which is tracked separately from the web console.
Is scheduled maintenance the same as an outage?
No, and Hetzner lists them separately. The Planned maintenance section carries upcoming work with dates, often affecting a single datacenter, a mirror service or the accounts system. If your servers went unreachable at a time that matches a listed maintenance window, the cause is announced work rather than a fault, and the resolution is to wait it out rather than to escalate.

How we measure this

  • We request Hetzner's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Hetzner publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Hetzner goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required