Theme

Popular tools

Is It Down for Everyone or Just Me?

Is this website down, or just for you? Check website status from 11 places and your own connection, and see a live screenshot of what it shows.

11 Cloudflare locations · a real Chrome browser in 4 regions · your own browser · official status pages
11 places live

A domain or a full URL, with a path or a port if you need one.

Try
Popular nowYouTubeDiscordChatGPTInstagramWhatsAppRobloxSteamX

We load the site from 11 places and take a screenshot. Nothing you type is stored with your IP.

Is it down for everyone or just me?

If our 11 places reach a site and your browser doesn't, it's just you. If nobody reaches it, it's down for everyone.

Every check asks the same question from two sides at once. Our 11 places open the site the way a browser does, and your own browser tries it over your connection. Comparing the two is the honest way to answer “is it just me?”: a down checker that asks from one server can't.

A site can also be down only in some places (a regional network fault or a country block), or answer people but turn away automated checks: we show those apart, never as “down”.

Up for everyoneUp

Every place and your browser reach it.

Just youJust you

We reach it; your browser can't. The fix is on your side.

Down for everyoneDown

Nobody reaches it, you included. Only the owner can fix it.

Partly downPartly down

Some places fail. It depends where you are.

The four answers, from 11 places and your browser. A fifth, “up but blocks bots”, is when only automated checks are turned away.
Website down checker result: up for everyone and for you, a live screenshot, the check path and 11 places on a mapWebsite down checker result: up for everyone and for you, a live screenshot, the check path and 11 places on a mapOne verdictEveryone (our 11 places) and you (your own browser) in one sentence, with the status code most places got.The live screenshotWhat a real Chrome browser saw a few seconds ago, with where and when it was taken. Take another from any region, or as a phone.Where it breaksThe check path from you to the rendered page: DNS, connect, TLS and the server's answer, each with its time.From 11 placesEvery place on the map, green when it got the page, amber when it was slow or blocked, red when it failed.
A check of our own homepage: the verdict, the live screenshot taken in Europe, the check path and the 11 places. Select a number to see what each part shows.

How to check if a website is down

Each place runs the steps a browser runs, and times each one. Then a real browser loads the page and takes the screenshot.

DNS turns the name into an address. Connect opens a TCP connection to it. TLS checks the certificate the way browsers do, so expired, misnamed and untrusted certificates each get their own answer. Then we send the request, wait for the first byte and follow up to 5 redirects, checking each one.

