Live

Multiple services unavailable

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

2
docs.python.org - Backendsdocs.python.org - docs.python.org - Backends

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.cc/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.cc/feed.xml?providers=pypi
Slack
/feed subscribe https://outages.cc/feed.xml?providers=pypi

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane