Cloud & Infrastructurehetzner.com

Is Hetzner Online Down Right Now?

Live global uptime status, multi-region edge latency, official incident reports, and automated monitoring for Hetzner Online.

H

Hetzner Online

hetzner.com

High-performance European cloud servers, dedicated hardware, and storage boxes.

Degraded Performance
Edge Latency
1285 ms

Primary edge roundtrip

24h Global Uptime
98.40%

Edge consensus

Vantage Points
7 Regions

NA, EU, APAC Edge DOs

Last Checked
5:24:50 AM

Edge consensus mesh

Telemetry verified by SteadyStack Autonomous Edge Network
Official Status
Automated Developer Alerting

Stop checking manually.

When Hetzner Online goes down or suffers silent latency degradation, you shouldn't be refreshing status pages, searching social feeds, or waiting for angry user reports. Get alerted the exact second Hetzner Online fails.

Monitor Hetzner Online in 1 Click

Free 50 monitors • 3m standard (1m for first 10) • 2-of-3 Edge Quorum • No credit card required

10-Second Edge Intervals

Continuous HTTP, WebSocket & DNS checks from 15+ global edge nodes.

4-of-7 Quorum Verification

Multi-region consensus verification prevents 3 AM wakeups from transient routing blips.

Multi-Channel Escalation

Instant alerts to Slack, Discord, Telegram, SMS, PagerDuty & Webhooks.

steadystack.config.ts
Auto-provisioned Monitor
import { defineMonitor } from "@steadystack/core";

export default defineMonitor({
  name: "Hetzner Online API & Health",
  target: "https://hetzner.com",
  interval: "10s",
  consensus: { requiredRegions: 3 },
  alerts: ["slack-dev-ops", "pagerduty-p1", "discord-incidents"],
});

Global Edge Reachability & Regional Latency

Synthetic probe response times tested from SteadyStack worldwide vantage points.

🇺🇸
US-East (N. Virginia)
us-east
533 ms
UP
🇺🇸
US-West (Oregon)
us-west
552 ms
UP
🇩🇪
EU-Central (Frankfurt)
eu-central
595 ms
UP
🇯🇵
AP-Tokyo (Tokyo)
ap-northeast
656 ms
UP
🇧🇷
SA-East (São Paulo)
sa-east
668 ms
UP
🇿🇦
AF-South (Cape Town)
af-south
729 ms
UP

Downtime Impact Analysis

What happens when Hetzner Online degrades

Falkenstein/Nuremberg/Helsinki DC network loss, cloud server API unreachability.

Common HTTP Error Codes Observed

Connection Timed Out502 Bad GatewayNetwork Unreachable

Critical Monitored Subsystems

Components tracked on hetzner.com

Cloud Servers
Synthetic Active
Dedicated Root Servers
Synthetic Active
Storage Boxes
Synthetic Active
Load Balancers
Synthetic Active

Engineering Resilience Guide: Surviving Hetzner Online Outages

Defensive software architecture patterns to prevent third-party cascade failures.

Immediate Tactical Steps

  • 1Check status.hetzner.com.
  • 2Inspect Robot / Cloud Console vSwitch status.

Recommended Resiliency Patterns

Circuit Breaker Pattern: Automatically trip and fallback to cache when Hetzner Online error rates exceed 15% in a 30s rolling window.

Idempotent Background Retries: Push failed API events into an asynchronous dead-letter queue with exponential backoff and jitter.

Multi-Region Edge Synthetic Consensus: Rely on SteadyStack to alert your team before end-users notice degradation.

Frequently Asked Questions: Hetzner Online Availability & Monitoring

Everything you need to know about tracking Hetzner Online outages and SLA reliability.

Our real-time global edge probes continuously test Hetzner Online (hetzner.com) across multiple worldwide locations. You can check the live status badge and latency meter at the top of this page. If you are seeing errors while the global status is operational, it may be due to localized ISP routing, local DNS caching, or account-specific rate limiting.