Skip to content

Outage tracker / PyPI

Is PyPI down?

I'm having a problem

Vendor reports no incidentWhat PyPI reports

PyPI reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:00 UTC.

PyPI'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 moments ago

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

As of Nov 5, 2026, 3:05 PM UTC, RealUptime's checks of PyPI passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:05 PM UTC
US-East583 msChecks passing
US-West1004 msChecks passing
Europe225 msChecks passing
Asia-Pacific1764 msChecks passing
US-Central175 msChecks passing
Canada1303 msChecks passing
UK307 msChecks passing
Southeast Asia1934 msChecks passing
Australia2158 msChecks passing
South America1231 msChecks passing
their status pagetheir claim, not our reading

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

from PyPI's own status page, checked Nov 5, 2026, 1:22 PM UTC

PyPI's own component breakdown, as they publish it

  • AWS elasticache-us-east-2Operational
  • Message Handling ServicesOperational
  • docs.python.org - BackendsOperational
  • pypi.org - GeneralOperational
  • python.org - CDNOperational
  • AWS elb-us-east-2Operational
  • Fastly Asia/Pacific (HK)Operational
  • Mailing Lists and Archives - MailmanOperational
  • docs.python.org - CDNOperational
  • pypi.org - CDNOperational
  • python.org - BackendsOperational
  • speed.pypy.orgOperational
  • AWS ec2-us-east-2Operational
  • Fastly US East (IAD)Operational
  • Mailing Lists and Archives - Mailman 3Operational
  • pypi.org - BackendsOperational
  • python.org - Downloads BackendsOperational
  • AWS rds-us-east-2Operational
  • pypi.org - EmailOperational
  • Fastly US East (MIA)Operational
  • Google Cloud Platform Google Cloud StorageOperational
  • bugs.python.orgOperational
  • files.pythonhosted.org - FilesOperational
  • Fastly US Central (DEN)Operational
  • files.pythonhosted.org - RedirectsOperational
  • wiki.python.orgOperational
  • Fastly US Central (DFW)Operational
  • files.pythonhosted.org - Redirects BackendsOperational
  • psfmember.orgOperational
  • us.pycon.orgOperational
  • Fastly US West (SEA)Operational
  • Fastly US West (SJC)Operational
  • Fastly Europe (FRA)Operational
  • Fastly Europe (AMS)Operational
  • Fastly Europe (LHR)Operational
  • Fastly Asia/Pacific (SYD)Operational
  • Fastly Asia/Pacific (NZ)Operational
  • Fastly Brisbane (BNE)Operational
  • Fastly Dubai (FJR)Operational
  • Fastly Melbourne (MEL)Operational
  • Fastly Osaka (ITM)Operational
  • Fastly Perth (PER)Operational
  • Fastly Tokyo (HND)Operational
  • Fastly Tokyo (TYO)Operational
  • Fastly Wellington (WLG)Operational
  • Fastly Dublin (DUB)Operational
  • Fastly Copenhagen (CPH)Operational
  • Fastly Frankfurt (HHN)Operational
  • Fastly Helsinki (HEL)Operational
  • Fastly London (LON)Operational
  • Fastly Madrid (MAD)Operational
  • Fastly Manchester (MAN)Operational
  • Fastly Milan (MXP)Operational
  • Fastly Oslo (OSL)Operational
  • Fastly Buenos Aires (EZE)Operational
  • Fastly Bogota (BOG)Operational
  • Fastly Curitiba (CWB)Operational
  • Fastly Rio de Janeiro (GIG)Operational
  • Fastly Santiago (SCL)Operational
  • Fastly Johannesburg (JNB)Operational
  • Fastly Cape Town (CPT)Operational
  • Fastly Vancouver (YVR)Operational
  • Fastly Toronto (YYZ)Operational
  • Fastly St. Louis (STL)Operational
  • Fastly Palo Alto (PAO)Operational
  • Fastly Newark (EWR)Operational
  • Fastly New York (LGA)Operational
  • Fastly Montreal (YUL)Operational
  • Fastly Minneapolis (STP)Operational
  • Fastly Minneapolis (MSP)Operational
  • Fastly Los Angeles (BUR)Operational
  • Fastly Kansas City (MCI)Operational
  • Fastly Houston (IAH)Operational
  • Fastly Dallas (DAL)Operational
  • Fastly Columbus (CMH)Operational
  • Fastly Chicago (CHI)Operational
  • Fastly Boston (BOS)Operational
  • Fastly Atlanta (PDK)Operational
  • Fastly Atlanta (FTY)Operational
  • Fastly Ashburn (WDC)Operational
  • Fastly New Delhi (DEL)Operational
  • Fastly Mumbai (BOM)Operational
  • Fastly Chennai (MAA)Operational
  • Fastly Vienna (VIE)Operational
  • Fastly Stockholm (BMA)Operational
  • Fastly Paris (CDG)Operational
  • Fastly PurgingOperational
  • Fastly Tokyo (NRT)Operational
  • Fastly Singapore (QPG)Operational
  • Fastly Seoul (ICN)Operational
  • Fastly Manila (MNL)Operational
  • Fastly Kuala Lumpur (KUL)Operational
  • Fastly Dubai (DXB)Operational
  • Fastly Christchurch (CHC)Operational
  • Fastly Adelaide (ADL)Operational
  • Fastly Ghana (ACC)Operational
  • Fastly Sāo Paulo (CGH)Operational
  • Fastly Lima (LIM)Operational
  • Fastly Fortaleza (FOR)Operational
  • Fastly Seattle (BFI)Operational

