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-10-22 18:58 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 2 minutes ago

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

As of Oct 22, 2026, 7:04 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 Oct 22, 2026, 7:04 PM UTC
US-East1029 msChecks passing
US-West1070 msChecks passing
Europe809 msChecks passing
Asia-Pacific1345 msChecks passing
US-Central413 msChecks passing
Canada1153 msChecks passing
UK956 msChecks passing
Southeast Asia1373 msChecks passing
Australia896 msChecks passing
South America1458 msChecks passing
their status pagetheir claim, not our reading

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

from PyPI's own status page, checked Oct 22, 2026, 7:02 PM UTC
PyPI's own status page shows no incident, and our checks of PyPI pass right now.

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.5sp95 · 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-23 UTC: p95 596ms2026-09-24 UTC: p95 128ms2026-09-25 UTC: p95 346ms2026-09-26 UTC: p95 219ms2026-09-27 UTC: p95 222ms2026-09-28 UTC: p95 363ms2026-09-29 UTC: p95 542ms2026-09-30 UTC: p95 489ms2026-10-01 UTC: p95 581ms2026-10-02 UTC: p95 568ms2026-10-03 UTC: p95 803ms2026-10-04 UTC: p95 559ms2026-10-05 UTC: p95 507ms2026-10-06 UTC: p95 476ms2026-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.5s
Sep 23Oct 7Oct 22
US-West
1.7sp95 · 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-23 UTC: p95 402ms2026-09-24 UTC: p95 337ms2026-09-25 UTC: p95 320ms2026-09-26 UTC: p95 299ms2026-09-27 UTC: p95 538ms2026-09-28 UTC: p95 470ms2026-09-29 UTC: p95 532ms2026-09-30 UTC: p95 517ms2026-10-01 UTC: p95 555ms2026-10-02 UTC: p95 284ms2026-10-03 UTC: p95 383ms2026-10-04 UTC: p95 524ms2026-10-05 UTC: p95 549ms2026-10-06 UTC: p95 435ms2026-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.7s
Sep 23Oct 7Oct 22
Europe
740msp95 · 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-23 UTC: p95 382ms2026-09-24 UTC: p95 96ms2026-09-25 UTC: p95 140ms2026-09-26 UTC: p95 213ms2026-09-27 UTC: p95 154ms2026-09-28 UTC: p95 395ms2026-09-29 UTC: p95 62ms2026-09-30 UTC: p95 172ms2026-10-01 UTC: p95 210ms2026-10-02 UTC: p95 40ms2026-10-03 UTC: p95 186ms2026-10-04 UTC: p95 336ms2026-10-05 UTC: p95 636ms2026-10-06 UTC: p95 629ms2026-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 740ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.8sp95 · 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-09-23 UTC: p95 757ms2026-09-24 UTC: p95 556ms2026-09-25 UTC: p95 430ms2026-09-26 UTC: p95 461ms2026-09-27 UTC: p95 697ms2026-09-28 UTC: p95 554ms2026-09-29 UTC: p95 841ms2026-09-30 UTC: p95 947ms2026-10-01 UTC: p95 697ms2026-10-02 UTC: p95 682ms2026-10-03 UTC: p95 585ms2026-10-04 UTC: p95 701ms2026-10-05 UTC: p95 673ms2026-10-06 UTC: p95 734ms2026-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.8s
Sep 23Oct 7Oct 22
US-Central
585msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 392ms2026-09-24 UTC: p95 34ms2026-09-25 UTC: p95 191ms2026-09-26 UTC: p95 319ms2026-09-27 UTC: p95 419ms2026-09-28 UTC: p95 444ms2026-09-29 UTC: p95 237ms2026-09-30 UTC: p95 307ms2026-10-01 UTC: p95 265ms2026-10-02 UTC: p95 247ms2026-10-03 UTC: p95 274ms2026-10-04 UTC: p95 250ms2026-10-05 UTC: p95 248ms2026-10-06 UTC: p95 247ms2026-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 585ms
Sep 23Oct 7Oct 22
Canada
1.5sp95 · 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-23 UTC: p95 468ms2026-09-24 UTC: p95 275ms2026-09-25 UTC: p95 255ms2026-09-26 UTC: p95 135ms2026-09-27 UTC: p95 349ms2026-09-28 UTC: p95 425ms2026-09-29 UTC: p95 291ms2026-09-30 UTC: p95 327ms2026-10-01 UTC: p95 310ms2026-10-02 UTC: p95 336ms2026-10-03 UTC: p95 326ms2026-10-04 UTC: p95 453ms2026-10-05 UTC: p95 471ms2026-10-06 UTC: p95 396ms2026-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.5s
Sep 23Oct 7Oct 22
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-09-23 UTC: p95 253ms2026-09-24 UTC: p95 195ms2026-09-25 UTC: p95 174ms2026-09-26 UTC: p95 111ms2026-09-27 UTC: p95 71ms2026-09-28 UTC: p95 236ms2026-09-29 UTC: p95 294ms2026-09-30 UTC: p95 404ms2026-10-01 UTC: p95 712ms2026-10-02 UTC: p95 156ms2026-10-03 UTC: p95 81ms2026-10-04 UTC: p95 201ms2026-10-05 UTC: p95 230ms2026-10-06 UTC: p95 159ms2026-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.3s
Sep 23Oct 7Oct 22
Southeast Asia
2.5sp95 · 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-23 UTC: p95 932ms2026-09-24 UTC: p95 273ms2026-09-25 UTC: p95 630ms2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 463ms2026-09-30 UTC: p95 328ms2026-10-01 UTC: p95 392ms2026-10-02 UTC: p95 287ms2026-10-03 UTC: p95 356ms2026-10-04 UTC: p95 417ms2026-10-05 UTC: p95 401ms2026-10-06 UTC: p95 280ms2026-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.5s
Sep 23Oct 7Oct 22
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 225ms2026-09-25 UTC: p95 381ms2026-09-26 UTC: p95 851ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 924ms2026-09-29 UTC: p95 294ms2026-09-30 UTC: p95 349ms2026-10-01 UTC: p95 272ms2026-10-02 UTC: p95 136ms2026-10-03 UTC: p95 155ms2026-10-04 UTC: p95 547ms2026-10-05 UTC: p95 409ms2026-10-06 UTC: p95 351ms2026-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.1s
Sep 23Oct 7Oct 22
South America
2.0sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 541ms2026-09-24 UTC: p95 657ms2026-09-25 UTC: p95 575ms2026-09-26 UTC: p95 615ms2026-09-27 UTC: p95 750ms2026-09-28 UTC: p95 711ms2026-09-29 UTC: p95 526ms2026-09-30 UTC: p95 410ms2026-10-01 UTC: p95 481ms2026-10-02 UTC: p95 612ms2026-10-03 UTC: p95 800ms2026-10-04 UTC: p95 878ms2026-10-05 UTC: p95 633ms2026-10-06 UTC: p95 535ms2026-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.0s
Sep 23Oct 7Oct 22

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: 1029msstatus code: 200checked: Oct 22, 2026, 7: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: 1070msstatus code: 200checked: Oct 22, 2026, 6:57 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: 413msstatus code: 200checked: Oct 22, 2026, 6:49 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: 1153msstatus code: 200checked: Oct 22, 2026, 7:02 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: 1458msstatus code: 200checked: Oct 22, 2026, 6:59 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: 809msstatus code: 200checked: Oct 22, 2026, 7:00 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: 956msstatus code: 200checked: Oct 22, 2026, 6:47 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: 1345msstatus code: 200checked: Oct 22, 2026, 7:04 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: 1373msstatus code: 200checked: Oct 22, 2026, 7:01 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: 896msstatus code: 200checked: Oct 22, 2026, 7:01 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

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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.