Is Hetzner Down? Live status & outage reports

Service info and troubleshooting

Server instance won't start after reboot

Your virtual server might fail to boot due to filesystem errors or corrupted boot configuration. Connect through the rescue console available in your Cloud panel. Mount your disk and run fsck to check filesystem integrity. If you recently modified GRUB settings, restore the backup configuration from /boot/grub/grub.cfg.bak. For cloud instances, check if your startup script isn't blocking the boot process.

SSH connection times out constantly

• Verify your firewall rules aren't blocking port 22 in the Cloud Firewall settings
• Check if fail2ban accidentally banned your IP address by reviewing /var/log/fail2ban.log
• Test connectivity from another network to isolate routing issues
• Ensure sshd service is running with systemctl status sshd
• Review your DNS records if connecting via hostname instead of IP

Storage Box access suddenly stopped working

Authentication failures with Storage Box usually stem from password changes or SSH key mismatches. Regenerate your credentials through Robot panel under Storage section. For SFTP connections, double-check you're using the correct username format: your-username-u123456. Some FTP clients cache old credentials, so clear saved sessions and reconnect. Protocol restrictions might also apply, ensure you're using SFTP, not plain FTP.

Network performance drops unexpectedly

High latency often points to network interface misconfiguration or CPU throttling. Run ethtool to verify your NIC settings match the expected speeds. Check for packet loss with mtr commands to identify if the issue occurs within the datacenter or upstream. Monitor your bandwidth graphs in the panel, you might be hitting rate limits. Disable any traffic shaping tools temporarily to rule them out.

Console access shows blank screen

The web console might display nothing if your instance uses a serial console configuration that doesn't output to the VNC display. Modify your bootloader to enable console output on ttyS0 and tty0 simultaneously. Add console=tty0 console=ttyS0,115200n8 to your kernel parameters. After applying changes, reboot and the console should respond properly.