Is Hetzner down?
No, Hetzner is not down.
Hetzner’s status page reports no incidents, api.hetzner.cloud and robot-ws.your-server.de responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.hetzner.com
- Reachable6 of 6 regionsHetzner Cloud API 6/6 · Robot API (dedicated servers) 6/6
- Reports in the last hour0Normal
Hetzner’s status page
From status.hetzner.com. Read at
Maintenance under way, to : Maintenance UPS systems in HEL1-DC6.
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 611 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.hetzner.cloud)
By region
| Region | Hetzner Cloud API api.hetzner.cloud | Robot API (dedicated servers) robot-ws.your-server.de |
|---|---|---|
| N. Virginia us-east-1 | 401 · 394 ms | 401 · 406 ms |
| Oregon us-west-2 | 401 · 716 ms | 401 · 702 ms |
| Frankfurt eu-central-1 | 401 · 33 ms | 401 · 43 ms |
| Singapore ap-southeast-1 | 401 · 902 ms | 401 · 692 ms |
| Tokyo ap-northeast-1 | 401 · 1017 ms | 401 · 1017 ms |
| São Paulo sa-east-1 | 401 · 809 ms | 401 · 833 ms |
Two regions check Hetzner every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Hetzner ourselves since Oct 28, 2026. Earlier days come from its status page.
47 days with problems in the last 90 days.
Recent incidents
Incidents: 6 in the last 30 days and 8 in the last 90, lasting a median of 2 h 8 min.
- Fault report on mirror (mirror.hetzner.de / download.hetzner.com / packages.hetzner.com)Partial outage1 h 34 min
- Object Storage in location nbg1 partially degradedPartial outage2 h 14 min
- Object Storage in location nbg1 partially degradedPartial outage2 h 3 min
- API failure for metricsPartial outage46 min
- Router fault fra-core8Partial outage2 h 17 min
- Technical issues with vSwitch MAC learningPartial outage1 day
- Object Storage in location HEL1 partially degradedPartial outage43 days
- Outage of DENIC servicesDegraded1 h 7 min
If Hetzner isn’t working for you
Hetzner is a German hosting company offering low-cost cloud servers, dedicated servers and storage in Europe, the US and Singapore.
Common Hetzner errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
resource_unavailable | A 412 error: the requested resource is currently unavailable, for example not available for order in that location. | Heavy load | Try another server type or location. Source |
resource_limit_exceeded | A 403 error: your account hit the maximum quantity of that resource. | Your side | Request a limit increase in the Cloud Console. Source |
rate_limit_exceeded | A 429 error: too many API requests. | Your side | Slow down and wait for the rate limit to reset. Source |
server_error | A 500 error inside the Hetzner API backend. | An outage | Retry and check status.hetzner.com. Source |
unavailable | A 503 error: a service or product is currently not available. | An outage | Retry later and check status.hetzner.com. Source |
Is it just you?
- Check status.hetzner.com for your location; most incidents affect one datacenter or product.
- Use the Cloud Console's server console to tell a crashed server from a network problem.
- For resource_unavailable, try a different server type or location; capacity varies by location.
- Check your account limits in the Cloud Console before treating limit errors as an outage.
Alternatives to Hetzner
Questions
Common causes are capacity in that location (resource_unavailable), account limits (resource_limit_exceeded) and API rate limits. The error code in the API or console response tells you which.
If the Cloud Console works and other servers respond, the problem is likely your server. Hetzner posts incidents per location and product at status.hetzner.com.
Sources: docs.hetzner.cloud, status.hetzner.com
Get alerted when Hetzner breaks your app.
If your product or your team depends on Hetzner, its outage is your outage, and your users will blame you, not Hetzner. Point a Site Qwality monitor at the Hetzner endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.