Stack Exchange stackexchange.com Live · Operational

Is Stack Exchange down right now? Live status and outage tracker

No, Stack Exchange is up.

No outage detected, and no user reports in the last hour.

Reports, last hour: 0
Usual at this hour: Almost none
Vs the hour before: –

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 96 normal · 0 elevated · 0 outage

Not working for you?

Updated 3 min ago · Data refreshes every 5 minutes

01 · User reports

0 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

Last 24 hours

Stack Exchange outages and problems

User reports, last 24 hours

1 report in total, counted in 15-minute windows

No problem reports came in for Stack Exchange in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 1 report. There has been no spike in reports since 9 November. These are user reports from the US, where most people report Stack Exchange problems.

NormalClose to the usual level24 h · 1 report
ElevatedMore than 1.5 times the usual levelNone in this chart
OutageMore than twice the usual level and far above the day's averageNone in this chart
Usual levelWhat a usual day sees at that timeAlmost none at this time of day

Reports, last hour

Quiet

Uptime, 24 h

100.00%

No outage windows

Last outage

None

In the last 24 hours

Busiest 15 minutes

1 report, 5 h ago

Stack Exchange status card: No, Stack Exchange is up. User reports over the last 24 hours. — **Share this status**The picture people see when this page is shared: the answer and the last 24 hours of reports.
Image

In the past 24 hours, 1 user report came in for Stack Exchange. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 1 report, about 5 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Stack Exchange stayed at their usual level the whole time.

This month

Stack Exchange in November 2026

Problem reports in November (since 9 November): 123

Monthly report for November 2026

People who report a problem with Stack Exchange to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:

Website
Login
App

World map

Where Stack Exchange problem reports come from

The map shows where recent problem reports for Stack Exchange came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.

Outage now
Problems now
Normal

Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

Stack Exchange problem spikes, last 30 days

Since 9 November, Stack Exchange had no outage spikes or periods of elevated reports.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 9 November 2026. Monthly reports for all services

Troubleshooting

How to fix Stack Exchange not working

Stack Exchange is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach stackexchange.com over your own connection, right now. Nothing is sent to us or stored.

Reload Stack Exchange without cache
Press Ctrl+Shift+R on Windows or Command+Shift+R on Mac, then open stackexchange.com in a private or incognito window. That rules out a stale copy. If the page loads there, disable extensions one at a time to find the one that breaks it.
Try another Stack Exchange community
Use the network list on stackexchange.com to open a different community, then load its question list and a question page. If only one community fails, the problem is likely that page or your link to it. If every community fails, keep testing your browser session.
Delete Stack Exchange cookies in DevTools
Open DevTools with F12, go to the Application tab, expand Cookies, select the stackexchange.com domain, and delete the entries. Reload the page, then sign in again with the same email or provider. If login still loops, check that your browser accepts cookies for the site.
Check DNS for stackexchange.com
Run nslookup stackexchange.com in Command Prompt or dig stackexchange.com in Terminal, then repeat it on another device that uses the same network. A DNS failure can show a browser error even when other sites load. If the lookup fails only on your machine, flush the cache with ipconfig /flushdns on Windows or sudo killall -HUP mDNSResponder on macOS; if it fails everywhere, restart the router or try a different network.

While it is down

While Stack Exchange is down: what to use instead

Quora A general question and answer site where you can post a query or read existing answers on many topics; it helps when you need a quick response and a different community is fine.
Reddit Many subreddits have active threads with answers and troubleshooting tips; use it when you want community opinions, but check the quality of replies.
Stack Overflow The programming Q&A site on the same network; go straight to it for coding questions if only the main network page is down.
Super User A direct Stack Exchange site for general computer questions; it can load when the network homepage does not, so try it for non-coding tech issues.

Busiest times

When people report Stack Exchange problems

The busiest hour for reports about Stack Exchange is 00:00 to 01:00 Central European time, and the busiest day is Tuesday.

By hour of the day

By day of the week

Each bar is the average number of user reports in that hour, or on that day of the week, from 36 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Stack Exchange goes down