These are PyPI's components, named and scored by PyPI. 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 PyPI'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.

PyPI response time, by region

US-East
1.1sp95 · 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-10-07 UTC: p95 578ms2026-10-08 UTC: p95 506ms2026-10-09 UTC: p95 527ms2026-10-10 UTC: p95 462ms2026-10-11 UTC: p95 634ms2026-10-12 UTC: p95 561ms2026-10-13 UTC: p95 733ms2026-10-14 UTC: p95 681ms2026-10-15 UTC: p95 721ms2026-10-16 UTC: p95 645ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.6sp95 · 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-10-07 UTC: p95 492ms2026-10-08 UTC: p95 540ms2026-10-09 UTC: p95 616ms2026-10-10 UTC: p95 582ms2026-10-11 UTC: p95 544ms2026-10-12 UTC: p95 500ms2026-10-13 UTC: p95 608ms2026-10-14 UTC: p95 682ms2026-10-15 UTC: p95 665ms2026-10-16 UTC: p95 548ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Europe
817msp95 · 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-10-07 UTC: p95 405ms2026-10-08 UTC: p95 321ms2026-10-09 UTC: p95 340ms2026-10-10 UTC: p95 382ms2026-10-11 UTC: p95 414ms2026-10-12 UTC: p95 476ms2026-10-13 UTC: p95 296ms2026-10-14 UTC: p95 202ms2026-10-15 UTC: p95 178ms2026-10-16 UTC: p95 218ms2026-10-17 UTC: p95 614ms2026-10-18 UTC: p95 818ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 843ms2026-10-21 UTC: p95 781ms2026-10-22 UTC: p95 791ms2026-10-23 UTC: p95 792ms2026-10-24 UTC: p95 655ms2026-10-25 UTC: p95 680ms2026-10-26 UTC: p95 768ms2026-10-27 UTC: p95 856ms2026-10-28 UTC: p95 730ms2026-10-29 UTC: p95 829ms2026-10-30 UTC: p95 851ms2026-10-31 UTC: p95 897ms2026-11-01 UTC: p95 990ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 681ms2026-11-04 UTC: p95 458ms2026-11-05 UTC: p95 817ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 739ms2026-10-08 UTC: p95 674ms2026-10-09 UTC: p95 752ms2026-10-10 UTC: p95 639ms2026-10-11 UTC: p95 397ms2026-10-12 UTC: p95 739ms2026-10-13 UTC: p95 561ms2026-10-14 UTC: p95 419ms2026-10-15 UTC: p95 532ms2026-10-16 UTC: p95 537ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-Central
1.5sp95 · 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-10-07 UTC: p95 246ms2026-10-08 UTC: p95 202ms2026-10-09 UTC: p95 74ms2026-10-10 UTC: p95 541ms2026-10-11 UTC: p95 552ms2026-10-12 UTC: p95 602ms2026-10-13 UTC: p95 600ms2026-10-14 UTC: p95 615ms2026-10-15 UTC: p95 677ms2026-10-16 UTC: p95 580ms2026-10-17 UTC: p95 657ms2026-10-18 UTC: p95 853ms2026-10-19 UTC: p95 880ms2026-10-20 UTC: p95 851ms2026-10-21 UTC: p95 962ms2026-10-22 UTC: p95 578ms2026-10-23 UTC: p95 627ms2026-10-24 UTC: p95 678ms2026-10-25 UTC: p95 955ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 912ms2026-10-28 UTC: p95 973ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 979ms2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Canada
1.7sp95 · 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 523ms2026-10-08 UTC: p95 436ms2026-10-09 UTC: p95 223ms2026-10-10 UTC: p95 399ms2026-10-11 UTC: p95 327ms2026-10-12 UTC: p95 344ms2026-10-13 UTC: p95 386ms2026-10-14 UTC: p95 366ms2026-10-15 UTC: p95 395ms2026-10-16 UTC: p95 467ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
UK
1.4sp95 · 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 110ms2026-10-08 UTC: p95 255ms2026-10-09 UTC: p95 275ms2026-10-10 UTC: p95 285ms2026-10-11 UTC: p95 278ms2026-10-12 UTC: p95 277ms2026-10-13 UTC: p95 174ms2026-10-14 UTC: p95 118ms2026-10-15 UTC: p95 105ms2026-10-16 UTC: p95 345ms2026-10-17 UTC: p95 971ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 916ms2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 925ms2026-10-31 UTC: p95 995ms2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · 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 537ms2026-10-08 UTC: p95 326ms2026-10-09 UTC: p95 450ms2026-10-10 UTC: p95 392ms2026-10-11 UTC: p95 348ms2026-10-12 UTC: p95 382ms2026-10-13 UTC: p95 453ms2026-10-14 UTC: p95 728ms2026-10-15 UTC: p95 469ms2026-10-16 UTC: p95 304ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Australia
2.3sp95 · 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-10-07 UTC: p95 338ms2026-10-08 UTC: p95 762ms2026-10-09 UTC: p95 315ms2026-10-10 UTC: p95 367ms2026-10-11 UTC: p95 323ms2026-10-12 UTC: p95 397ms2026-10-13 UTC: p95 322ms2026-10-14 UTC: p95 291ms2026-10-15 UTC: p95 304ms2026-10-16 UTC: p95 300ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
South America
1.6sp95 · 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 630ms2026-10-08 UTC: p95 634ms2026-10-09 UTC: p95 332ms2026-10-10 UTC: p95 281ms2026-10-11 UTC: p95 319ms2026-10-12 UTC: p95 451ms2026-10-13 UTC: p95 509ms2026-10-14 UTC: p95 734ms2026-10-15 UTC: p95 680ms2026-10-16 UTC: p95 599ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 9.2s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 20 readings for PyPI came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about PyPI's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on PyPI

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 PyPI. It cannot diagnose PyPI's own systems.

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

