Knowledge base

Checking whether the problem is at our end

How to tell a platform incident from a problem with your own site, before you spend an hour on the wrong one.

When something stops working the first useful question is whether it is your site or ours, because the two have completely different next steps.

Check the status page first

It is linked from the panel, and it lists anything currently affecting the platform. If what you are seeing is on there, it is ours, we already know, and it is being worked on — the page is updated as it progresses, so you can follow it there rather than opening a ticket to ask for an update.

We tell you if it affects you specifically

You do not have to go looking. If an open incident affects services you actually have, the panel says so, and the ticket form tells you before you finish writing. An incident affecting a region or a product you are not on is not shown to you as though it were your problem.

If the status page is clear

Then it is probably your site, and the place to start is the site's own diagnosis — it checks the things that are wrong most often, including whether your domain still points at us.

When to open a ticket anyway

Open one if the status page is clear and the checks find nothing, or if what you are seeing is worse or different from what an incident describes. A status page saying "degraded performance" does not cover your site being entirely down, and if those two disagree we want to know.

You never need to open a ticket to ask whether an incident is still open, or to be told when it is resolved. Follow it on the status page.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →