Is my site down?
Ask the whole world.
Check any website or API from 17 locations on six continents, live. In a few seconds you know if it’s down for everyone or just you, with the status code and response time from each region.
hyperping.com
hyperping.com is up.
It answered from all 17 regions, with a median of 36 ms. If it won’t load for you, the problem is between you and the site. What to try on your side
- Regions up
- 17/17
- Median
- 36 ms
- Fastest
- London · 22 ms
- IP address
- 76.76.21.21
- San Francisco20048 ms
- N. California20036 ms
- N. Virginia20030 ms
- New York20075 ms
- Toronto20051 ms
- São Paulo20052 ms
- London20022 ms
- Paris20027 ms
- Frankfurt20039 ms
- Amsterdam20074 ms
- Cape Town20029 ms
- Mumbai20033 ms
- Bangalore20098 ms
- Singapore20026 ms
- Seoul20034 ms
- Tokyo20030 ms
- Sydney20044 ms
Down for everyone, or just you? How to read the answer.
- 17/17
Up everywhere: it’s just you
Every region reached the site, so the problem is on your side: your network, DNS resolver, VPN or browser. Try mobile data, flush your DNS cache, turn off the VPN or ad blocker, or open a private window.
- 0/17
Down everywhere: it’s not just you
No region could reach it, so it’s down for everyone. If the site isn’t yours, check the company’s status page and give it a few minutes. If it is yours, go through the checklist below.
- 14/17
Down in some regions
Part of the world can’t reach it. Usually a failing CDN edge or load balancer node, a DNS change still propagating, a firewall or geo-block, or a routing problem between networks.
- DNS
Domain not found
The name doesn’t resolve anywhere. Check the spelling first, then the DNS records and nameservers, and whether the domain has expired.
- 403
Up, but refusing the check
The server answered with a 4xx. A 403 often comes from bot protection or a firewall that blocks data centers, a 404 from a wrong path. People may still load the site fine.
- 10 s
No answer within 10 seconds
Nothing came back in time. The server is overloaded or stuck, or a firewall silently drops the traffic. Browsers would keep spinning too.
What each answer means. The codes you’ll see, in plain words.
| Answer | What it means | Read more |
|---|---|---|
200OK | The page loaded. All good. | What a 200 means |
301 · 302Redirect | The page moved. The check follows redirects and reports the final page. | |
401 · 403Unauthorized · Forbidden | The server is up but refuses the request: a login wall, bot protection or an IP block. | 401 vs 403 |
404Not Found | The server is up, the page isn’t there. Check the path. | 404 vs 500 |
429Too Many Requests | The server is up and rate limiting. Too many requests from the same address. | |
500Internal Server Error | The application crashed while building the page. | |
502Bad Gateway | A proxy or load balancer got no valid answer from the application behind it. | |
503Service Unavailable | The server can’t take requests right now: overloaded, or down for maintenance. | Fixing a 503 |
504Gateway Timeout | The application behind the proxy took too long to answer. | |
520 to 526Cloudflare | Cloudflare answered, but couldn’t reach the origin server or trust its certificate. | |
TimeoutNo answer | Nothing came back within 10 seconds. | |
DNSDomain not found | The domain doesn’t resolve to any address. | |
RefusedConnection refused | The machine answered, but nothing listens on that port. |
Your site is down? Check these, in this order.
- 01
Confirm it from outside
One failing region can be a network blip. A failure from several regions, or from all of them, is an outage.
- 02
Check your providers’ status pages
Your host, CDN, DNS provider and cloud region. If one of them has an incident, you know where to look and roughly how long to wait.
- 03
Check DNS and the domain
A DNS error means a record changed, the nameservers moved or the domain expired. Run dig, or open your registrar.
Domain expiry monitoring - 04
Check the SSL certificate
An expired or mismatched certificate stops browsers even when the server answers. Look at its dates and hostnames.
SSL monitoring - 05
Look at the last deploy
Most outages follow a change. Read the logs from the release and roll it back if the timing matches.
- 06
Check the server itself
CPU, memory and disk. A full disk, or a process killed for lack of memory, takes a site down without warning.
Server monitoring - 07
Tell your users
Post an incident on your status page before the support tickets pile up, and update it until it’s fixed.
Status pages - →
Next time, hear it first
A Hyperping monitor runs this check around the clock and alerts you before your users notice.
Start monitoring free
How this check works. The same probes as Hyperping’s monitors.
- GET
A real request from 17 regions
A GET request to your URL from probes in North America, South America, Europe, Africa, Asia and Oceania. The same probes run Hyperping’s monitors.
- < 400
Redirects followed, 10 second timeout
Redirects are followed to the final page, and up means a status below 400. A region with no answer within 10 seconds counts as a timeout.
- ms
Response time from each region
Each bar is the time to the first byte of the answer from that region, DNS lookup and TLS handshake included. Hover a row for the breakdown.
- 30 s
No account, no history
Results aren’t saved and no alert is sent. A URL checked in the last 30 seconds gets that same result, and each site gets a limited number of checks, so nobody can flood a site through this page.
North America
- San Francisco
- N. California
- N. Virginia
- New York
- Toronto
South America
- São Paulo
Europe
- London
- Paris
- Frankfurt
- Amsterdam
Africa
- Cape Town
Asia
- Mumbai
- Bangalore
- Singapore
- Seoul
- Tokyo
Oceania
- Sydney
Trusted by teams that put uptime first.
Read customer stories
Stop refreshing. Know the moment it goes down.
This page checks once, when you ask. A Hyperping monitor runs the same check around the clock and tells your team the moment it fails.
- 30 s
Checked around the clock
From up to 18 regions, as often as every 30 seconds on paid plans and every 5 minutes on Free.
- rechecked
Confirmed before anyone is woken up
A failure is rechecked from other regions before an alert goes out. A network blip in one place never pages you at 3 a.m.
- Slack · SMS
Alerts where your team is
Slack, Teams, SMS, phone calls, email, PagerDuty and webhooks, with on-call rotations and escalation policies.
- status page
A status page that updates itself
Each confirmed outage shows on your public status page, so customers know before they write to support.
- SSL · domain
Expiry reminders
Reminders up to 90 days before a certificate or a domain runs out.
- 99.98%
Uptime and response time reports
Uptime, response times and incidents for each monitor, ready to share with customers.
Questions about website downtime.
How do I check if a website is down?
Enter its address in the box at the top of this page. Hyperping requests it from 17 regions on six continents at once and shows the status code and response time from each one. If every region gets an answer, the site is up and the problem is on your side. If none does, it’s down for everyone.
Is it down for everyone or just me?
If the check shows the site up from every region but it won’t load for you, it’s just you: your connection, DNS resolver, VPN, firewall or browser. If it fails from every region, it’s down for everyone. If it fails from some regions only, it’s a regional outage.
Why is a website down for me but working for others?
The usual suspects are a stale DNS cache, a VPN or proxy, your internet provider’s routing, a company firewall or a browser extension. Try another network such as mobile data, flush your DNS cache, restart your router, or open the site in a private window.
Why is a site down in only some regions?
A regional failure usually comes from a CDN edge or load balancer node in trouble, DNS changes that haven’t reached every resolver yet, firewall rules or geo-blocking, or a routing problem between networks. For the people in those regions, it’s a real outage even if the site loads for you.
What do 403 and 503 status codes mean?
A 403 Forbidden means the server is up but refuses the request, often because of bot protection, a firewall or a missing login. A 503 Service Unavailable means the server can’t handle requests right now, usually because it’s overloaded or in maintenance. See the table of status codes above, or our guides to 401 vs 403 and 503 errors.
Is this website down checker free?
Yes. It’s free, needs no account and keeps nothing. To protect the sites being checked, each visitor can run a few checks per minute, and a URL checked in the last 30 seconds gets that same result.
Can I check an API endpoint or a specific page?
Yes. Paste the full URL with its path and query string: the check sends a GET request and follows redirects. To check an API with headers, a request body or an expected response, set up a free uptime monitor.
How do I get alerted when my site goes down?
Add your site as a monitor in a free Hyperping account. Hyperping checks it from up to 18 regions, confirms each failure from other regions, and alerts you by email, Slack, Teams, SMS or phone call. The free plan includes 20 monitors checked every 5 minutes; paid plans check every 30 seconds. See pricing.