Get an email when PyPI reports an incident

Email me when PyPI 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 PyPI'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: 583msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach PyPI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1004msstatus code: 200checked: Nov 5, 2026, 3:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach PyPI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 175msstatus code: 200checked: Nov 5, 2026, 2:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach PyPI normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1303msstatus code: 200checked: Nov 5, 2026, 2:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach PyPI normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1231msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach PyPI 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: 225msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach PyPI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 307msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach PyPI 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: 1764msstatus code: 200checked: Nov 5, 2026, 2:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach PyPI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1934msstatus code: 200checked: Nov 5, 2026, 3:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach PyPI normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2158msstatus code: 200checked: Nov 5, 2026, 2:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach PyPI 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 PyPI, 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 PyPI yet, which is not evidence that nothing is wrong.

Recent probe events

PyPI Backends Partial Availability, 17mdeclared on their status page2026-10-02
Multiple services unavailable, 6mdeclared on their status page2026-10-01
Issues with search, logins and logged-in pages, 12h 42mdeclared on their status page2026-09-28
Issues with search, logins and logged-in pages, 6h 3mdeclared on their status page2026-09-23
Python Infrastructure Outage, 2h 47mdeclared on their status page2026-02-26
API Traffic experiencing intermittent failures, 1h 12mdeclared on their status page2026-02-19
PyPI Uploads failing, 18mdeclared on their status page2026-01-07
Slow updates to PyPI pages/API responses, 39mdeclared on their status page2025-11-12

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

We have been measuring PyPI 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 PyPI covering any window you pick, with our check readings and PyPI's own claim at the time, side by side.

Full check history for PyPI: 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

PyPI uptime by RealUptime's checksLive, from this page's own readings.
[![PyPI uptime by RealUptime's checks](https://realuptime.io/outages/pypi/badge.svg?days=30)](https://realuptime.io/outages/pypi)
<a href="https://realuptime.io/outages/pypi"><img src="https://realuptime.io/outages/pypi/badge.svg?days=30" alt="PyPI 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 PyPI down?", https://realuptime.io/outages/pypi. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://pypi.org/pypi/requests/json
secondary
https://status.python.org/

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: pypi.org

RealUptime is not affiliated with PyPI; the name identifies what we checked, and nothing here speaks for PyPI's own team. We send a single web request to PyPI from 10 regions on our own schedule and time the response. We do not see inside PyPI's systems, do not use an account or real transaction, and are not the same signal PyPI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for PyPI 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.