Skip to content
DownSpotter

Diagnosis

Is it down, or is it just me?

How to tell a global outage from a problem on your Wi-Fi, DNS, VPN, or browser.

Start with a second vantage point

If a website fails on your phone, laptop, or office network, the failure might be local: a DNS resolver, a captive portal, a VPN, an extension, or an ISP issue. It might also be a real outage. You need an independent check that does not use your network.

DownSpotter probes the site from our monitoring infrastructure and reports what we can reach — not a claim that the whole internet agrees. If we can load the site and you cannot, the problem is likely on your side. If several of our checks fail, an outage is more likely.

What “down for everyone” actually means

No single monitor sees every network. CDNs serve different cities. A site can be down for one ISP and fine for another. Treat any one checker — including this one — as evidence, not a verdict.

Look at consecutive failures over a few minutes, HTTP status codes, DNS errors, and (when we have them) user reports. One timeout is a blip. Several independent failures are an incident.

If it is just you

Work through non-destructive steps: try another site, another browser or private window, disable the VPN briefly, switch between Wi-Fi and cellular, and retry DNS. Restarting the router is reasonable if several sites fail. Avoid random “fix” downloads and registry tweaks.

  1. Confirm another well-known site loads.
  2. Retry in a private window without extensions.
  3. Disconnect from VPN or proxy and try again.
  4. Switch networks (Wi-Fi to cellular, or the reverse).
  5. If many sites fail, restart the router and check DNS settings.

Related: How to check if a website is down · How to fix DNS problems · What does HTTP 503 mean?