Network status
Current state of the platform and of each datacenter region, plus what to send us if something looks wrong on your server specifically.
17 August 2026, 09:00 UTC
- Fastest report: WhatsApp
- Planned work: client-area announcements
Platform
- Client area & billing Operational
- Website Operational
- Automated VPS deployment Operational
- Support channels Operational
Network
- North America — United States, Canada Operational
- Western Europe — United Kingdom, Germany, France Operational
- Northern Europe — Sweden, Finland Operational
- Asia — Turkey, India, Malaysia, Iran Operational
Recent Incidents
No incidents reported.
Planned maintenance windows are announced in the client-area Announcements section before they happen, and posted here while they are in progress.
If Your Server Looks Down
Most reports turn out to be reachable from somewhere else, which narrows the problem in seconds. Three checks first, then tell us what you found.
-
1
Check the banner above
If a region is already marked degraded or down, we know and are working on it. Nothing to report — though you are welcome to ask for an estimate.
-
2
Test from outside your own network
Ping or trace the IP from a different connection, or use any public looking-glass service. Local ISP routing and your own firewall cause a surprising share of reports.
-
3
Check the server itself, not just the service
If SSH or RDP answers but your application does not, the machine is up and the problem is above our layer — still tell us, but that changes where to look.
-
4
Send it to us
WhatsApp for speed, email for detail. Include what you found in steps 2 and 3 — it removes an entire round trip.
Include your order ID or the server IP
Without one of the two, the first reply we send is a question rather than an answer.
Say when it started
“About twenty minutes ago” is enough. It tells us which window to look at.
Paste the exact error
A timeout, a refused connection and a DNS failure are three different problems that look identical when described as “it does not work”.
Mention anything you changed
A firewall rule added an hour ago is the most common cause of a server that “suddenly” stopped answering.