Last, Chrome (Cloudflare's Browser Run) loads the page in the region nearest you and takes the screenshot. The verdict never waits for it: it comes from the 11 places and your own browser, usually within a few seconds.

One check of shop.example from Amsterdam
  1. DNS11 ms

    Name → address, from Google and Cloudflare.

    NXDOMAINSERVFAIL
  2. Connect7 ms

    TCP to the address, from each place.

    refusedtimed out
  3. TLS9 ms

    The certificate, checked like a browser does.

    expiredwrong name
  4. First byte128 ms

    The request, and the server's wait.

    5xx52xslow
  5. Download14 ms

    The page and up to 5 redirects.

    resetloop
  6. Render2.3 s

    Chrome loads it and takes the screenshot.

    blankbot wall
The network steps take milliseconds; the browser takes seconds, which is why the verdict comes first and the screenshot follows.

What do 500, 502, 503, 504 and Cloudflare 52x errors mean?

A status code means the server answered; a browser error means nothing did. Where the chain breaks tells you who can fix it.

The small path on each row is you → the proxy or CDN in front of the site → the site's own server, with the break marked. The check path beside every result shows the same thing at full size.

Two Cloudflare details most pages get wrong: a Cloudflare-branded 502 or 504 page means the site's own server sent the error, while a blank, unbranded one came from Cloudflare; and 1xxx codes (1016, 1020, 1033) live in the page itself, while the status line carries 403, 409, 429 or 530.

The server answered, with an error · a status code
500 Internal Server ErrorThe site's own code failed on this page.Site
502 Bad GatewayA proxy or CDN got a broken answer from the server behind it.Site
503 Service UnavailableOverloaded, or down for maintenance on purpose. Retry-After may say when it's back.Site
504 Gateway TimeoutA proxy waited for the server behind it and gave up.Site
429 Too Many RequestsYou (or your network) sent too many requests: wait, then retry.You
Nothing answered · browser errors, no status code
ERR_NAME_NOT_RESOLVEDNo address for the name: a typo, an expired domain, or your DNS.Site or you
DNS_PROBE_FINISHED_NXDOMAINChrome checked your DNS works, so the domain itself doesn't exist (or is misspelled).Site or you
ERR_CONNECTION_REFUSEDThe address said no: nothing listens there, or a firewall refuses you.Site or you
ERR_CONNECTION_TIMED_OUTNothing answered at all: the server is down, or a network blocks it.Site or you
ERR_CONNECTION_RESETThe connection was cut: an unstable line, a VPN or security software.You
ERR_CERT_DATE_INVALIDThe certificate expired, or your computer's clock is wrong.Site or you
Cloudflare answered for the site · 52x and 530: Cloudflare is fine, the server behind it isn't
520 Unknown errorThe server sent Cloudflare an empty or unexpected answer.Site
521 Web server is downThe server refused Cloudflare's connection.Site
522 Connection timed outNo answer to Cloudflare's connection within 19 seconds.Site
523 Origin is unreachableCloudflare has no route to the server's address.Site
524 A timeout occurredConnected, but no page within 125 seconds.Site
525 SSL handshake failedThe TLS handshake between Cloudflare and the server failed.Site
526 Invalid SSL certificateCloudflare couldn't validate the server's certificate.Site
530 Origin errorCloudflare couldn't find the server: the page's 1xxx code says why.Site
you → proxy or CDN → the site's server, the break markedSiteonly the owner can fix itSite or youcheck your side firstYouon your side
Each meaning follows its definition: RFC 9110 and RFC 6585 for the status codes, Cloudflare's documentation for 52x and 530, Chromium's network error list for the browser errors.

Website not loading for you? Fixes that work

If our 11 places reach the site and you can't, the problem sits between you and the internet: your browser, your DNS, your network or your provider.

Work through the steps in order and check again after each one. The DNS steps fix most cases: your computer or router remembers an old address for as long as its TTL allows, and a “not found” answer for as long as the domain's negative-cache time.

If the site loads on mobile data but not on your Wi-Fi, your network or your provider is blocking it. On a work computer, a security proxy can break certificates for some sites; ask your IT team.

1
Reload without the cacheCtrl+F5 · ⌘+Shift+R
2
Flush your DNS cacheYour device may hold an old address.
3
Switch DNS1.1.1.1 or 8.8.8.8
4
VPN, proxy, ad blocker offSome block whole sites.
5
Try mobile dataWorks there? Your network blocks it.
6
Restart your routerIt drops the router's DNS cache too.
ipconfig /flushdns

In Command Prompt. Clears the DNS cache, including remembered “not found” answers.

Step 2 per system. Phones have no command: switching between Wi-Fi and mobile data tells you whether your network is the problem.

Why websites go down

Most website outages are one of six things, and each one leaves a different trace in the check.

When a big provider fails, thousands of unrelated sites go down at the same minute, and status pages lag behind. That's when an independent check is most useful: it tells you which layer broke, not only that something did.

Overload or a crash

Too many visitors, a bad release, a crashed app.

503 · 500 · 502
An expired domain

The owner forgot to renew; the registrar puts it on hold or parks it.

NXDOMAIN or parked · expiry date
An expired certificate

Browsers refuse the site until a new one is installed.

TLS: expired
A DNS mistake

A wrong record, broken DNSSEC, a botched nameserver move.

SERVFAIL · wrong address
A cloud or CDN outage

A provider thousands of sites share has a bad day.

52x · many sites at once
Blocked on the way

A firewall, a country block or a bot wall turns some people away.

partly down · 403

Big outages, from each provider's own report

  1. Cloudflare

    A firewall rule with a runaway regular expression used up CPU worldwide; visitors saw 502 errors.

    27 min
  2. Fastly

    A valid customer setting hit a latent bug: 85% of Fastly's network returned errors.

    95% back in 49 min
  3. Akamai

    A configuration update triggered a bug in a DNS component of its edge network.

    up to an hour
  4. Meta

    A maintenance command took down Meta's backbone; its DNS servers withdrew their routes, so Facebook, Instagram and WhatsApp vanished.

    length not published
  5. CrowdStrike

    A faulty security-sensor update crashed Windows PCs: Microsoft estimated about 8.5 million devices.

    bad file live 78 min
  6. Google Cloud

    A policy with blank fields crashed API management worldwide; customers got 503s.

    7 h 27 min
  7. AWS us-east-1

    A race in DynamoDB's DNS automation left an empty record and cascaded into EC2, Lambda and more.

    14 h 32 min
  8. Cloudflare

    A bot-management file that doubled in size crashed Cloudflare's proxy; many sites returned errors. Not an attack.

    5 h 46 min

Lengths from each provider's report: start to full recovery, except where noted.

Website screenshots: why a site looks different from another country

Sites change their language, prices, cookie banners and even what they show by country. So every screenshot says where it was taken.

Our screenshots come from Cloudflare's Browser Run, which runs Chrome in big locations near the Worker that calls it. We call it from four regions: North America, Europe, East and South-East Asia, and Oceania. We use the one nearest you, and you can take another from any region, or as a phone.

There's no browser pool in South America, Africa, India or the Middle East, so checks from there use the nearest region, and we name it. The city is read inside the page at capture time: we never label a screenshot with a place it wasn't taken in. A site that Cloudflare's security filters list as malware or phishing gets no screenshot at all; the link safety checker shows which services block a link and why.

1234North AmericaORD · DFW · MIA · IADEuropeAMS · CDG · VIEAsiaNRT · ICN · HKG · SINOceaniaAKLSouth AmericaAfricaIndiaMiddle East
  • Our homepage as an example screenshot for North America1North AmericaORD
  • Our homepage as an example screenshot for Europe · Deutsch2Europe · DeutschAMS
  • Our homepage as an example screenshot for Asia · 日本語3Asia · 日本語NRT
  • Our homepage as an example screenshot for Oceania4OceaniaAKL
Browser pool (cities seen in our tests)No pool: uses the region the arrow points to
Illustration with our own homepage: a site that adapts to its visitors looks different in each region. Pools as measured on 22 Oct 2026; Cloudflare can move them, so the city comes from inside the page.

Is my website down? Uptime in minutes

“99.9% uptime” sounds perfect, but it still allows almost 44 minutes of downtime every month.

Hosting and cloud contracts promise uptime as a percentage (an SLA). The figure turns each promise into the downtime it allows in an average month (365.25 ÷ 12 days) and in a year.

To catch outages on your own site as they happen, you need a website uptime checker: a check every minute from more than one place. A one-off check like this one answers “is it down right now?”, and the SSL Checker and WHOIS Lookup tell you when your certificate and your domain run out.

UptimeDowntime a month (log scale)A monthA year
99%7 h 18 min3 d 16 h
99.5%3 h 39 min1 d 20 h
99.9%43 min 50 s8 h 46 min
99.95%21 min 55 s4 h 23 min
99.99%4 min 23 s52 min 36 s
99.999%26 s5 min 16 s
Each extra nine divides the allowed downtime by ten; each half step halves it.

Website Down Checker FAQ

How do I check if a website is down right now?

Type the website's address above and press Check to check the website's status. Within a few seconds you see whether 11 places around the world can open it, whether your own browser can, and a live screenshot of the page. The answer names the cause in plain words: a server error, an expired domain or certificate, a DNS fault, or a site that only blocks automated checks.

Is it down for everyone or just me?

Compare the two lanes in the result: “Everyone” is our 11 places, “You” is your own browser. If we reach the site and your browser doesn't, it's just you, and the fixes appear right there. If nobody reaches it, it's down for everyone and only the site's owner can fix it.

Why is a website not loading for me when it works for others?

Usually your DNS cache, your DNS server, a VPN or ad blocker, or a block on your network or by your provider. Flushing your DNS cache and trying mobile data tells most of these apart. The fixes in the result list them in order, with the command for your system.

Why does the screenshot show a blank page or “Access denied”?

Some sites turn away automated browsers, and ours always says it is one: Cloudflare's Browser Run identifies itself to every site. If your own browser reaches the site, it is up, and we say “blocks bots”, never “down”. The places table shows the same answer, usually a 403.

Where is the website checked from?

From 11 places: the Cloudflare location nearest you, plus San Jose, Ashburn, London, Stockholm, Singapore, Sydney, São Paulo, Cape Town, Mumbai and Osaka. Each row names the data centre that answered. The screenshot comes from a real Chrome browser in North America, Europe, Asia or Oceania, and the caption names the city.

What do 502, 503 and 522 errors mean?

A 502 means a proxy or CDN got a broken answer from the server behind it. A 503 means the server is overloaded or down for maintenance, often on purpose. A 522 means the site is on Cloudflare and its own server didn't answer Cloudflare in time. All three are on the site's side: only its owner can fix them.

Why does the checker say the certificate expired?

Every HTTPS site needs a valid certificate, and one issued since 15 March 2026 lasts at most 200 days (older ones up to 398). When it runs out, browsers show a full-page warning instead of the site, so for most visitors it is down. We check the certificate ourselves and show when it expired and who issued it. If your computer's clock is wrong, you may see the same warning on sites that are fine.

Is the domain expired, or is the site just down?

When no DNS server knows the name, we ask the domain's registry. An expired domain shows its expiry date and status: until the owner renews, its registrar usually puts it on hold, which takes it out of DNS, or parks it. A name no registry knows was never registered or has been released. A site that is only down still has its DNS. To see when a name expires, use the domain expiry checker.

How is this different from Downdetector?

Downdetector counts reports from users and compares them with the usual number for that service. This website status checker asks the site itself: from 11 places, from your own browser and in a real browser, for any address, in seconds. For well-known services we also show their official status page. Both views help: reports show what people feel, a check shows what breaks.

Does checking a site tell the site who I am?

The site sees our servers, and for the test from your side, your browser asks it for one page, like a normal visit: then it sees your IP address. We send nothing else, and we never send your browser to a site Cloudflare lists as unsafe. We keep the result and screenshot for up to 24 hours, without your IP, to answer repeat checks and share links.

How often can I check a website, and can I share the result?

Checks of the same address are shared for 90 seconds, so during an outage everyone sees the same fresh result at once; Check again runs a new one. You can check about 12 sites a minute. Copy link shares the result with its screenshot, which we keep for up to 24 hours.

Missing something?Suggest a feature or a new tool

Related tools