outages.live
Live
HetznerMaintenance · 2026-11-03 08:00 UTC

Load Balancers: Security relevant maintenance work

MaintenanceOfficial update

We will be performing routine maintenance work on Load Balancers in all locations. During this maintenance work, there may be a short connection loss from the active connections (TCP and HTTP) to the Load Balancers, or from the Load Balancers to their targets.

The latest update from Hetzner.

State

Planned

Starts

in 10 h

2026-11-03 08:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Hetzner

Planned2026-11-02 19:00 UTC

We will be performing routine maintenance work on Load Balancers in all locations. During this maintenance work, there may be a short connection loss from the active connections (TCP and HTTP) to the Load Balancers, or from the Load Balancers to their targets.

Affected components

1
Load Balancer

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

3

Median duration

1 h 34 min

This incident

Not comparable

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

2 h 15 min
median 1 h 34 min
90 days agoToday

Other Hetzner incidents

All incidents

Hetzner·DHCP degraded in FSN1 and NBG1

The issue was found and solved.

Resolvedresolved 5 d ago

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

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

Resolvedresolved 6 d ago

Hetzner·Object Storage in location nbg1 partially degraded

The problem is fixed.

Resolvedresolved 7 d ago

Hetzner·Object Storage in location nbg1 partially degraded

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

Resolvedresolved 7 d ago

Hetzner·API failure for metrics

The problem is fixed.

Resolvedresolved 8 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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane