Skip to content

Outage tracker / Wikipedia

Is Wikipedia down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Wikipedia from all 10 regions we check.

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

Functional endpoints verified

No outage recorded in the 58 days we have measured Wikipedia (since Aug 8, 2026).

our independent probeslive · checked Oct 5, 2026, 8:13 PM UTC
US-East1145 msOperational
US-West379 msOperational
Europe605 msOperational
Asia-Pacific597 msOperational
US-Central472 msOperational
Canada417 msOperational
UK628 msOperational
Southeast Asia1358 msOperational
Australia1853 msOperational
South America578 msOperational
their status pagetheir claim, not our reading

Wikipedia reports: All systems operational (“All Systems Operational”)

from Wikipedia's own status page, checked Aug 21, 2026, 3:33 AM UTC
Our probes and Wikipedia's own status page agree: both show Wikipedia as reachable right now.

This is Wikipedia's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Wikipedia response time, by region

US-East
690msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 263ms2026-09-07 UTC: p95 272ms2026-09-08 UTC: p95 284ms2026-09-09 UTC: p95 246ms2026-09-10 UTC: p95 272ms2026-09-11 UTC: p95 293ms2026-09-12 UTC: p95 329ms2026-09-13 UTC: p95 355ms2026-09-14 UTC: p95 369ms2026-09-15 UTC: p95 392ms2026-09-16 UTC: p95 479ms2026-09-17 UTC: p95 575ms2026-09-18 UTC: p95 481ms2026-09-19 UTC: p95 487ms2026-09-20 UTC: p95 470ms2026-09-21 UTC: p95 424ms2026-09-22 UTC: p95 557ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 432ms2026-09-26 UTC: p95 457ms2026-09-27 UTC: p95 437ms2026-09-28 UTC: p95 433ms2026-09-29 UTC: p95 485ms2026-09-30 UTC: p95 435ms2026-10-01 UTC: p95 554ms2026-10-02 UTC: p95 726ms2026-10-03 UTC: p95 558ms2026-10-04 UTC: p95 718ms2026-10-05 UTC: p95 690ms
Sep 6Sep 20Oct 5
US-West
616msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 476ms2026-09-07 UTC: p95 478ms2026-09-08 UTC: p95 449ms2026-09-09 UTC: p95 344ms2026-09-10 UTC: p95 338ms2026-09-11 UTC: p95 282ms2026-09-12 UTC: p95 342ms2026-09-13 UTC: p95 322ms2026-09-14 UTC: p95 267ms2026-09-15 UTC: p95 636ms2026-09-16 UTC: p95 704ms2026-09-17 UTC: p95 675ms2026-09-18 UTC: p95 641ms2026-09-19 UTC: p95 657ms2026-09-20 UTC: p95 632ms2026-09-21 UTC: p95 703ms2026-09-22 UTC: p95 643ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 923ms2026-09-26 UTC: p95 638ms2026-09-27 UTC: p95 607ms2026-09-28 UTC: p95 601ms2026-09-29 UTC: p95 551ms2026-09-30 UTC: p95 620ms2026-10-01 UTC: p95 726ms2026-10-02 UTC: p95 730ms2026-10-03 UTC: p95 720ms2026-10-04 UTC: p95 679ms2026-10-05 UTC: p95 616ms
Sep 6Sep 20Oct 5
Europe
801msp95 · 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 613ms2026-09-07 UTC: p95 628ms2026-09-08 UTC: p95 608ms2026-09-09 UTC: p95 656ms2026-09-10 UTC: p95 723ms2026-09-11 UTC: p95 649ms2026-09-12 UTC: p95 615ms2026-09-13 UTC: p95 639ms2026-09-14 UTC: p95 596ms2026-09-15 UTC: p95 762ms2026-09-16 UTC: p95 862ms2026-09-17 UTC: p95 862ms2026-09-18 UTC: p95 781ms2026-09-19 UTC: p95 712ms2026-09-20 UTC: p95 747ms2026-09-21 UTC: p95 777ms2026-09-22 UTC: p95 762ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 732ms2026-09-26 UTC: p95 719ms2026-09-27 UTC: p95 656ms2026-09-28 UTC: p95 763ms2026-09-29 UTC: p95 734ms2026-09-30 UTC: p95 590ms2026-10-01 UTC: p95 784ms2026-10-02 UTC: p95 960ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 832ms2026-10-05 UTC: p95 801ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 2.2s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
US-Central
776msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 708ms2026-09-07 UTC: p95 621ms2026-09-08 UTC: p95 626ms2026-09-09 UTC: p95 667ms2026-09-10 UTC: p95 639ms2026-09-11 UTC: p95 594ms2026-09-12 UTC: p95 742ms2026-09-13 UTC: p95 646ms2026-09-14 UTC: p95 724ms2026-09-15 UTC: p95 726ms2026-09-16 UTC: p95 691ms2026-09-17 UTC: p95 667ms2026-09-18 UTC: p95 720ms2026-09-19 UTC: p95 746ms2026-09-20 UTC: p95 723ms2026-09-21 UTC: p95 736ms2026-09-22 UTC: p95 806ms2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 890ms2026-09-26 UTC: p95 858ms2026-09-27 UTC: p95 745ms2026-09-28 UTC: p95 733ms2026-09-29 UTC: p95 658ms2026-09-30 UTC: p95 699ms2026-10-01 UTC: p95 845ms2026-10-02 UTC: p95 863ms2026-10-03 UTC: p95 874ms2026-10-04 UTC: p95 784ms2026-10-05 UTC: p95 776ms
Sep 6Sep 20Oct 5
Canada
842msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 755ms2026-09-07 UTC: p95 532ms2026-09-08 UTC: p95 577ms2026-09-09 UTC: p95 636ms2026-09-10 UTC: p95 684ms2026-09-11 UTC: p95 823ms2026-09-12 UTC: p95 642ms2026-09-13 UTC: p95 721ms2026-09-14 UTC: p95 838ms2026-09-15 UTC: p95 771ms2026-09-16 UTC: p95 684ms2026-09-17 UTC: p95 714ms2026-09-18 UTC: p95 693ms2026-09-19 UTC: p95 743ms2026-09-20 UTC: p95 746ms2026-09-21 UTC: p95 721ms2026-09-22 UTC: p95 524ms2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 723ms2026-09-26 UTC: p95 686ms2026-09-27 UTC: p95 758ms2026-09-28 UTC: p95 790ms2026-09-29 UTC: p95 605ms2026-09-30 UTC: p95 716ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 864ms2026-10-03 UTC: p95 876ms2026-10-04 UTC: p95 865ms2026-10-05 UTC: p95 842ms
Sep 6Sep 20Oct 5
UK
622msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 558ms2026-09-07 UTC: p95 455ms2026-09-08 UTC: p95 402ms2026-09-09 UTC: p95 445ms2026-09-10 UTC: p95 446ms2026-09-11 UTC: p95 439ms2026-09-12 UTC: p95 396ms2026-09-13 UTC: p95 376ms2026-09-14 UTC: p95 401ms2026-09-15 UTC: p95 455ms2026-09-16 UTC: p95 498ms2026-09-17 UTC: p95 481ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 496ms2026-09-20 UTC: p95 440ms2026-09-21 UTC: p95 501ms2026-09-22 UTC: p95 532ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 928ms2026-09-26 UTC: p95 757ms2026-09-27 UTC: p95 420ms2026-09-28 UTC: p95 496ms2026-09-29 UTC: p95 435ms2026-09-30 UTC: p95 466ms2026-10-01 UTC: p95 890ms2026-10-02 UTC: p95 611ms2026-10-03 UTC: p95 629ms2026-10-04 UTC: p95 733ms2026-10-05 UTC: p95 622ms
Sep 6Sep 20Oct 5
Southeast Asia
1.4sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 836ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 2.2s2026-09-23 UTC: p95 2.4s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
Australia
2.4sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.2s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 2.4s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 2.3s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 2.4s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 2.2s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.4s2026-10-04 UTC: p95 2.1s2026-10-05 UTC: p95 2.4s
Sep 6Sep 20Oct 5
South America
1.1sp95 · 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 975ms2026-09-07 UTC: p95 882ms2026-09-08 UTC: p95 948ms2026-09-09 UTC: p95 945ms2026-09-10 UTC: p95 739ms2026-09-11 UTC: p95 808ms2026-09-12 UTC: p95 755ms2026-09-13 UTC: p95 835ms2026-09-14 UTC: p95 761ms2026-09-15 UTC: p95 999ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 885ms2026-09-21 UTC: p95 845ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 886ms2026-09-26 UTC: p95 993ms2026-09-27 UTC: p95 976ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 766ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 943ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5

