Skip to main content
PyPI

PyPI Elevated Error Rates

Partial outage Lasted 16m · started · PyPI's page

Level
confirmed
Worst impact
Partial outage
Components
pypi.org - Backends
Down Index
24of 100

What to do

  • Check whether you use PyPI pypi.org - Backends. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 16m it lasted.

    Anything that failed between 2025-04-24 12:02 UTC and 2025-04-24 12:18 UTC may need a replay.
  • Subscribe to PyPI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=pypi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from PyPI 4

  1. investigating

    We're investigating elevated error rates for pypi.org

    provider

  2. identified

    We've identified an issue with database contention arising from locking.

    provider

  3. monitoring

    The locking process has been terminated and we're monitoring as things recover.

    provider

  4. resolved

    This incident is resolved. We're going to do some further investigation to understand what led to the lock contention.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7810123fe3

Is PyPI still down?

No, this incident was resolved 2025-04-24 12:18 UTC. For PyPI's live state, see https://down.guide/pypi.

How long did it last?

16m, from 2025-04-24 12:02 UTC to 2025-04-24 12:18 UTC, by the times PyPI posted.

What was affected?

PyPI named pypi.org - Backends.

What caused it?

PyPI hasn't published a root cause. If it does, it shows here.

Where does this come from?

PyPI's official status page, https://status.python.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.