Is Hetzner down?

Hetzner reports a partial outage right now.

As reported on status.hetzner.com, read on
Partial outage
incidents in the last 90 days
3
days since the last incident
0

Phare never probes Hetzner itself: an outage shows up here once Hetzner announces it. Times are UTC.

Ongoing incidents

As Hetzner reports it, latest update first.

Impact not stated · Investigating

API failure for metrics

Started 1 hour ago, UTC. Affects Cloud.

Follow it on status.hetzner.com

  1. Update

    API endpoints for metrics (/servers/{id}/metrics and /load_balancers/{id}/metrics) are failing or data may be incomplete. Monitoring 2026-11-12T14:11:49+00:00 We have fixed the error. We are monitoring the systems closely. In_progress 2026-11-12T13:23:07+00:00 We have identified the issue and are working on a fix. The service will be available again once the fix has been applied.

    Show more

Partial outage · Investigating

Object Storage in location fsn1 partially degraded

Started 12 hours ago, UTC. Affects Object Storage.

Follow it on status.hetzner.com

  1. Update

    Object Storage service in location fsn1 is currently only partially available. Requests to some buckets may fail or time out. We are currently investigating the issue. Monitoring 2026-11-12T03:32:19+00:00 We have fixed the error. We are monitoring the systems closely.

No impact · Investigating

CVE-2026-97631 - critical security vulnerability in the EDK II UEFI firmware component

Started 2 weeks ago, UTC.

Follow it on status.hetzner.com

  1. Update

    A critical security vulnerability has recently been identified in the EDK II UEFI firmware component (CVE-2026-97631, CVSS 9.5). Further details can be found in the advisory: https://github.com/tianocore/edk2/security/advisories/GHSA-99cj-7hg9-mp4m What is affected? The vulnerability affects systems that boot over the network using PXE. During the boot process, an attacker may be able to execute malicious code through specially crafted network packets, even before the operating system and its security mechanisms (e.g., Secure Boot) are active. Systems that are already running are not directly at risk; the vulnerability can only be exploited during a PXE boot. An official patch is not yet available. What do we recommend? As an immediate precautionary measure, we recommend avoiding reboots of your hosts until further notice if they use PXE boot. What happens next? We are currently analyzing the impact on our environment and developing further recommendations and additional protective measures. We will inform you promptly as soon as new findings or updates become available. Update 2026-11-10T14:46:24+00:00 Network filters are now active across our entire infrastructure, including the data center networks for dedicated servers. Based on our current knowledge, the vulnerability can therefore no longer be exploited. Reboots are possible again without additional precautions. Update 2026-11-03T09:56:06+00:00 Network filters have already been in place for cloud servers for some time. These protective measures are now fully implemented across our Cloud infrastructure, resolving the issue for Cloud. For dedicated (bare-metal) servers, we are continuing to explore ways to further expand these protective measures within our data center networks. Update 2026-11-02T13:03:18+00:00 The network filters described in our last update are now active at our network edge and between our locations. We are completing the rollout of the filters on cloud servers today. For dedicated (BareMetal) servers, we are currently evaluating how to extend these protective measures further within our DC networks. Until then, our previous recommendations still apply, especially for dedicated servers: Please avoid reboots where possible, and if a reboot is necessary, temporarily block incoming ICMP packets using the Hetzner Firewall. We will keep you informed about further progress. Update 2026-10-30T16:07:21+00:00 We're implementing filters in our network, which will drop fragmented ICMPv4 packets, as well as ICMPv4 errors larger than 768 bytes. In particular: Any IPv4 packet with protocol ICMP and the "More Fragments (MF)" flag or non-zero "Fragment Offset" will be dropped. We will also drop any ICMPv4 packets that are of type 3 (Destination Unreachable), 4 (Source Quench), 5 (Redirect), 11 (Time Exceeded), or 12 (Parameter Problem), when their IPv4 header has a "Total Length" >= 768 bytes. Our previous recommendations on how to protect your systems still apply. Update 2026-10-29T12:34:52+00:00 What is affected? Dedicated Servers (bare-metal servers) and Cloud VMs running with UEFI. On Linux, you can check this with the following command: [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS What do we recommend? A running system is not directly at risk. For Dedicated Servers, the risk only exists during a reboot. For Cloud VMs, the risk only exists when booting into the Rescue System. If possible, avoid these boot processes until a solution is available. As an additional security measure, you can temporarily block incoming ICMP packets using the Hetzner Firewall during reboots: Dedicated Servers (https://docs.hetzner.com/robot/dedicated-server/firewall/): Please make sure to enable “Allow Hetzner Services” when creating the firewall rules. Cloud Servers: https://docs.hetzner.com/cloud/firewalls/getting-started/creating-a-firewall/ What happens next? We are working on further recommendations and additional security measures. We will inform you as soon as we have new information or updates.

    Show more

No impact · Investigating

Limited availability of cloud instances

Started 4 months ago, UTC. Affects Cloud Server.

Follow it on status.hetzner.com

  1. Update

    Due to the continuing high demand and the limited availability of required hardware components, the provisioning of cloud servers at our locations is currently only possible to a limited extent. Given this situation, we are currently required to restrict the creation of new cloud servers for both new customers and some of our existing customers. The selection of affected existing customers is made at random. Unfortunately, it is not possible to individually influence or prioritize specific requests. We are continuously monitoring the situation and working intensively to expand capacity. More details can be found in this article: https://docs.hetzner.com/cloud/general/faq#why-can-cloud-instances-occasionally-not-be-ordered Thank you very much for your understanding.

    Show more

No impact · Investigating

Phishing emails stealing logins and credit card data

Started 2 years ago, UTC.

Follow it on status.hetzner.com

  1. Update

    Phishing is a serious digital security threat, which causes billions of dollars in damages every year. It’s a risk that both everyday users and companies should not underestimate. There are currently phishing emails circulating in the name of Hetzner. You can recognise these emails by the following features: Sense of urgency: Be careful about any emails with subject lines that ask you to do something urgently, for example, subject likes, “Last reminder: accept the new data protection policies”, “Urgent: renew your domain xyz or it will be locked”, or “Your contract will end soon”. Fake sender: Look out for emails with fake sender names like “HETZNER”, “HetznerSupportTeam”, “Hetzner Online GmbH”. The sender is also fake if the email address does not end with “@hetzner.com”. Links that look real: In the email texts, there are links that look real at first, but that will take you to fake Hetzner login pages. These fake login pages will try to get you to enter your Hetzner login details or your credit card details so they can steal them. If you think an email is fake, do NOT open the email at all. And if you accidentally do open the email, do NOT click on any links. If you get an email like this, delete it immediately. If you already entered your username and/or password on site that you think was fake, you should immediately change your Hetzner password at https://accounts.hetzner.com. To better protect your account against hackers, we strongly recommend that you activate two-factor authentication (2FA) for your Hetzner Account: https://docs.hetzner.com/accounts-panel/accounts/two-factor-authentication/ Please do not call our telephone support about phishing-related issues. Instead, write to us at support@hetzner.com. You can see a collection of phishing emails that we know about here: https://docs.hetzner.com/general/others/phishing-email-collection

    Show more

Maintenance

In progress and scheduled, as announced by Hetzner.

Maintenance · In progress

Migration of Image Archive Compression Format to zstd

Started 5 months ago, UTC. Affects system images.

Follow it on status.hetzner.com

  1. Update

    As part of our ongoing optimization efforts, we are migrating the compression format of our image archives from tar.gz to tar.zst (zstd) to significantly reduce installation times. The file extension of the archives has changed accordingly. If you are operating an automated installation environment and reusing existing installimage configurations, we kindly ask you to review the respective IMAGE parameter and update the file extension to reflect the new tar.zst format.

Maintenance · Scheduled

Maintenance work on billing functions and consumption data

Starts in 3 days, UTC.

Follow it on status.hetzner.com

  1. Update

    During this time, we will be doing routine maintenance work which is why the following functions are temporarily not available: - Accounts - view/edit contact details - view/pay invoices - view transactions - view/edit payment details - Activate Vouchers - Robot - server transfer - storagebox transfer - Detailed invoice view (https://usage.hetzner.com)

    Show more

Maintenance · Scheduled

Maintenance UPS systems in HEL1-DC10

Starts in 4 days, UTC. Affects HEL1-DC10.

Follow it on status.hetzner.com

  1. Update

    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.

Maintenance · Scheduled

Maintenance UPS systems in HEL1-DC12

Starts in 4 days, UTC. Affects HEL1-DC12.

Follow it on status.hetzner.com

  1. Update

    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.

Maintenance · Scheduled

UPS function tests in HEL1-DC10

Starts in 5 days, UTC. Affects HEL1-DC10.

Follow it on status.hetzner.com

  1. 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.

Maintenance · Scheduled

UPS function tests in HEL1-DC12

Starts in 5 days, UTC. Affects HEL1-DC12.

Follow it on status.hetzner.com

  1. 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.

Maintenance · Scheduled

Replacement of power supply components and UPS in NBG1-DC2

Starts in 1 week, UTC. Affects NBG1-DC2.

Follow it on status.hetzner.com

  1. Update

    During this time, technicians will be upgrading various power supply components, including the UPS system in NBG1-DC2 . The work should not negatively affect our server systems. You can see which data center your server is located in by doing a trace route (for example, by using https://dnstools.ws/).

Incident history

Every incident Hetzner published since Jul 5, 2024.

  • No outage reported
  • Partial outage

Last 90 days, today on the right

Nothing to list yet, no resolved incident so far.

About this page

An uptime monitoring service that refuses to monitor Hetzner. There is a good reason, promise.

Phare is not affiliated with Hetzner, names and trademarks belong to their owners.

More cloud providers

European providers on the lookout, all read from their official status pages.

See all providers

Frequently asked questions

You could not find the answer to your question? Ask support.

  • Is Hetzner down right now?

    Hetzner reports a partial outage right now. This page reads the official status page of Hetzner every 10 minutes.

  • Hetzner isn’t working for me, but no incident is reported. Why?

    Status pages are updated by people, often a while after an outage starts, and some problems only hit one region, network or account. If Hetzner still reports nothing, the problem may be closer to home: check your own setup, then contact Hetzner support.

  • How often does Hetzner have incidents?

    Hetzner reported 3 incidents in the last 90 days, the last one on Nov 12, 2026. The history above goes back to Jul 5, 2024, when Phare started recording it.

  • How does Phare know the status of Hetzner?

    Phare reads what Hetzner publishes on its status page, incidents and maintenances included, and keeps their history. It never probes Hetzner itself, so the status is indicative: an outage shows up once Hetzner announces it.

  • How do I know if my own website is down?

    Monitor it: Phare checks your websites and APIs from multiple regions, alerts you on Slack, Discord or email, and hosts your status page, with a free plan to get started.

Phare would have checked your website once by now.

How many times have you checked it in the last 0 seconds?

Start monitoring for free