Is Hetzner down?
Loading the latest status…
Is Hetzner down right now? Live status from Hetzner’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
Hetzner’s status page
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- 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 | ||
| Oregon | ||
| Frankfurt | ||
| Singapore | ||
| Tokyo | ||
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked Hetzner ourselves since Oct 28, 2026. Earlier days come from its status page.
17 days with problems in the last 90 days.
Recent incidents
Incidents: 7 in the last 30 days and 7 in the last 90, lasting a median of 3 h 2 min. Our checks flagged problems a median of 5924 minutes before Hetzner’s status page did.
- Fault report on Cloud API and Hetzner ConsolePartial outage38 min
- API failure for metricsPartial outage1 h 36 min
- Object Storage in location fsn1 partially degradedPartial outage1 day
- API failure for metricsPartial outage3 h 2 min
- Object Storage in location fsn1 partially degradedPartial outage12 daysOur checks saw it 13530 min before the status page
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 depends on Hetzner, your users feel its outages too. Point a Site Qwality monitor at the Hetzner endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.