Urgent maintenance on Object Storage in HEL+FSN
To ensure the stability and performance of our Object Storage in Helsinki (HEL) and Falkenstein (FSN), we are carrying out urgent maintenance work. During the maintenance, brief connection interruptions may occur. We apologize for any inconvenience and will provide an update once the work has been completed.
The latest update from Hetzner.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Hetzner
To ensure the stability and performance of our Object Storage in Helsinki (HEL) and Falkenstein (FSN), we are carrying out urgent maintenance work. During the maintenance, brief connection interruptions may occur. We apologize for any inconvenience and will provide an update once the work has been completed.
To ensure the stability and performance of our Object Storage in Falkenstein (FSN), we are carrying out urgent maintenance work. During the maintenance, brief connection interruptions may occur. We apologize for any inconvenience and will provide an update once the work has been completed.
Affected components
1Hetzner in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
18
Median duration
1 h 35 min
This incident
Not comparable
Other Hetzner incidents
All incidentsHetzner·Fault report on Hetzner Console
The Hetzner Console is not available. This affects only the Hetzner Console. The issue is resolved. The outage lasted 17 minutes.
Hetzner·Object Storage in location fsn1 partially degraded
Object Storage in location fsn1 is partially degraded. Requests to some buckets may fail or time out. Hetzner reports that it fixed the error and is monitoring the systems closely.
Hetzner·API failure for metrics
The API for metrics on the Cloud component did not work. Hetzner identified the issue and applied a fix. Hetzner reports that the problem is resolved after 4 hours and 57 minutes.
Hetzner·Object Storage in location HEL partially degraded
Hetzner Object Storage in location HEL is partially degraded. Write operations can take a long time, fail, or time out. Hetzner reports the state is monitoring and work on a fix continues.
Hetzner·Fault report on Cloud API and Hetzner Console
The Cloud API and the Hetzner Console did not work. Hetzner resolved the fault after 38 minutes. All systems are reachable again.
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