outages.live
Live
HetznerIncident ·

Cloud Router fault nbg1-cloud1-core_spine_rdev1

ResolvedOfficial update
0

The fault has been fixed. All systems are accessible again

The latest update from Hetzner.

State

Resolved

Started

Lasted

7 min

Worst impact

Major outage

Timeline

1 update
15:0315:0415:0615:0815:10
NoticeUpdate postedTimes in UTC

Resolved

7 min 100%

Updates

Times in UTC

As posted by Hetzner

Resolved

The fault has been fixed. All systems are accessible again

Affected components

1
Cloud-Network

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

5

Median duration

58 min

This incident

88% shorter than the median

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

7 h 34 min
median 58 min
90 days agoToday

Other Hetzner incidents

All incidents

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

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.

Resolved

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 reports that the outage is resolved. It lasted about 58 minutes.

Resolved

Hetzner·DHCP degraded in FSN1 and NBG1

The issue was found and solved.

Resolved

Hetzner·Fault report on mirror (mirror.hetzner.de / download.hetzner.com / packages.hetzner.com)

We have fixed the fault. The system is accessible again.

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