Is it Wikipedia, 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 Wikipedia -- it cannot diagnose Wikipedia's own systems.

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

Get told when we measure this

We will tell you when our probes stop reaching Wikipedia, and again when they can reach it again. That is our own measurement from ten regions, not Wikipedia'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: 1145msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Wikipedia normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 379msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Wikipedia normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 472msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Wikipedia normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 417msstatus code: 200checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Wikipedia normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 578msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Wikipedia normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 605msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Wikipedia normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 628msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Wikipedia 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: 597msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Wikipedia normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1358msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Wikipedia normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1853msstatus code: 200checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Wikipedia 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 Wikipedia, 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 Wikipedia yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Wikipedia.

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

We have been measuring Wikipedia since August 8, 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 Wikipedia covering any window you pick, with our measurements and Wikipedia's own claim at the time, side by side.

Full availability history for Wikipedia: 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

Wikipedia uptime measured by RealUptimeLive, from this page's own readings.
[![Wikipedia uptime measured by RealUptime](https://realuptime.io/outages/wikipedia/badge.svg?days=30)](https://realuptime.io/outages/wikipedia)
<a href="https://realuptime.io/outages/wikipedia"><img src="https://realuptime.io/outages/wikipedia/badge.svg?days=30" alt="Wikipedia 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 Wikipedia's SLA implies, from our measurement

At or above your target

We measured none of downtime for Wikipedia 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 Wikipedia'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://en.wikipedia.org/api/rest_v1/page/summary/Wikipedia
secondary
https://www.wikipedia.org/
RealUptime is not affiliated with Wikipedia; the name identifies what we measured, and nothing here speaks for Wikipedia's own team. We send a single web request to Wikipedia from 10 regions on our own schedule and time the response. We do not see inside Wikipedia's systems, do not use an account or real transaction, and are not the same signal Wikipedia's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Wikipedia 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.