PyPI reported "Multiple services unavailable" on its status page at 2026-10-01 11:13 UTC.

When did the incident start and end?

It started at 2026-10-01 11:13 UTC and ended at 2026-10-01 11:18 UTC. It lasted 6 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-01 11:13 UTC

Multiple services unavailable

Q: What is affected?

PyPI lists these components: docs.python.org - Backends, docs.python.org - docs.python.org - Backends.

ResolvedOfficial update

All services are restored.

The latest update from PyPI.

State

Resolved

Started

32 d ago

2026-10-01 11:13 UTC

Lasted

6 min

until 2026-10-01 11:18 UTC

Worst impact

Notice

Timeline

2 updates

11:1311:1411:1511:1711:18

NoticeUpdate postedTimes in UTC

Monitoring

6 min 100%

Updates

Times in UTC

As posted by PyPI

Resolved2026-10-01 11:18 UTC

All services are restored.

Monitoring2026-10-01 11:13 UTC

Multiple python.org services were impacted by expiration of internal TLS certificates caused by use of APIs deprecated by a recent library update. We have resolved the issue and are monitoring as services come back online after renewing their internal certificates.

Affected components

docs.python.org - Backendsdocs.python.org - docs.python.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

97% 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·PyPI Backends Partial Availability

the maintenance is complete and everything has stabilized

Resolvedresolved 31 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