PyPI reported "PyPI Backends Partial Availability" on its status page at 2026-10-02 01:15 UTC.

PyPI lists these components: pypi.org - Backends, PyPI - pypi.org - Backends.

When did the incident start and end?

It started at 2026-10-02 01:15 UTC and ended at 2026-10-02 01:32 UTC. It lasted 17 min.

How do I get alerts for PyPI?

Subscribe to the PyPI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of PyPI. outages.live reads it every few minutes and keeps every update.

PyPIIncident · 2026-10-02 01:15 UTC

PyPI Backends Partial Availability

ResolvedOfficial update

the maintenance is complete and everything has stabilized

The latest update from PyPI.

State

Resolved

Started

31 d ago

2026-10-02 01:15 UTC

Lasted

17 min

until 2026-10-02 01:32 UTC

Worst impact

Partial outage

Timeline

2 updates

01:1501:1901:2401:2801:32

Partial outageUpdate postedTimes in UTC

Identified

17 min 100%

Updates

Times in UTC

As posted by PyPI

Resolved2026-10-02 01:32 UTC

the maintenance is complete and everything has stabilized

Identified2026-10-02 01:15 UTC

infrastructure maintenance is having a larger impact on availability of PyPI's backends than anticipated. we are working to stabilize.

Affected components

pypi.org - BackendsPyPI - pypi.org - Backends

PyPI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

3 h 10 min

This incident

91% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 h 42 min

median 3 h 10 min

90 days agoToday

Other PyPI incidents

All incidents

PyPI·Multiple services unavailable

All services are restored.

Resolvedresolved 32 d ago

PyPI·Issues with search, logins and logged-in pages

This incident has been resolved.

Resolvedresolved 34 d ago

PyPI·Issues with search, logins and logged-in pages

A fix has been implemented and the incident is closed.

Resolvedresolved 39 d ago

Follow PyPI

Your coding agent knows when PyPI is down, and tells you when a failure is theirs, not yours. You can also get PyPI incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pypi" and tell me if PyPI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=pypi

Slack

/feed subscribe https://outages.live/feed.xml?providers=pypi

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane