Skip to content

Outage tracker / Stack Overflow

Is Stack Overflow down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Stack Overflow from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Stack Overflow answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Stack Overflow (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East263 msOperational
US-West435 msOperational
Europe217 msOperational
Asia-Pacific534 msOperational
US-Central324 msOperational
Canada342 msOperational
UK338 msOperational
Southeast Asia711 msOperational
Australia327 msOperational
South America923 msOperational
their status pagetheir claim, not our reading

Stack Overflow publishes no status feed we can read, so the only independent reading here is ours on the left.

Stack Overflow response time, by region

US-East
464msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 398ms2026-09-07 UTC: p95 352ms2026-09-08 UTC: p95 358ms2026-09-09 UTC: p95 271ms2026-09-10 UTC: p95 272ms2026-09-11 UTC: p95 455ms2026-09-12 UTC: p95 359ms2026-09-13 UTC: p95 362ms2026-09-14 UTC: p95 399ms2026-09-15 UTC: p95 426ms2026-09-16 UTC: p95 503ms2026-09-17 UTC: p95 515ms2026-09-18 UTC: p95 520ms2026-09-19 UTC: p95 453ms2026-09-20 UTC: p95 448ms2026-09-21 UTC: p95 473ms2026-09-22 UTC: p95 573ms2026-09-23 UTC: p95 559ms2026-09-24 UTC: p95 621ms2026-09-25 UTC: p95 433ms2026-09-26 UTC: p95 460ms2026-09-27 UTC: p95 436ms2026-09-28 UTC: p95 526ms2026-09-29 UTC: p95 574ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 586ms2026-10-02 UTC: p95 414ms2026-10-03 UTC: p95 434ms2026-10-04 UTC: p95 378ms2026-10-05 UTC: p95 464ms
Sep 6Sep 20Oct 5
US-West
467msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 505ms2026-09-07 UTC: p95 496ms2026-09-08 UTC: p95 365ms2026-09-09 UTC: p95 307ms2026-09-10 UTC: p95 302ms2026-09-11 UTC: p95 332ms2026-09-12 UTC: p95 291ms2026-09-13 UTC: p95 361ms2026-09-14 UTC: p95 249ms2026-09-15 UTC: p95 418ms2026-09-16 UTC: p95 598ms2026-09-17 UTC: p95 579ms2026-09-18 UTC: p95 595ms2026-09-19 UTC: p95 714ms2026-09-20 UTC: p95 704ms2026-09-21 UTC: p95 751ms2026-09-22 UTC: p95 813ms2026-09-23 UTC: p95 746ms2026-09-24 UTC: p95 698ms2026-09-25 UTC: p95 935ms2026-09-26 UTC: p95 907ms2026-09-27 UTC: p95 678ms2026-09-28 UTC: p95 570ms2026-09-29 UTC: p95 460ms2026-09-30 UTC: p95 450ms2026-10-01 UTC: p95 447ms2026-10-02 UTC: p95 331ms2026-10-03 UTC: p95 356ms2026-10-04 UTC: p95 394ms2026-10-05 UTC: p95 467ms
Sep 6Sep 20Oct 5
Europe
523msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 751ms2026-09-07 UTC: p95 693ms2026-09-08 UTC: p95 772ms2026-09-09 UTC: p95 706ms2026-09-10 UTC: p95 540ms2026-09-11 UTC: p95 548ms2026-09-12 UTC: p95 545ms2026-09-13 UTC: p95 563ms2026-09-14 UTC: p95 555ms2026-09-15 UTC: p95 647ms2026-09-16 UTC: p95 817ms2026-09-17 UTC: p95 926ms2026-09-18 UTC: p95 872ms2026-09-19 UTC: p95 910ms2026-09-20 UTC: p95 800ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 997ms2026-09-26 UTC: p95 829ms2026-09-27 UTC: p95 637ms2026-09-28 UTC: p95 800ms2026-09-29 UTC: p95 898ms2026-09-30 UTC: p95 592ms2026-10-01 UTC: p95 541ms2026-10-02 UTC: p95 498ms2026-10-03 UTC: p95 703ms2026-10-04 UTC: p95 588ms2026-10-05 UTC: p95 523ms
Sep 6Sep 20Oct 5
Asia-Pacific
856msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 779ms2026-09-07 UTC: p95 796ms2026-09-08 UTC: p95 990ms2026-09-09 UTC: p95 991ms2026-09-10 UTC: p95 851ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 926ms2026-09-13 UTC: p95 818ms2026-09-14 UTC: p95 815ms2026-09-15 UTC: p95 826ms2026-09-16 UTC: p95 820ms2026-09-17 UTC: p95 750ms2026-09-18 UTC: p95 722ms2026-09-19 UTC: p95 747ms2026-09-20 UTC: p95 814ms2026-09-21 UTC: p95 827ms2026-09-22 UTC: p95 932ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 983ms2026-09-26 UTC: p95 981ms2026-09-27 UTC: p95 984ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 913ms2026-09-30 UTC: p95 987ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 950ms2026-10-05 UTC: p95 856ms
Sep 6Sep 20Oct 5
US-Central
462msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 435ms2026-09-07 UTC: p95 469ms2026-09-08 UTC: p95 488ms2026-09-09 UTC: p95 434ms2026-09-10 UTC: p95 417ms2026-09-11 UTC: p95 433ms2026-09-12 UTC: p95 430ms2026-09-13 UTC: p95 454ms2026-09-14 UTC: p95 542ms2026-09-15 UTC: p95 466ms2026-09-16 UTC: p95 344ms2026-09-17 UTC: p95 412ms2026-09-18 UTC: p95 440ms2026-09-19 UTC: p95 521ms2026-09-20 UTC: p95 544ms2026-09-21 UTC: p95 466ms2026-09-22 UTC: p95 494ms2026-09-23 UTC: p95 606ms2026-09-24 UTC: p95 638ms2026-09-25 UTC: p95 405ms2026-09-26 UTC: p95 450ms2026-09-27 UTC: p95 442ms2026-09-28 UTC: p95 460ms2026-09-29 UTC: p95 551ms2026-09-30 UTC: p95 553ms2026-10-01 UTC: p95 507ms2026-10-02 UTC: p95 571ms2026-10-03 UTC: p95 546ms2026-10-04 UTC: p95 494ms2026-10-05 UTC: p95 462ms
Sep 6Sep 20Oct 5
Canada
454msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 476ms2026-09-07 UTC: p95 343ms2026-09-08 UTC: p95 443ms2026-09-09 UTC: p95 393ms2026-09-10 UTC: p95 336ms2026-09-11 UTC: p95 500ms2026-09-12 UTC: p95 575ms2026-09-13 UTC: p95 566ms2026-09-14 UTC: p95 563ms2026-09-15 UTC: p95 511ms2026-09-16 UTC: p95 523ms2026-09-17 UTC: p95 507ms2026-09-18 UTC: p95 447ms2026-09-19 UTC: p95 481ms2026-09-20 UTC: p95 472ms2026-09-21 UTC: p95 525ms2026-09-22 UTC: p95 580ms2026-09-23 UTC: p95 656ms2026-09-24 UTC: p95 462ms2026-09-25 UTC: p95 406ms2026-09-26 UTC: p95 533ms2026-09-27 UTC: p95 562ms2026-09-28 UTC: p95 637ms2026-09-29 UTC: p95 619ms2026-09-30 UTC: p95 554ms2026-10-01 UTC: p95 566ms2026-10-02 UTC: p95 544ms2026-10-03 UTC: p95 626ms2026-10-04 UTC: p95 523ms2026-10-05 UTC: p95 454ms
Sep 6Sep 20Oct 5
UK
490msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 513ms2026-09-07 UTC: p95 563ms2026-09-08 UTC: p95 560ms2026-09-09 UTC: p95 556ms2026-09-10 UTC: p95 753ms2026-09-11 UTC: p95 691ms2026-09-12 UTC: p95 652ms2026-09-13 UTC: p95 706ms2026-09-14 UTC: p95 406ms2026-09-15 UTC: p95 472ms2026-09-16 UTC: p95 484ms2026-09-17 UTC: p95 487ms2026-09-18 UTC: p95 530ms2026-09-19 UTC: p95 497ms2026-09-20 UTC: p95 547ms2026-09-21 UTC: p95 613ms2026-09-22 UTC: p95 639ms2026-09-23 UTC: p95 792ms2026-09-24 UTC: p95 715ms2026-09-25 UTC: p95 698ms2026-09-26 UTC: p95 660ms2026-09-27 UTC: p95 527ms2026-09-28 UTC: p95 576ms2026-09-29 UTC: p95 525ms2026-09-30 UTC: p95 592ms2026-10-01 UTC: p95 644ms2026-10-02 UTC: p95 640ms2026-10-03 UTC: p95 587ms2026-10-04 UTC: p95 437ms2026-10-05 UTC: p95 490ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 956ms2026-09-07 UTC: p95 933ms2026-09-08 UTC: p95 953ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 966ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 808ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 903ms2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 924ms2026-09-13 UTC: p95 892ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 981ms2026-09-24 UTC: p95 896ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5

Is it Stack Overflow, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Stack Overflow -- it cannot diagnose Stack Overflow's own systems.

Get an email when we see Stack Overflow go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Stack Overflow, and again when they can reach it again. That is our own measurement from ten regions, not Stack Overflow's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 263msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Stack Overflow normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 435msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Stack Overflow normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 324msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Stack Overflow normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 342msstatus code: 200checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Stack Overflow normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 923msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Stack Overflow normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 217msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Stack Overflow normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 338msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Stack Overflow normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 534msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Stack Overflow normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 711msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Stack Overflow normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 327msstatus code: 200checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Stack Overflow normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Stack Overflow, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Stack Overflow yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Stack Overflow.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Stack Overflow since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Stack Overflow covering any window you pick, with our measurements and Stack Overflow's own claim at the time, side by side.

Full availability history for Stack Overflow: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Stack Overflow uptime measured by RealUptimeLive, from this page's own readings.
[![Stack Overflow uptime measured by RealUptime](https://realuptime.io/outages/stack-overflow/badge.svg?days=30)](https://realuptime.io/outages/stack-overflow)
<a href="https://realuptime.io/outages/stack-overflow"><img src="https://realuptime.io/outages/stack-overflow/badge.svg?days=30" alt="Stack Overflow uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Stack Overflow's SLA implies, from our measurement

At or above your target

We measured none of downtime for Stack Overflow over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Stack Overflow's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.stackexchange.com/2.3/info?site=stackoverflow
RealUptime is not affiliated with Stack Overflow; the name identifies what we measured, and nothing here speaks for Stack Overflow's own team. We send a single web request to Stack Overflow from 10 regions on our own schedule and time the response. We do not see inside Stack Overflow's systems, do not use an account or real transaction, and are not the same signal Stack Overflow's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Stack Overflow is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.