Stack Exchange is a network of question and answer sites for technical and academic topics. Developers and IT staff rely on it to find fixes and post follow-up questions, so an outage interrupts search, question pages, answer pages, and sign-in.

Search often breaks first. A query hangs, or a question opens with no answers while the header and sidebar still load, and the page keeps waiting. Posting a question or answer may hang, and sign-in can fail with a generic error. Problems are often partial: one site in the network can lag while another works, and trouble can hit one part of the service while the rest stays up.

Servers and network

Stack Exchange IP address, servers and network

Checking stackexchange.com from our server…

Questions

Stack Exchange FAQ

Is Stack Exchange down right now?

The status at the top of this page shows whether user problem reports for Stack Exchange are above their usual level, counted in 15-minute windows over the last 24 hours. Those reports go to a public outage-reporting service, and the status comes only from them; this site does not monitor the service or collect reports itself. To tell whether the problem is on your side, try another network and a private window, then check whether the same failure follows you.

Why do I get 'Oops! Something Bad Happened' when I open a question on Stack Exchange?

That page is the network's generic error screen, so it can appear when a question loads badly or a request times out. Reload once, then try the same question in a private window on another network; if the error follows you across pages, the problem is likely on the service side. If only one question fails, open its meta post or search the site for a duplicate report.

Why does Stack Exchange say 'Too many requests from this IP address' when I try to post?

That message is a rate limit tied to your network address, not a sign that your account is broken. Wait a few minutes and retry, and avoid refreshing the submit button in a loop because each attempt can extend the block. If you share a network with many people, try another connection or a mobile data link to see whether the block clears.

Why can't I comment or answer on a Stack Exchange site?

New accounts and low-reputation accounts face limits on comments and answers, so the site may hide the comment box or reject a short answer. Read the site's posting rules, then edit an existing question or answer to add detail instead of posting a duplicate. If your account was suspended, the notice on your profile page explains the reason and the next step.

Why does Stack Exchange log me out or fail to sign in with my account?

Login problems often come from blocked cookies or an expired third-party sign-in token. Sign in again in a private window with cookies allowed, then check that your email address on the account still works. If you use a Google or GitHub login, confirm that the linked account has not changed before you try a password reset.

Official channels

Contact Stack Exchange support

Tip: Stack Exchange doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.

For your site

Put the Stack Exchange status on your site

Paste one of these into a web page, a blog post or a README: a small badge, or a card with the chart. Both show the same status as this page, based on user problem reports, and link back here.

HTML

<a href="https://isitdownrightnow.app/services/stackexchange/"><img src="https://isitdownrightnow.app/badge/stackexchange.svg" alt="Stack Exchange status" height="20"></a>

Markdown, for README files

[![Stack Exchange status](https://isitdownrightnow.app/badge/stackexchange.svg)](https://isitdownrightnow.app/services/stackexchange/)

A live card with the chart

The status, reports in the last hour and the last 24 hours, updated every 5 minutes. Use the frame, or the image where frames are not allowed, such as newsletters.

Frame

<iframe src="https://isitdownrightnow.app/embed/stackexchange/" title="Stack Exchange status" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe>
<p><a href="https://isitdownrightnow.app/services/stackexchange/">Stack Exchange status</a> from IsItDownRightNow.app</p>

Image, updated about every 10 minutes

<a href="https://isitdownrightnow.app/services/stackexchange/"><img src="https://isitdownrightnow.app/share/stackexchange.png" alt="Stack Exchange status: problem reports over the last 24 hours" width="600" height="315" loading="lazy"></a>

Markdown image, for README files

[![Stack Exchange status](https://isitdownrightnow.app/share/stackexchange.png)](https://isitdownrightnow.app/services/stackexchange/)

Badge, frame and image load no scripts from other sites and set no cookies; people who see them on your page load them from our server. More for journalists.

How we track Stack Exchange

The status on this page comes from user-submitted problem reports for Stack Exchange, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Stack Exchange, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Stack Exchange doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.