Network Status
The board is clear right now
A hand-kept read on the platform. When we know something is broken it goes up here — and if you hit a fault that is missing, reporting it is what gets it listed.
No incidents recorded
No core service currently carries a flag. Because this board is kept by a person rather than a monitor, a fault you can see and we cannot is exactly the kind worth reporting.
- Running
Web Hosting
Nodes carrying shared, WordPress and business plans
- Running
VPS
KVM instances and the provisioning API
- Running
Email
Mail flowing in and out of your inboxes
- Running
Control Panel
cPanel, the client area and the billing screens
- Running
Network
Core routing, DNS and datacentre uplinks
This board is updated by hand. Spotted a fault that isn't shown above? Tell our support team and we'll get straight onto it.
5
Core services tracked here
By hand
How this board gets updated
99.9%
The uptime we aim at
Any hour
When a fault can be reported
Behind the Board
Engineered to keep moving
The platform lives in hardened datacentres with standby power, cooling and network paths, so a single failure rarely gets anywhere near your site. Faults at that layer are flagged to us automatically by the platform beneath, and we post them on this board.
- Backup power and cooling on standby
- Multiple upstream network routes
- NVMe storage with backups behind it
- Platform-level faults flagged to us automatically
How It Works
A status board that stays honest
Two roads a fault travels
The platform beneath us flags hardware and network faults automatically, and customers report the rest. Whichever arrives first, a person updates this board.
Redundancy already wired in
Duplicated power feeds, network routes and storage mean one component failing rarely has to reach you at all.
The board tells the truth
What you read here is what we currently know. We will not bury a rough hour to keep a row green — and if a row looks stale, say so and we will correct it.
Monitored
What we watch
The parts of the platform this board covers. A fault in any of them belongs on it, so flag anything you hit that is missing.
- Servers and nodes responding
- Mail moving out and queue depth
- Control panel and sign-in availability
- Power feeds and network circuits in the datacentre
- DNS resolution and propagation
- SSL certificates issuing on time
- Nightly backup jobs completing
- The API that provisions and deploys accounts
Spotted a Problem?
Real engineers, ready to move
Not every problem is a platform outage — often it's a DNS record still catching up or a certificate due for renewal. Either way, support will help you track it down and put it right, and keep you in the loop while they do.
- Tickets and email, around the clock
- Humans, never canned replies
- Straight updates while we work
- Help isolating account-level faults
Hit A Snag?
Three quick steps to a fix
- 1
Scan this board
Every core service appears with its current state. A fault on our side lands here first.
- 2
Check your control panel
Sign in and rule out a one-off on a single site, mailbox or DNS record you can fix yourself.
- 3
Message support
Still blocked? Open a ticket describing exactly what you see, and the team will dig in and keep you updated.
Peace Of Mind
Reliability is built in, not bolted on
99.9% uptime, the target
Every plan we run is engineered and watched against a 99.9% uptime target.
Protected and backed up
Free SSL, network-level filtering and regular backups keep your data safe and close at hand.
Support that picks up
Human help at every hour means someone is there the second you need to ask.
FAQ
How this board works
What does an all-green board really mean?
That nothing is flagged against any core piece — web hosting, VPS, email, the control panel and the network. It records what we currently know, updated by a person rather than generated by a probe, so read it as 'nothing reported' instead of a live measurement. When a service drops and we know it, its row here says so.
How current is what I'm looking at?
A person updates it, not a monitor. The moment a fault reaches us — from the platform underneath, or from a customer — the affected row changes. That means the board can trail a fault by however long it takes someone to report it, which is exactly why reporting one speeds things up for everybody.
The board reads green but my site is down. Now what?
That usually points to something local to your account rather than a platform outage — a DNS change still propagating, an expired certificate, a plugin conflict, or a resource limit you have hit. Start in your control panel, and if nothing there explains it, message support and we will run it down with you.
Is uptime guaranteed?
We aim at 99.9%, and our terms give you a pro-rated credit for any month that lands short because of a fault on our side — ask and we apply it. We deliberately stop short of calling that a contractual SLA. For an independent record, point a free external monitor at your own domain; then you have a measurement rather than our word.
I've hit a fault the board doesn't show. How do I flag it?
Send support your domain, the affected service and what you are seeing. Since this board runs on human updates, customer reports are one of the two roads a fault travels to reach it — you are not bothering anyone, you are telling us something we may not yet know.
Spotted something we haven't?
If things look wrong from your side while this board still reads green, tell us — the team will jump on it.
Message Support