outages.live
Live
HetznerMaintenance ·

UPS function tests in FSN1-DC1

MaintenanceOfficial update

We will do routine function tests on our UPS systems. Due to the redundant design of our power supply systems, we do not expect any issues.

The latest update from Hetzner.

State

Planned

Started

Ongoing for

21 min

Worst impact

Maintenance

Timeline

1 update
06:3006:3506:4006:4506:51
MaintenanceUpdate postedTimes in UTC

Planned

21 min 100%

Updates

Times in UTC

As posted by Hetzner

Planned

We will do routine function tests on our UPS systems. Due to the redundant design of our power supply systems, we do not expect any issues.

Affected components

1
FSN1-DC1

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

12

Days with an incident

8

Median duration

1 h 18 min

This incident

Not comparable

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

7 h 34 min
median 1 h 18 min
90 days agoToday

Other Hetzner incidents

All incidents

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

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

Resolved

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.

Resolved

Hetzner·Cloud Router fault nbg1-cloud1-core_spine_rdev1

The fault has been fixed. All systems are accessible again

Resolved

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.

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