Stack Overflow appears to be down

Our check of stackoverflow.com failed: the server did not return a usable response. Checked 0s ago.

Status
Response time
30 ms
First byte
30 ms
Ping
6.4 ms 0% loss
Server IP
198.252.206.1

Result is 0s old (cached for 60 seconds). Refresh · or run a full diagnostic on stackoverflow.com.

What to do now

The failure is at Stack Overflow's end, so there is nothing to fix on your device.

  1. Wait a few minutes and reload this page — most outages of large services last under an hour.
  2. Check the service's own status page or social account for an acknowledgement.
  3. If it is your site, run the full check — it names the failing stage.
  4. Set up a free monitor so you are emailed the moment it recovers.

About this check

Checked from
London, United Kingdom
Method
Live HTTPS request + ICMP ping
Address
stackoverflow.com
Resolved IP
198.252.206.1
Server
cloudflare
Redirects
1
Last checked
14:22:10 UTC

We report only what our own request returned. We do not count user reports, so a single angry tweet cannot make this page say "down".

Is Stack Overflow down for everyone or just me?

That is the only question worth answering when a site stops loading, and it has a simple test: check it from a machine that shares none of your network. This page does exactly that — the request comes from our server in London, using its own DNS resolver and its own route to the internet. If stackoverflow.com answers us, it is up, and whatever is stopping you sits between your device and the wider network.

Local causes are more common than real outages. A stale DNS entry, a router that needs a restart, an ISP resolver holding a bad record, a VPN exit node the service blocks, an ad-blocker rule, or simply a cached error page in your browser: each one produces a site that is "down" for exactly one person.

What a failed check actually means

When a check fails we name the stage that failed rather than saying "down", because the fixes are entirely different. DNS failure means the name could not be turned into an address — an expired domain or a broken nameserver change. Connection refused means the machine answered but nothing is listening: the web server process has stopped. Timeout means packets vanished — a firewall, a routing problem, or a server too loaded to accept connections. TLS error means the site is running but its certificate is expired or mismatched, and every browser will refuse it.

Other developer & infrastructure services

Check the live status of similar services:

Track Stack Overflow automatically

Free monitoring checks every 5 minutes and emails you when the status changes.

Monitor stackoverflow.com for free