Skip to content

Outage tracker / Wikipedia

Is Wikipedia down?

I'm having a problem

Vendor reports no incidentWhat Wikipedia reports

Wikipedia reports no incident on its status page.

As of the last successful poll, 2026-11-05 13:53 UTC.

Wikipedia's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Wikipedia pass from all 10 regions we check.

As of Nov 5, 2026, 2:04 PM UTC, RealUptime's checks of Wikipedia passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:04 PM UTC
US-East336 msChecks passing
US-West1642 msChecks passing
Europe2481 msChecks passing
Asia-Pacific2577 msChecks passing
US-Central1376 msChecks passing
Canada916 msChecks passing
UK644 msChecks passing
Southeast Asia2142 msChecks passing
Australia3130 msChecks passing
South America1666 msChecks passing
their status pagetheir claim, not our reading

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

from Wikipedia's own status page, checked Nov 5, 2026, 1:22 PM UTC
Wikipedia's own status page shows no incident, and our checks of Wikipedia pass right now.

Wikipedia's own component breakdown, as they publish it

  • ReadingOperational
  • EditingOperational

These are Wikipedia's components, named and scored by Wikipedia. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

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
2.1sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 619ms2026-10-08 UTC: p95 613ms2026-10-09 UTC: p95 522ms2026-10-10 UTC: p95 606ms2026-10-11 UTC: p95 604ms2026-10-12 UTC: p95 678ms2026-10-13 UTC: p95 657ms2026-10-14 UTC: p95 502ms2026-10-15 UTC: p95 470ms2026-10-16 UTC: p95 558ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
US-West
2.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 644ms2026-10-08 UTC: p95 642ms2026-10-09 UTC: p95 693ms2026-10-10 UTC: p95 584ms2026-10-11 UTC: p95 628ms2026-10-12 UTC: p95 683ms2026-10-13 UTC: p95 642ms2026-10-14 UTC: p95 659ms2026-10-15 UTC: p95 585ms2026-10-16 UTC: p95 594ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Europe
2.3sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 778ms2026-10-08 UTC: p95 712ms2026-10-09 UTC: p95 707ms2026-10-10 UTC: p95 668ms2026-10-11 UTC: p95 768ms2026-10-12 UTC: p95 687ms2026-10-13 UTC: p95 694ms2026-10-14 UTC: p95 654ms2026-10-15 UTC: p95 774ms2026-10-16 UTC: p95 717ms2026-10-17 UTC: p95 799ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 950ms2026-10-24 UTC: p95 984ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Asia-Pacific
3.5sp95 · 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-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.5s2026-10-24 UTC: p95 2.9s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 3.3s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 3.2s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 3.5s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5
US-Central
1.4sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 809ms2026-10-08 UTC: p95 804ms2026-10-09 UTC: p95 793ms2026-10-10 UTC: p95 989ms2026-10-11 UTC: p95 791ms2026-10-12 UTC: p95 816ms2026-10-13 UTC: p95 788ms2026-10-14 UTC: p95 857ms2026-10-15 UTC: p95 833ms2026-10-16 UTC: p95 948ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 952ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Canada
1.8sp95 · 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-10-07 UTC: p95 756ms2026-10-08 UTC: p95 643ms2026-10-09 UTC: p95 756ms2026-10-10 UTC: p95 677ms2026-10-11 UTC: p95 796ms2026-10-12 UTC: p95 857ms2026-10-13 UTC: p95 731ms2026-10-14 UTC: p95 711ms2026-10-15 UTC: p95 763ms2026-10-16 UTC: p95 698ms2026-10-17 UTC: p95 712ms2026-10-18 UTC: p95 806ms2026-10-19 UTC: p95 897ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
UK
1.3sp95 · 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-10-07 UTC: p95 667ms2026-10-08 UTC: p95 714ms2026-10-09 UTC: p95 682ms2026-10-10 UTC: p95 668ms2026-10-11 UTC: p95 655ms2026-10-12 UTC: p95 648ms2026-10-13 UTC: p95 639ms2026-10-14 UTC: p95 647ms2026-10-15 UTC: p95 563ms2026-10-16 UTC: p95 682ms2026-10-17 UTC: p95 960ms2026-10-18 UTC: p95 942ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 937ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 989ms2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 764ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 804ms2026-11-02 UTC: p95 894ms2026-11-03 UTC: p95 870ms2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 3.2s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
4.3sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.2s2026-10-08 UTC: p95 2.3s2026-10-09 UTC: p95 2.6s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.3s2026-10-12 UTC: p95 2.4s2026-10-13 UTC: p95 2.2s2026-10-14 UTC: p95 2.2s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 3.5s2026-10-19 UTC: p95 3.6s2026-10-20 UTC: p95 3.5s2026-10-21 UTC: p95 3.4s2026-10-22 UTC: p95 3.4s2026-10-23 UTC: p95 3.3s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 3.5s2026-10-26 UTC: p95 3.6s2026-10-27 UTC: p95 3.7s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 4.1s2026-11-03 UTC: p95 3.1s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 4.3s
Oct 7Oct 21Nov 5
South America
2.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 860ms2026-10-08 UTC: p95 907ms2026-10-09 UTC: p95 988ms2026-10-10 UTC: p95 956ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 897ms2026-10-17 UTC: p95 840ms2026-10-18 UTC: p95 430ms2026-10-19 UTC: p95 768ms2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 3.0s2026-10-23 UTC: p95 9.2s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 3.1s2026-11-01 UTC: p95 3.2s2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Wikipedia

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.

