Question 1

How does this check work?

Accepted Answer

Our server requests your address the way a browser would, follows any redirects, and reports what happened: the status code and how long the response took. If we reach it and you can't, the problem is on your side of the internet; if we can't reach it either, it is genuinely down.

Question 2

It's up for you but down for me. What do I do?

Accepted Answer

In order: try mobile data instead of Wi-Fi (isolates your network), try a private/incognito window (isolates cache and extensions), restart your router, and flush your DNS. If it fails only at your office, ask whoever manages that network.

Question 3

It's down for everyone. Now what?

Accepted Answer

Check your hosting provider's status page first — most outages are theirs and resolve without you. If hosting is fine, the usual suspects are an expired domain, broken DNS records after a change, or an expired SSL certificate. Your registrar and hosting dashboards will show which.

Question 4

How do I stop discovering outages from customers?

Accepted Answer

Uptime monitoring — a service that checks your site every minute and emails you the moment it fails. Sites this studio maintains get monitoring as standard; finding out from a customer is the expensive way.

Question 5

The site is 'up' but a specific page errors. Does this catch that?

Accepted Answer

Check that exact page's URL here — the tool tests whatever address you give it, and a 404 or 500 on the page will show as the status code.

Down for everyone — or just you?

Fair questions.

Have a project in mind?