outages.live
Live

Hetzner

Hetzner is operational

Checked 20 s ago Operational

History

90 days agoToday

Incidents in 90 days

5

Days with an incident

3

Median duration

1 h 34 min

Longest incident

2 h 15 min

Components

74

Cloud

Cloud Server Operational
90 days agoNo incidentsToday
Load Balancer Operational
90 days agoNo incidentsToday
Networks Operational
90 days agoNo incidentsToday
Object Storage Operational
90 days ago2 days with an incidentToday
Cloud Volume Operational
90 days agoNo incidentsToday
Dedicated Root Server Operational
90 days agoNo incidentsToday
Datacenter-Infrastructure Operational
90 days agoNo incidentsToday
DNS API Operational
90 days agoNo incidentsToday
FSN1-DC21 Operational
90 days agoNo incidentsToday
Hetzner API Operational
90 days agoNo incidentsToday

Managed

Managed Server Operational
90 days agoNo incidentsToday
Webhosting Operational
90 days agoNo incidentsToday

Storage

Storage Box Operational
90 days agoNo incidentsToday
Storage Share Operational
90 days agoNo incidentsToday

FSN1

FSN1-DC1 Operational
90 days agoNo incidentsToday
FSN1-DC2 Operational
90 days agoNo incidentsToday
FSN1-DC3 Operational
90 days agoNo incidentsToday
FSN1-DC4 Operational
90 days agoNo incidentsToday
FSN1-DC5 Operational
90 days agoNo incidentsToday
FSN1-DC6 Operational
90 days agoNo incidentsToday
FSN1-DC7 Operational
90 days agoNo incidentsToday
FSN1-DC8 Operational
90 days agoNo incidentsToday
FSN1-DC9 Operational
90 days agoNo incidentsToday
FSN1-DC10 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration26 min20:06 to 20:32DHCP degraded in FSN1 and NBG1Major outage

The issue was found and solved.

Oct 27, 2026

Duration1 h 34 min08:45 to 10:19Fault report on mirror (mirror.hetzner.de / download.hetzner.com / packages.hetzner.com)Major outage

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

Duration2 h 15 min07:15 to 09:30Object Storage in location nbg1 partially degradedMajor outage

The problem is fixed.

Oct 26, 2026

Duration2 h 4 min16:36 to 18:40Object Storage in location nbg1 partially degradedMajor outage

We have fixed the error. All systems are reachable again.

Duration46 min06:21 to 07:07API failure for metricsMajor outage

The problem is fixed.

Maintenance

Maintenance UPS systems in FSN1-DC22

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

Maintenancestarts in 13 h

Urgent maintenance on all core routers

We are currently carrying out urgent maintenance on all of our core routers. The routers are being serviced one after another. During this work, network redundancy is reduced globally. We do not expect any service interruptions, but you may experience increased latency. This maintenance ensures the long-term security and stability of our infrastructure. We appreciate your understanding and thank you for your patience.

Maintenanceupdated 17 d ago

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.cc/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.cc/feed.xml?providers=hetzner
Slack
/feed subscribe https://outages.cc/feed.xml?providers=hetzner

Go from tracking outages to fixing production issues with Polylane.

Try Polylane