What we measured, function by function

Wikipedia answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • ArticlesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • EditingUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • MediaUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • SearchUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • WikidataUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Wikipedia reports an incident on its status page, and again when it reports it resolved.

Get an email when Wikipedia reports an incident

Email me when Wikipedia reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Wikipedia's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 336msstatus code: 200checked: Nov 5, 2026, 2:03 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
      Checks passinglatency: 1642msstatus code: 200checked: Nov 5, 2026, 1:55 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
      Checks passinglatency: 1376msstatus code: 200checked: Nov 5, 2026, 2:04 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
      Checks passinglatency: 916msstatus code: 200checked: Nov 5, 2026, 1:53 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
    Checks passinglatency: 1666msstatus code: 200checked: Nov 5, 2026, 1:57 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 2481msstatus code: 200checked: Nov 5, 2026, 2:02 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
      Checks passinglatency: 644msstatus code: 200checked: Nov 5, 2026, 1:59 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2577msstatus code: 200checked: Nov 5, 2026, 1:51 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
      Checks passinglatency: 2142msstatus code: 200checked: Nov 5, 2026, 1:44 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
      Checks passinglatency: 3130msstatus code: 200checked: Nov 5, 2026, 1:46 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 probe events

Wikimedia API is unavailable, 1h 45mdeclared on their status page2026-10-28
Maintenance, 121h 41mdeclared on their status page2026-10-22
Service disruption, 1h 47mdeclared on their status page2026-09-23
Wikipedia and other sites slow or unavailable, 1h 32mdeclared on their status page2026-08-25
Connectivity issues from Russia, 24h 1mdeclared on their status page2026-07-30
Ongoing network outage, users might be unable to reach the wikis, 5mdeclared on their status page2026-07-01
Wikipedia and other wikis reporting errors with edits, 3h 10mdeclared on their status page2026-04-02
Wikis were in read only mode, 8h 29mdeclared on their status page2026-03-05

check 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 check readings and Wikipedia's own claim at the time, side by side.

Full check history for Wikipedia: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Wikipedia uptime by RealUptime's checksLive, from this page's own readings.
[![Wikipedia uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Wikipedia down?", https://realuptime.io/outages/wikipedia. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://en.wikipedia.org/api/rest_v1/page/summary/Wikipedia
secondary
https://www.wikipedia.org/
secondary
https://en.wikipedia.org/w/api.php?action=opensearch&search=Earth&limit=1&format=json
secondary
https://en.wikipedia.org/wiki/Earth
secondary
https://en.wikipedia.org/w/index.php?title=Earth&action=edit
secondary
https://upload.wikimedia.org/wikipedia/commons/thumb/8/80/Wikipedia-logo-v2.svg/120px-Wikipedia-logo-v2.svg.png
secondary
https://www.wikidata.org/wiki/Special:EntityData/Q42.json

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: en.wikipedia.org

RealUptime is not affiliated with Wikipedia; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.