Is Wikipedia Down?

No — Wikipedia is up

Reachable from all 8 checked regions

Average response time: 656ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://www.wikimediastatus.net

Wikipedia uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

277ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

432ms

DNS 404ms TCP 2ms TLS 9ms TTFB 420ms

lhr

460ms

DNS 327ms TCP 20ms TLS 28ms TTFB 406ms

nrt

831ms

DNS 409ms TCP 67ms TLS 76ms TTFB 649ms

ord

246ms

DNS 109ms TCP 21ms TLS 28ms TTFB 189ms

sin

479ms

DNS 454ms TCP 1ms TLS 10ms TTFB 469ms

sjc

346ms

DNS 316ms TCP 2ms TLS 9ms TTFB 334ms

syd

1932ms

DNS 631ms TCP 205ms TLS 210ms TTFB 1338ms

yyz

526ms

DNS 425ms TCP 15ms TLS 21ms TTFB 485ms

What Wikipedia does

Wikipedia is the Wikimedia Foundation's encyclopedia, edited by volunteers and read by hundreds of millions of people monthly. It is also a dependency for search results, voice assistants and countless applications that pull summaries from its API, so an outage reaches far beyond people who intended to visit the site.

What an outage looks like

Articles fail to load or return error pages, and search from within the site stops returning results. Editing fails while reading continues, since Wikimedia reports the two separately. Images may not render while article text does, because media is served from a different path. Applications and assistants that quote Wikipedia return blanks or fall back to other sources.

What to do about it

Check wikimediastatus.net, the Wikimedia Foundation's own page, which reports Reading and Editing as separate components alongside metrics for request volume, error responses and response time. Reading is usually restored before editing. If you are mid-edit, copy your work out of the browser before reloading, since an unsaved edit is not held anywhere.

Is it down for everyone, or just you?

If this page says Wikipedia is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

IMDb

Cloudflare

Bing

Wikipedia outage FAQ

Is Wikipedia down or is it blocked on my network?

Wikipedia is blocked or filtered in some countries and on some corporate and school networks, which looks identical to an outage from the affected device. Check wikimediastatus.net, which reports globally, and try a different network. If the status page shows Reading as operational, the block is local rather than a Wikimedia incident.

Will I lose an edit I was writing during an outage?

Very likely, if you reload or navigate away. An unsaved edit lives only in your browser and Wikimedia holds nothing until you publish. Copy the text into a local file before touching the page. For long edits this is worth doing habitually rather than only during incidents, since browser crashes cost the same work.

Why can I read Wikipedia but not edit it?

Wikimedia reports Reading and Editing as separate components, and they genuinely fail independently. Serving an article can be handled from cache, while an edit must reach the databases behind it. During a partial incident, or during scheduled maintenance, editing is often disabled deliberately while reading continues uninterrupted for everyone.

Does a Wikipedia outage affect other Wikimedia projects?

Often yes, since Wiktionary, Wikimedia Commons, Wikidata and the rest share infrastructure. The status page covers Wikimedia's services rather than Wikipedia alone. Wikidata mattering here is easy to overlook: many external applications read from it, so an incident propagates into tools that never mention Wikipedia by name.

Why did my app stop showing Wikipedia summaries?

A great many applications, assistants and search features pull from the Wikimedia API, so an incident silently removes content from products that never say where it came from. The application usually shows a blank panel rather than an error. Nothing needs fixing on your side; it returns when Wikimedia does.

How we measure this

We request Wikipedia's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Wikipedia publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Wikipedia goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required