outages.live
Live
HetznerIncident ·

Cloud Resource Creation Delay

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

45 min

Worst impact

Major outage

Timeline

4 updates
12:0312:1412:2512:3712:48
Major outageUpdate postedTimes in UTC

In progress

21 min 47%

Monitoring

24 min 53%

Updates

Times in UTC

As posted by Hetzner

Resolved

The problem is fixed and creating and modifying resources works as usual.

Monitoring

The problem has been found and resolved, but it'll still take a while to process the backlog.

Monitoring

Das Problem wurde gefunden und behoben, aber es wird noch einige Zeit dauern bis das Backlog abgearbeitet ist.

In progress

Currently there is a delay in creating or modifying resources in the Hetzner Cloud.

Affected components

1
Cloud

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

7

Days with an incident

4

Median duration

58 min

This incident

22% shorter than the median

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

2 h 15 min
median 58 min
90 days agoToday

Other Hetzner incidents

All incidents

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

Hetzner·Object Storage in location nbg1 partially degraded

The problem is fixed.

Resolved

Hetzner·Object Storage in location nbg1 partially degraded

We have fixed the error. All systems are reachable 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