Skip to content

Outage tracker / PyPI

Is PyPI down?

I'm having a problem

Operationalchecked moments ago

We reached PyPI from all 10 regions we check.

As of Oct 5, 2026, 8:17 PM UTC, PyPI answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured PyPI (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:17 PM UTC
US-East248 msOperational
US-West209 msOperational
Europe905 msOperational
Asia-Pacific486 msOperational
US-Central59 msOperational
Canada172 msOperational
UK114 msOperational
Southeast Asia289 msOperational
Australia386 msOperational
South America355 msOperational
their status pagetheir claim, not our reading

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

from PyPI's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and PyPI's own status page agree: both show PyPI as reachable 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
475msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 452ms2026-09-07 UTC: p95 425ms2026-09-08 UTC: p95 433ms2026-09-09 UTC: p95 474ms2026-09-10 UTC: p95 491ms2026-09-11 UTC: p95 473ms2026-09-12 UTC: p95 491ms2026-09-13 UTC: p95 484ms2026-09-14 UTC: p95 480ms2026-09-15 UTC: p95 566ms2026-09-16 UTC: p95 597ms2026-09-17 UTC: p95 647ms2026-09-18 UTC: p95 641ms2026-09-19 UTC: p95 693ms2026-09-20 UTC: p95 592ms2026-09-21 UTC: p95 610ms2026-09-22 UTC: p95 616ms2026-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 475ms
Sep 6Sep 20Oct 5
US-West
536msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 678ms2026-09-07 UTC: p95 690ms2026-09-08 UTC: p95 672ms2026-09-09 UTC: p95 278ms2026-09-10 UTC: p95 332ms2026-09-11 UTC: p95 249ms2026-09-12 UTC: p95 215ms2026-09-13 UTC: p95 303ms2026-09-14 UTC: p95 254ms2026-09-15 UTC: p95 334ms2026-09-16 UTC: p95 331ms2026-09-17 UTC: p95 373ms2026-09-18 UTC: p95 356ms2026-09-19 UTC: p95 380ms2026-09-20 UTC: p95 382ms2026-09-21 UTC: p95 367ms2026-09-22 UTC: p95 415ms2026-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 536ms
Sep 6Sep 20Oct 5
Europe
636msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 240ms2026-09-07 UTC: p95 232ms2026-09-08 UTC: p95 242ms2026-09-09 UTC: p95 299ms2026-09-10 UTC: p95 463ms2026-09-11 UTC: p95 372ms2026-09-12 UTC: p95 411ms2026-09-13 UTC: p95 307ms2026-09-14 UTC: p95 367ms2026-09-15 UTC: p95 383ms2026-09-16 UTC: p95 521ms2026-09-17 UTC: p95 586ms2026-09-18 UTC: p95 507ms2026-09-19 UTC: p95 468ms2026-09-20 UTC: p95 446ms2026-09-21 UTC: p95 520ms2026-09-22 UTC: p95 541ms2026-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 636ms
Sep 6Sep 20Oct 5
Asia-Pacific
671msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 742ms2026-09-07 UTC: p95 928ms2026-09-08 UTC: p95 807ms2026-09-09 UTC: p95 730ms2026-09-10 UTC: p95 782ms2026-09-11 UTC: p95 831ms2026-09-12 UTC: p95 838ms2026-09-13 UTC: p95 636ms2026-09-14 UTC: p95 684ms2026-09-15 UTC: p95 719ms2026-09-16 UTC: p95 826ms2026-09-17 UTC: p95 808ms2026-09-18 UTC: p95 745ms2026-09-19 UTC: p95 778ms2026-09-20 UTC: p95 743ms2026-09-21 UTC: p95 847ms2026-09-22 UTC: p95 775ms2026-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 671ms
Sep 6Sep 20Oct 5
US-Central
257msp95 · 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-06 UTC: p95 410ms2026-09-07 UTC: p95 435ms2026-09-08 UTC: p95 421ms2026-09-09 UTC: p95 444ms2026-09-10 UTC: p95 453ms2026-09-11 UTC: p95 555ms2026-09-12 UTC: p95 470ms2026-09-13 UTC: p95 382ms2026-09-14 UTC: p95 368ms2026-09-15 UTC: p95 816ms2026-09-16 UTC: p95 387ms2026-09-17 UTC: p95 540ms2026-09-18 UTC: p95 517ms2026-09-19 UTC: p95 411ms2026-09-20 UTC: p95 413ms2026-09-21 UTC: p95 396ms2026-09-22 UTC: p95 437ms2026-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 257ms
Sep 6Sep 20Oct 5
Canada
472msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 639ms2026-09-07 UTC: p95 582ms2026-09-08 UTC: p95 422ms2026-09-09 UTC: p95 428ms2026-09-10 UTC: p95 458ms2026-09-11 UTC: p95 548ms2026-09-12 UTC: p95 467ms2026-09-13 UTC: p95 444ms2026-09-14 UTC: p95 505ms2026-09-15 UTC: p95 524ms2026-09-16 UTC: p95 514ms2026-09-17 UTC: p95 554ms2026-09-18 UTC: p95 566ms2026-09-19 UTC: p95 529ms2026-09-20 UTC: p95 540ms2026-09-21 UTC: p95 529ms2026-09-22 UTC: p95 563ms2026-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 472ms
Sep 6Sep 20Oct 5
UK
231msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 234ms2026-09-07 UTC: p95 312ms2026-09-08 UTC: p95 297ms2026-09-09 UTC: p95 398ms2026-09-10 UTC: p95 217ms2026-09-11 UTC: p95 167ms2026-09-12 UTC: p95 151ms2026-09-13 UTC: p95 196ms2026-09-14 UTC: p95 140ms2026-09-15 UTC: p95 168ms2026-09-16 UTC: p95 206ms2026-09-17 UTC: p95 258ms2026-09-18 UTC: p95 207ms2026-09-19 UTC: p95 275ms2026-09-20 UTC: p95 224ms2026-09-21 UTC: p95 303ms2026-09-22 UTC: p95 256ms2026-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 231ms
Sep 6Sep 20Oct 5
Southeast Asia
412msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 892ms2026-09-07 UTC: p95 584ms2026-09-08 UTC: p95 642ms2026-09-09 UTC: p95 719ms2026-09-10 UTC: p95 730ms2026-09-11 UTC: p95 790ms2026-09-12 UTC: p95 762ms2026-09-13 UTC: p95 664ms2026-09-14 UTC: p95 318ms2026-09-15 UTC: p95 419ms2026-09-16 UTC: p95 394ms2026-09-17 UTC: p95 414ms2026-09-18 UTC: p95 576ms2026-09-19 UTC: p95 597ms2026-09-20 UTC: p95 544ms2026-09-21 UTC: p95 809ms2026-09-22 UTC: p95 1.2s2026-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 412ms
Sep 6Sep 20Oct 5
Australia
415msp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 929ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 992ms2026-09-16 UTC: p95 946ms2026-09-17 UTC: p95 973ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.3s2026-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 415ms
Sep 6Sep 20Oct 5
South America
631msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 368ms2026-09-07 UTC: p95 333ms2026-09-08 UTC: p95 332ms2026-09-09 UTC: p95 338ms2026-09-10 UTC: p95 270ms2026-09-11 UTC: p95 385ms2026-09-12 UTC: p95 458ms2026-09-13 UTC: p95 572ms2026-09-14 UTC: p95 579ms2026-09-15 UTC: p95 715ms2026-09-16 UTC: p95 565ms2026-09-17 UTC: p95 656ms2026-09-18 UTC: p95 606ms2026-09-19 UTC: p95 619ms2026-09-20 UTC: p95 480ms2026-09-21 UTC: p95 389ms2026-09-22 UTC: p95 471ms2026-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 631ms
Sep 6Sep 20Oct 5

Is it PyPI, or is it you?

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.

Get an email when we see PyPI go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching PyPI, and again when they can reach it again. That is our own measurement from ten regions, not PyPI's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 248msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 209msstatus code: 200checked: Oct 5, 2026, 8:13 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
      Operationallatency: 59msstatus code: 200checked: Oct 5, 2026, 8:07 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
      Operationallatency: 172msstatus code: 200checked: Oct 5, 2026, 8:09 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
    Operationallatency: 355msstatus code: 200checked: Oct 5, 2026, 8:12 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 905msstatus code: 200checked: Oct 5, 2026, 8:09 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
      Operationallatency: 114msstatus code: 200checked: Oct 5, 2026, 8:13 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 486msstatus code: 200checked: Oct 5, 2026, 8:10 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
      Operationallatency: 289msstatus code: 200checked: Oct 5, 2026, 8:11 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
      Operationallatency: 386msstatus code: 200checked: Oct 5, 2026, 8:17 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 outages

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

measured 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 measurements and PyPI's own claim at the time, side by side.

Full availability history for PyPI: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![PyPI uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What PyPI's SLA implies, from our measurement

At or above your target

We measured none of downtime for PyPI over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from PyPI's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://pypi.org/pypi/requests/json
secondary
https://status.python.org/
RealUptime is not affiliated with PyPI; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.