Object Storage in location FSN1 partially degraded
Hetzner Object Storage in location FSN1 was partially degraded. The incident affected specific customer buckets. Hetzner resolved the problem and the service runs as expected again. The outage lasted about 5 hours and 51 minutes.
State
Resolved
Started
Lasted
5 h 51 min
Worst impact
Major outage
Timeline
3 updatesInvestigating
2 h 35 min 44%
Monitoring
3 h 16 min 56%
Updates
Times in UTCAs posted by Hetzner
The problem has been resolved; the service is now running as expected again
We were able to pinpoint and resolve the problem. We will continue to monitor the situation to ensure that we haven’t overlooked anything.
This incident only affects specific customer buckets. We are investigating the root cause.
Affected components
1Hetzner in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
7
Median duration
1 h
This incident
5.8× the median
Other Hetzner incidents
All incidentsHetzner·Fault report on Hetzner Console
The Hetzner Console and the Cloud API in the Cloud component did not work. Hetzner restored the systems and now monitors them. Hetzner reports that the outage is resolved. It lasted about 62 minutes.
Hetzner·Cloud Router fault nbg1-cloud1-core_spine_rdev1
The fault has been fixed. All systems are accessible again
Hetzner·Cloud Resource Creation Delay
Hetzner Cloud had a delay in creating and modifying resources. The problem is resolved and the outage lasted 45 minutes.
Hetzner·Fault report for Cloud DNS API and reverse DNS APIs (Primary IP, Floating IPs, Cloud Server, Load Balancer)
Hetzner reports that the Cloud DNS API and the reverse DNS APIs for Primary IPs, Floating IPs, Cloud Servers and Load Balancers did not work. Managed Certificate issuance was also affected. Hetzner resolved the outage after 58 minutes.
Hetzner·DHCP degraded in FSN1 and NBG1
The issue was found and solved.
Follow Hetzner
Your coding agent knows when Hetzner is down, and tells you when a failure is theirs, not yours. You can also get Hetzner incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hetzner" and tell me if Hetzner has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=hetzner/feed subscribe https://outages.cc/feed.xml?providers=hetznerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane