Network Status
The board is clear right now
A hand-kept read on the platform. Anything we know to be broken is posted here, and a fault you meet that is missing gets listed the moment you report it.
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 moving 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
Built to keep going
The platform sits 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.
- Standby power and cooling on hand
- Several upstream network routes
- NVMe storage with copies behind it
- Platform-level faults flagged to us automatically
How It Works
A status board that stays honest
Two roads a fault travels
Hardware and network faults are flagged automatically by the platform beneath; customers bring us the rest. Whichever arrives first, a person updates this board.
Redundancy already wired in
With power feeds, network routes and storage all duplicated, a single failed component rarely needs to reach you.
The board tells the truth
This board shows what we know at this moment. A rough hour does not get buried to keep a row green, and a row that looks stale is worth telling us about.
Monitored
What we watch
The parts of the platform this board covers. A fault in any of them belongs on this board, so flag whatever you meet that is not here.
- Servers and nodes answering
- Mail moving out, and the queue depth
- Control panel and sign-in availability
- The power feeds and network circuits inside the facility
- DNS resolution and propagation
- SSL certificates issuing on time
- The nightly copy 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 reissue. Either way, support will help you track it down and put it right, and keep you posted while they do.
- Tickets and email, around the clock
- People, never canned replies
- Straight updates while we work
- Help isolating account-level faults
Hit A Snag?
Three quick moves 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 settle yourself.
- 3
Message support
Still stuck? Raise a ticket setting out exactly what you can see, and the team digs in and keeps you informed.
Peace Of Mind
Reliability is built in, not bolted on
99.9% uptime, the target
Every plan we run is built and watched against a 99.9% uptime target.
Guarded and copied
Free SSL, network-level filtering and regular copies keep your data safe and close to hand.
Support that picks up
Real help at every hour means somebody is there the second you need to ask.
FAQ
How this board works
What does an all-green board actually mean?
That nothing is flagged against any core piece — web hosting, VPS, mail, 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' rather than a live measurement. The moment a service drops and we know of it, its row says so.
How current is what I am looking at?
A person updates it, not a monitor. As soon as a fault reaches us, whether from the platform below or from a customer, the affected row changes. That means the board can trail a fault by however long it takes somebody 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, a lapsed certificate, a plugin conflict, or a resource limit you have hit. Start in your control panel, and if nothing there explains it, write to 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 falls short through a fault on our side — ask and we apply it. Calling it a contractual SLA is something we deliberately avoid. For an independent record, point a free external monitor at your own name; then you have a measurement rather than our word.
I have hit a fault the board does not show. How do I flag it?
Send support your name, 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 anybody, you are telling us something we may not yet know.
Seen something we have not?
If things look wrong from your side while this board still reads green, tell us — the team will get on it.
Message Support