Skip to main content

Is Wikipedia Down?

No — Wikipedia is up
Wikipedia's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 527 ms

Right now

The verdict is the worse of these two. How we decide

Wikipedia's status page

wikimediastatus.net · read · checked every 3 minutes

Operational
Wikipedia's components, as its status page reports them
ComponentStatus
ReadingOperational
EditingOperational

FlareWarden checks

wikipedia.org from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
527 ms
Checked

By region

  • Ashburn reachable, 124 ms
  • Dallas reachable, 325 ms
  • Frankfurt reachable, 587 ms
  • Johannesburg reachable, 1704 ms
  • Newark reachable, 202 ms
  • Paris reachable, 409 ms
  • Stockholm reachable, 493 ms
  • São Paulo reachable, 378 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn109 ms1 ms6 ms120 ms
Dallas308 ms1 ms6 ms320 ms
Frankfurt456 ms20 ms25 ms530 ms
Johannesburg715 ms160 ms164 ms1258 ms
Newark140 ms10 ms14 ms179 ms
Paris265 ms22 ms28 ms347 ms
Stockholm359 ms20 ms28 ms436 ms
São Paulo353 ms2 ms11 ms372 ms
We check that wikipedia.org loads, not every feature behind it. Test it yourself

History

Incidents Wikipedia reported

Since Oct 22, 15 days · from wikimediastatus.net

Incidents
2
Major or critical
0
Median to resolve
2d 13h
  1. lasted 1h 45m
  2. Maintenance

    Unrated ·

    lasted 5d 1h

Wikipedia website availability

Measured by FlareWarden · wikipedia.org

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
583ms

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 30 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of wikipedia.org from multiple regions every 6 hours. Wikipedia's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Wikipedia itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Wikipedia goes down

We check Wikipedia every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required