Is it down right now, or is it just you?
Type a website address. Our server in EU (Falkenstein) tries to reach it right away and shows what happened at each step, from the name lookup to the server's first byte, next to the site's downtime history and what other people report. Popular sites are also tested from home and mobile connections in 33 countries.
- Services monitored
- 662
- Each tested every 5 minutes
- Checks in 24 hours
- 197,872
- From our server in EU (Falkenstein)
- Countries tested from
- 33
- 5,188 home or mobile tests in 24 hours
- Outages logged
- 1,013
- Last 30 days, with start and end times
- Official status pages read
- 229
- Shown beside our own results
Live recording
- Googlegoogle.com
291 ms, Up
- YouTubeyoutube.com
363 ms, Up
- ChatGPTchatgpt.com
538 ms, Up
- Discorddiscord.com
63 ms, Up
- GitHubgithub.com
119 ms, Up
- Netflixnetflix.com
488 ms, Up
- X (Twitter)x.com
261 ms, Up
What's down right now
Reported on their own status pages
- Cloudflare StatusChanges made to Workers may be delayed or disruptedPartial System Outage
- DreamHostServer Maintenance: VPS, Managed VPS, Dedicated, and MySQL ServersPartial Service Disruption
- Genesys CloudElevated Error Rates - EMEA (UAE)Partial System Outage
- mastodon.socialNetworking outage at HetznerMinor service disruption
- AWSMultiple services (UAE): Region AvailabilityMinor service disruption
- Salesforcehttps://help.salesforce.com/s/issue?id=a02g700000DbedJMinor service disruption
Live status of popular services
| Service | Status | Response | Uptime 24h | Last check |
|---|---|---|---|---|
Googlegoogle.com | Up | 291 ms | ||
YouTubeyoutube.com | Up | 363 ms | ||
ChatGPTchatgpt.com | Up | 538 ms | ||
Discorddiscord.com | Up | 63 ms | ||
GitHubgithub.com | Up | 119 ms | ||
Netflixnetflix.com | Up | 488 ms | ||
X (Twitter)x.com | Up | 261 ms | ||
Supabasesupabase.com | Up | 177 ms | ||
Cloudflarecloudflare.com | Up | 171 ms | ||
Goodreadsgoodreads.com | Up | 867 ms | ||
Audiomackaudiomack.com | Up | 89 ms | ||
Lichesslichess.org | Up | 106 ms | ||
Kagglekaggle.com | Up | 408 ms | ||
Yahooyahoo.com | Up | 728 ms | ||
Bingbing.com | Up | 415 ms |
What happens when you check a site
Our server opens the site the way your browser would, and times every step. The numbers here are from a real check of ChatGPT, .
Look up the address
3 msComputers find each other by number, not by name. So first we ask DNS, the internet's address book, which number belongs to chatgpt.com.
When this step fails
- No address foundDown
Connect to the server
7 msWe open a connection to that number. This is the first time the site's own server has to respond, so a server that is off or overloaded fails here.
When this step fails
- Connection refusedDown
- No answer in 6 secondsDown
Make it secure
221 msBoth sides agree on encryption, and we check the site's certificate: the same thing behind the padlock in your browser. Sites without HTTPS skip this step.
When this step fails
- Secure connection failsDown
- Certificate expired or wrongProblems
Wait for the first byte
310 msWe ask for the homepage and wait for the first piece of the reply. This is the time the server spends working, so it grows when a site is busy. We read a few kilobytes and stop. The time from connecting to this first byte, 538 ms here, is the response time you see across this site.
When this step fails
- No reply in 10 secondsDown
- Error 500, 502 or 504Down
- Slower than 5 secondsProblems
- Error 503Problems
Up, problems or down
Every check ends in one of three answers. The rules are the same for every site, big or small.
Up
661services now
The server answered.
- With a normal page.
- Or with "access denied" (403) or "too many requests" (429). Many big sites turn away automated checks, but any answer proves the server is there.
Problems
1services now
It answered, but something is off.
- It took longer than 5 seconds.
- It said "service unavailable" (503).
- Its certificate is expired or wrong.
- People report problems at 4 times the usual rate.
Down
0services now
No usable answer.
- The name has no address.
- The connection is refused or times out.
- The secure connection fails.
- It answered with a server error, like 500, 502 or 504.
We try again before calling it down
When a check fails, we wait 2 seconds and try once more. Only the second result counts, so one dropped connection never turns into an outage.
Every 5 minutes, day and night
That is how often we check each of the 662 services on our list. Uptime and the outage log use only these regular checks. Checks people start pile up during outages, so counting them would make sites look worse than they are.
Where we check from
A site can work in one country and fail in the next. So we test from more than one place, and every result says where it came from.
Our server in EU (Falkenstein)
It checks all 662 services every 5 minutes. Only its results decide status, uptime and outages, so those numbers always mean the same thing.
Home and mobile connections in 33 countries
Globalping is a network of small probes that volunteers run on ordinary internet connections. Through it we test each service from up to 12 countries at a time: every few hours, and every 15 minutes while it is failing. These results show on the map but never change a status.
Your own browser
Every status page has a button that tests the site from your connection, so you can compare it with ours. Not sure it's the site at all? The connection test checks your internet as a whole.
What people and services tell us
Our check covers the homepage. Logins, apps and payments can break while it still loads, so we also count reports and read official status pages.
Reports from visitors
Anyone can report a problem on a status page, once an hour per site. We only say a site may have problems when it gets at least 5 reports in an hour and 4 times its usual number. You always see the real count.
The service's own status page
We read 229 official status pages every few minutes and show what they say next to our result, marked as the service's own words. When we disagree, you see both.
Shared networks
We note which network answered each check, such as Cloudflare or Amazon Web Services. When 3 or more sites on one network fail at the same time, the status page says the network may be the cause.
It works for us, but not for you?
Then the problem is usually somewhere between you and the site. Try these in order, quickest first.
Reload without the cache
Press Ctrl+Shift+R, or Cmd+Shift+R on a Mac. Your browser loads the page fresh instead of using a saved copy.
Try another network
Switch your phone from Wi-Fi to mobile data. If the site opens, the problem is your Wi-Fi or your provider.
Pause your VPN and blockers
VPNs, proxies, ad blockers and security apps can block single sites. Turn them off for a minute and try again.
Restart your router
Unplug it, wait 30 seconds and plug it back in. That clears many small network faults.
Change your DNS server
If the name won't load for you but works for us, a public DNS server such as 1.1.1.1 or 8.8.8.8 often fixes it.
Test your connection
Our connection test checks your internet, DNS, delay and device clock in a few seconds.
What a check can't tell you
- Whether logins, apps or payments work. We check the homepage. Visitor reports fill this gap.
- What every provider sees. One home or mobile connection per country is a sample, not the whole picture.
- What the service itself thinks. We aren't linked to any service we list, and our results are not their official word.
Free tools
No account, no cookies, nothing to install.
- Is my internet down?Test your connection, DNS, latency and device clock in a few seconds.
- Uptime and SLA calculatorTurn 99.9% into the minutes of downtime it allows per month and year.
- What is my IP?The address and network websites see, looked up and never stored.
- Badges, feeds and APIEmbed a live status badge, or read our results as JSON or Atom.
Recently checked by visitors
| Website | Result | Response | From | Checked |
|---|---|---|---|---|
| Kagglekaggle.com | Up | EU (Falkenstein) | ||
| Kagglekaggle.com | Up | EU (Falkenstein) | ||
| Replitreplit.com | Up | EU (Falkenstein) | ||
| Audiomackaudiomack.com | Up | EU (Falkenstein) | ||
| Audiomackaudiomack.com | Down | EU (Falkenstein) | ||
| GitHubgithub.com | Up | EU (Falkenstein) | ||
| pomidor.live | Up | EU (Falkenstein) | ||
| wintomato.com | Up | EU (Falkenstein) | ||
| wintomato.com | Up | EU (Falkenstein) | ||
| pomidor.live | Up | EU (Falkenstein) | ||
| wintomato.com | Up | EU (Falkenstein) | ||
| ledmegastore.de | Up | EU (Falkenstein) | ||
| tramvene.com | Up | EU (Falkenstein) | ||
| Doubandouban.com | Up | EU (Falkenstein) | ||
| ff.uni-lj.si | Down | EU (Falkenstein) |
Website not loading? Start here
- How do I check if a website is down?
- Type its address into the box at the top of this page. Within a few seconds our server in EU (Falkenstein) looks up the name, connects, completes the secure handshake and waits for the first byte. You see whether it answered, how long each step took and, for sites we monitor, every outage we have logged.
- Is the website down, or its server?
- The step that failed tells you. If the name doesn't resolve, the fault is the domain or its DNS. If the connection is refused or times out, the server or its network isn't answering. If the server replies with an error such as 500 or 502, it is running but the site behind it is failing. Every check shows each step and how long it took.
- Where do you check from?
- Our primary server in EU (Falkenstein) checks every monitored service every 5 minutes, and its results alone decide a site's status, uptime and outage log. Monitored services are also tested from home and mobile connections in a dozen countries at a time, through the Globalping network: every few hours, and every 15 minutes during an outage. In the last 24 hours those tests came from 33 countries. Each status page shows the result from every country on its map, so you can tell a global outage from a regional one.
- Why does a site load for other people but not for me?
- When our server gets an answer and your browser doesn't, the fault usually sits between you and the site: your Wi-Fi or mobile provider, an outdated DNS entry, a VPN, firewall or ad blocker, or a stale browser cache. Every status page has a button that makes your own browser try the site, so you can compare the two results.
- When do you call a site down?
- When its name does not resolve, the connection is refused or times out, the secure connection fails, or the server replies with an error such as 500, 502 or 504. A failed check is repeated before it counts. A site that answers slowly, replies 503, or draws far more problem reports than usual is marked as having problems instead.
- How often are popular services checked?
- The 662 services in our directory are tested every 5 minutes, day and night, and their uptime figures come only from those scheduled checks. Any other site is checked when someone asks, at most once a minute.
- Can you track downtime for my own website?
- You can ask us to. Check it here once, then press "Request monitoring" on its status page. We review every request. A site we add is checked every 5 minutes, and its status page keeps a downtime log with start and end times and its uptime. We don't send email alerts yet.
- Is this the official status page of these services?
- No. upordown.online is independent and not affiliated with any service it checks. When a service publishes its own status page, we show what it says beside our results, labelled as the service's own statement.
- Do I need an account, and does it cost anything?
- No to both. There are no accounts and no cookies. Checks, outage feeds, status badges and the JSON API are free to use.
