Object Storage in location fsn1 partially degraded
Hetzner Object Storage in location fsn1 was partially degraded. Some requests to buckets failed or timed out. Hetzner resolved the incident after 5 hours and 39 minutes.
State
Resolved
Started
Lasted
5 h 39 min
Worst impact
Major outage
Timeline
4 updatesInvestigating
2 h 6 min 37%
Monitoring
3 h 33 min 63%
Updates
Times in UTCAs posted by Hetzner
We were unable to identify any further issues and are therefore closing the status
We identified and blocked an abusive bucket that exhausted specific resources. Service for affected customers is fully restored.
The restrictions on the part of the cluster that were causing time-outs have now been resolved. We are continuing to monitor the situation so that we can take action if necessary.
Object Storage service in location fsn1 is currently only partially available. Requests to some buckets may fail or time out. We are currently investigating the issue.
Affected components
1Hetzner in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
8
Median duration
1 h 18 min
This incident
4.3× the median
Other Hetzner incidents
All incidentsHetzner·Object Storage in location FSN1 partially degraded
Hetzner Object Storage is partially degraded in location FSN1. The incident affected specific customer buckets. Hetzner reports that the problem is resolved. The outage lasted 5 hours and 51 minutes.
Hetzner·Fault report on Hetzner Console
Hetzner reports that a fault made the Cloud API and the Hetzner Console unavailable. The fault is resolved. All systems are reachable again. The outage lasted 1 hour and 2 minutes.
Hetzner·Cloud Router fault nbg1-cloud1-core_spine_rdev1
The fault has been fixed. All systems are accessible again
Hetzner·Outage of DHCP and Rescue Boot in FSN1
DHCP does not work in FSN1. This affects the rescue boot and installations through Robot. Hetzner reports that the issue is resolved. The outage lasted about 7 hours and 34 minutes.
Hetzner·Cloud Resource Creation Delay
Hetzner Cloud had a delay in creating and modifying resources in the Cloud component. The problem is resolved. The outage lasted 45 minutes. Creating and modifying resources works as usual.
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.live/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.live/feed.xml?providers=hetzner/feed subscribe https://outages.live/feed.xml?providers=hetznerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane