My server is unreachable — diagnostic checklist

1. Is it a billing suspension?

Check the client area. Suspended services show a red banner. An overdue invoice suspends the instance 24 hours after the due date; paying it restores service immediately with data intact.

2. Is the instance running?

Services → your server shows power state and live CPU/RAM/disk graphs. If it is off, power it on. If it will not start, open a ticket — that is ours.

3. Can you reach the console?

The HTML5 VNC console bypasses the network entirely. If the console works but SSH/RDP does not, the problem is inside your OS — almost always a firewall rule, a changed port, or a service that failed to start. This is where most cases end.

# Linux, from the console
sudo ufw status numbered
sudo ss -tulpn | grep -E '22|2222'
sudo systemctl status ssh

# Windows, from the console
Get-NetFirewallRule -Enabled True -Direction Inbound | Where-Object DisplayName -like "*RDP*"
Get-Service TermService

4. Is it your own network?

ping your.server.ip
tracert your.server.ip      # Windows
mtr your.server.ip          # Linux/macOS

Try from a phone on mobile data. Corporate and hotel networks frequently block outbound 3389 and non-standard SSH ports.

5. Are you being null-routed?

Sustained inbound attack traffic can trigger a temporary null-route in extreme cases. The client area shows a notice if so, and it lifts automatically once the attack stops. DDoS Protection Pro prevents most of these.

6. Check the status page

status.rdpforge.com lists every current and past incident per location. If your region shows an incident, we are already on it and updates land there first.

Still stuck?

Open a ticket with: your server IP, what you tried from the list above, the output of tracert/mtr, and your own public IP. That set of information typically gets a fix on the first reply rather than the third.