outages.live
Live
HetznerIncident ·

Object Storage in location HEL partially degraded

Major outageOfficial update
0

Hetzner reports that Object Storage in location HEL is partially degraded. Write operations may take a long time, fail, or time out. Hetzner is investigating and works on a fix.

State

Investigating

Started

Ongoing for

36 min

Worst impact

Major outage

Timeline

1 update
11:1411:2311:3311:4211:51
Major outageUpdate postedTimes in UTC

Investigating

36 min 100%

Updates

Times in UTC

As posted by Hetzner

Investigating

The Object Storage service in location HEL is currently partially degraded. Write operations may take unexpectedly long or fail or time out. We are already working on fixing the issue and getting things back to normal.

Affected components

1
Object Storage

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

11

Median duration

1 h 35 min

This incident

62% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

32 h 54 min
median 1 h 35 min
90 days agoToday

Other Hetzner incidents

All incidents

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.

Resolved

Hetzner·API failure for metrics

Hetzner reports that the API endpoints for metrics on Cloud, /servers/{id}/metrics and /loadbalancers/{id}/metrics, failed or returned incomplete data. Hetzner identified the issue and applied a fix. The incident is resolved and lasted 97 minutes.

Resolved

Hetzner·Object Storage in location fsn1 partially degraded

Hetzner reports that Object Storage in location fsn1 does not fully work. Some requests to buckets failed or timed out. Hetzner fixed the problem and resolved the incident. The outage lasted 32 hours and 54 minutes.

Resolved

Hetzner·API failure for metrics

Hetzner Cloud metrics API endpoints failed. The endpoints /servers/{id}/metrics and /loadbalancers/{id}/metrics returned errors or incomplete data. Hetzner resolved the outage after 2 hours and 55 minutes.

Resolved

Hetzner·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.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=hetzner
Slack
/feed subscribe https://outages.live/feed.xml?providers=hetzner

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane