Is Hetzner down?

Last checked 2m ago
Current status
Hetzner is having a partial outage

11 active incidents: Wartungsarbeiten an der Backbone-Verbindung zwischen Falken…, Wartungsarbeiten am Object Storage in FSN1 · +9 more

Get alerts when Hetzner breaks →

Free · no credit card

Official status page: https://status.hetzner.com · Polled every 5 minutes · 0 components tracked

Real-time Hetzner status, recent outages, and incident history — pulled directly from Hetzner's official status page at https://status.hetzner.com every 5 minutes. Pingoru tracks 0 Hetzner services and has captured 39 incidents in the last 90 days (81.11% uptime). Get email, Slack, Discord, or webhook alerts the moment Hetzner reports a new incident — free for 5 monitors, no credit card.

Users who monitor Hetzner also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel HashiCorp Egnyte Dyn Genesys Cloud Linode View all 6,000+ providers
Hetzner uptime 81.11% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Wartungsarbeiten an der Backbone-Verbindung zwischen Falkenstein - Frankfurt
    Ongoing ● 34m
    Started Apr 29, 2026, 06:02 PM UTC
    1 update · show timeline
    • monitoring · Apr 29, 2026, 06:02 PM UTC

      <p>Start: 2026-05-07T00:00:00+00:00</p> <p>Ende: 2026-05-07T04:00:00+00:00</p> <p>Im oben genannten Zeitraum werden Wartungsarbeiten an der Backboneverbindung zwischen Falkenstein - Frankfurt durchgeführt. Dadurch kann es zu erhöhten Latenzen kommen. Bitte entschuldigen Sie die Unannehmlichkeiten. Vielen Dank für Ihr Verständnis.</p>

    Latest: <p>Start: 2026-05-07T00:00:00+00:00</p> <p>Ende: 2026-05-07T04:00:00+00:00</p> <p>Im oben genannten Zeitraum werden Wartungsarbeiten an der Backboneverbindung zwischen Falkenstein …

  2. Load Balancer: Erstellung und Aktualisierungen vorübergehend nicht verfügbar
    Resolved 4h 32m
    Started Apr 29, 2026, 11:27 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC
    1 update · show timeline
    • monitoring · Apr 29, 2026, 11:27 AM UTC

      <p>Start: 2026-04-29T11:26:02+00:00</p> <p>Wir haben derzeit Probleme bei der Erstellung und Aktualisierung von Load Balancern. Unser Team untersucht das Problem aktiv. Wir entschuldigen uns für die Unannehmlichkeiten und werden so schnell wie möglich weitere Informationen bereitstellen.</p>

    Latest: <p>Start: 2026-04-29T11:26:02+00:00</p> <p>Wir haben derzeit Probleme bei der Erstellung und Aktualisierung von Load Balancern. Unser Team untersucht das Problem aktiv. Wir entschu…

  3. Load Balancer: Erstellung und Aktualisierung privater Netzwerke in FSN1 gestört
    Resolved 8h 19m
    Started Apr 29, 2026, 07:39 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC
    1 update · show timeline
    • monitoring · Apr 29, 2026, 07:39 AM UTC

      <p>Start: 2026-04-29T06:30:00+00:00</p> <p>Die Erstellung und Aktualisierung privater Netzwerke für Load Balancer ist im Rechenzentrum FSN derzeit gestört. Es kann zu vorübergehenden Einschränkungen beim Anlegen oder Ändern privater Netzwerke kommen.</p> <strong>Monitoring</strong> <small>2026-04-29T07:39:54+00:00</small> <p>Das Problem wurd behoben und wir beobachten die Situation.</p>

    Latest: <p>Start: 2026-04-29T06:30:00+00:00</p> <p>Die Erstellung und Aktualisierung privater Netzwerke für Load Balancer ist im Rechenzentrum FSN derzeit gestört. Es kann zu vorübergehend…

  4. Load Balancer: Erstellung und Aktualisierung privater Netzwerke in FSN1 gestört
    Resolved 8h 29m
    Started Apr 29, 2026, 07:30 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC
    1 update · show timeline
    • monitoring · Apr 29, 2026, 07:30 AM UTC

      <p>Start: 2026-04-29T06:30:00+00:00</p> <p>Die Erstellung und Aktualisierung privater Netzwerke für Load Balancer ist im Rechenzentrum FSN derzeit gestört. Es kann zu vorübergehenden Einschränkungen beim Anlegen oder Ändern privater Netzwerke kommen.</p>

    Latest: <p>Start: 2026-04-29T06:30:00+00:00</p> <p>Die Erstellung und Aktualisierung privater Netzwerke für Load Balancer ist im Rechenzentrum FSN derzeit gestört. Es kann zu vorübergehend…

  5. Wartungsarbeiten am Object Storage in FSN1
    Ongoing ● 1d 4h
    Started Apr 28, 2026, 02:31 PM UTC
    1 update · show timeline
    • monitoring · Apr 28, 2026, 02:31 PM UTC

      <p>Start: 2026-05-04T10:00:00+00:00</p> <p>Ende: 2026-05-04T14:00:00+00:00</p> <p>Wir führen planmäßige Wartungsarbeiten an unserem FSN1 Object Storage durch. Während dieser Zeit kann es zu kurzzeitigen Verbindungsabbrüchen kommen.</p>

    Latest: <p>Start: 2026-05-04T10:00:00+00:00</p> <p>Ende: 2026-05-04T14:00:00+00:00</p> <p>Wir führen planmäßige Wartungsarbeiten an unserem FSN1 Object Storage durch. Während dieser Zeit k…

See the full Hetzner outage history

34 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 35 incidents
  • Wartungsarbeiten an der Backbone-Verbindung zwischen Falkenstein - Frankfurt Ongoing
    Started Apr 29, 2026, 06:02 PM UTC · ● 34m
  • Load Balancer: Erstellung und Aktualisierungen vorübergehend nicht verfügbar Resolved
    Started Apr 29, 2026, 11:27 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC · 4h 32m
  • Load Balancer: Erstellung und Aktualisierung privater Netzwerke in FSN1 gestört Resolved
    Started Apr 29, 2026, 07:39 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC · 8h 19m
  • Load Balancer: Erstellung und Aktualisierung privater Netzwerke in FSN1 gestört Resolved
    Started Apr 29, 2026, 07:30 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC · 8h 29m
  • Wartungsarbeiten am Object Storage in FSN1 Ongoing
    Started Apr 28, 2026, 02:31 PM UTC · ● 1d 4h
  • Wartungsarbeiten Netzersatzanlage in FSN1-DC1 Ongoing
    Started Apr 28, 2026, 08:56 AM UTC · ● 1d 9h
  • Funktionstests USV und NEA in FSN1-DC11 Resolved
    Started Apr 28, 2026, 05:25 AM UTC · Resolved Apr 28, 2026, 09:56 AM UTC · 4h 30m
  • Funktionstests USV-Anlagen in FSN1-DC11 Resolved
    Started Apr 28, 2026, 05:24 AM UTC · Resolved Apr 29, 2026, 03:59 PM UTC · 1d 10h

See Hetzner in your Pingoru dashboard

Monitor Hetzner alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Hetzner to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Hetzner incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Hetzner or see every provider at once.

Maintenance calendar

Scheduled Hetzner maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Hetzner status change, one inbox

Pingoru watches Hetzner's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Subscribe to the specific Hetzner services you rely on. Everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Hetzner alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Hetzner maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Hetzner services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Hetzner from the same account, with per-user notification preferences for any monitor.

Get notified on Hetzner status changes

Pingoru watches Hetzner's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Hetzner free

Monitor Hetzner along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Hetzner and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Hetzner uptime & incident history

See 90 days of Hetzner uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Hetzner uptime history

Frequently asked questions

What is Hetzner's uptime?
Over the last 90 days, Hetzner reported 81.11% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.hetzner.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Hetzner's uptime history rolling forward in real time.
Has Hetzner had outages in 2026?
Yes — Hetzner has had 28 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Hetzner outage?
The most recent Hetzner incident was "Load Balancer: Erstellung und Aktualisierungen vorübergehend nicht verfügbar", which started on April 29, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.hetzner.com. See the full incident card above for affected components and the update timeline.
How often does Hetzner have outages?
Based on the last 90 days, Hetzner averages 9.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Hetzner's status page?
Hetzner's official status page is https://status.hetzner.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Hetzner down right now?
Hetzner is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Hetzner reports a change. Current status is based on 0 tracked services.
How does Pingoru know if Hetzner is down?
We read https://status.hetzner.com directly, using Hetzner's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Hetzner has an outage?
Create a free Pingoru account and add Hetzner as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Hetzner's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Hetzner incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Hetzner issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Hetzner status?
We use Hetzner's own status page at https://status.hetzner.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
Hetzner has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch Hetzner's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Hetzner free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →