Network Status
Nothing at all is flagged 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
Not one core service carries a flag at the moment. Since a person keeps this board rather than a monitor, a fault visible to you but invisible to us is precisely the kind worth reporting.
- Running
Web Hosting
The nodes that carry shared, WordPress and business plans
- Running
VPS
KVM instances, plus the provisioning API behind them
- Running
Email
Mail moving into and back out of your inboxes
- Running
Control Panel
cPanel, along with the client area and billing screens
- Running
Network
Core routing, DNS, and the datacentre uplinks
This board is maintained by hand. Spotted something broken that is not listed above? Tell our support team and somebody will get onto it straight away.
5
Core services tracked here
By hand
How this board gets updated
99.9%
The uptime we aim at
Any hour
The hours you can report a fault
Behind the Board
Engineered to keep moving
Our platform sits inside hardened datacentres with standby power, cooling and network paths, so a lone failure rarely gets anywhere near your site. At that layer the platform beneath flags faults to us without being asked, 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 tells the truth
Two roads a fault travels
Hardware and network faults get flagged by the platform beneath us on their own, while customers report everything else. Whichever comes in first, a person updates this board.
Redundancy already wired in
Power feeds, network routes and storage all run duplicated, so a single component failing rarely reaches you at all.
The board tells the truth
What sits on this page is what we currently know. A rough hour will not get buried to keep a row green. Should a row look stale to you, say so and we will put it right.
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 inside the datacentre itself
- 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 turns out to be a platform outage. Plenty of the time it is a DNS record still catching up, or a certificate that has come due for renewal. Whichever it is, support will help you track it down and fix it, keeping you posted along the way.
- Tickets and email, around the clock
- Humans, never canned replies
- Straight updates while we work
- Help isolating account-level faults
Hit A Snag?
A fix in three quick steps
- 1
Scan this board
Each core service is shown with the state it is in. A fault at our end arrives here first.
- 2
Check your control panel
Before anything else, check the account itself. One misbehaving site, one mailbox, one DNS entry: those you can often put right without us.
- 3
Message support
Still stuck? Raise a ticket setting out precisely what you are seeing, and the team will dig into it and keep you posted.
Peace Of Mind
Reliability built in, and never bolted on
99.9% uptime, the target
We build and watch every plan against a 99.9% uptime target, without exception.
Protected and backed up
Free SSL, filtering at the network level and regular backups keep your data safe and within reach.
Support that picks up
Real people answer at any hour, so somebody is there the second you need to ask.
FAQ
How this board works
What does an all-green board really mean?
Nothing carries a flag against it. Not web hosting, not VPS, not email, not the control panel, not the network. Bear in mind how the page is built: a person types what we currently know into it, rather than a probe generating a live reading, so treat green as an absence of reports. Once a service goes down and word reaches us, its row changes.
How current is what I'm looking at?
A person updates it, not a monitor. As soon as a fault reaches us, whether from the platform underneath or from a customer, the affected row changes. So the board can lag a fault by however long it takes somebody to report it, which is exactly why reporting one hurries things along for everyone.
Everything here reads green, yet my site is down. What now?
More often than not, the cause is sitting inside your own account rather than out on the platform. Propagation that has not finished. A certificate past its date. Two plugins arguing with each other. A resource ceiling you walked into. Look through the control panel first, and when nothing there adds up, message support and we will hunt it down with you.
Is uptime guaranteed?
Our aim is 99.9%, and the terms hand you a pro-rated credit for any month falling short through a fault at our end. Ask, and we apply it. Calling that a contractual SLA is something we deliberately avoid. Want an independent record? Point a free external monitor at your own domain, and then you hold a measurement rather than our word for it.
There is a fault here that the board never shows. How do I report it?
Send support your domain, the service affected and a description of what you see. Because this board runs on human updates, a customer report is one of the two roads by which a fault reaches it. You are not bothering anybody. You are telling us something we may not know yet.
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