Issues with search, logins and logged-in pages
ResolvedOfficial update
This incident has been resolved.
The latest update from PyPI.
State
Resolved
Started
35 d ago
2026-09-28 12:42 UTC
Lasted
12 h 42 min
until 2026-09-29 01:24 UTC
Worst impact
Degraded
Timeline
4 updates12:4215:5319:0322:1401:24
DegradedUpdate postedTimes in UTC
Investigating
1 h 6 min 9%
Monitoring
11 h 36 min 91%
Updates
Times in UTCAs posted by PyPI
Resolved2026-09-29 01:24 UTC
This incident has been resolved.
Monitoring2026-09-28 13:48 UTC
We have resolved the issue and are monitoring for changes.
Investigating2026-09-28 13:47 UTC
We are continuing to investigate this issue.
Investigating2026-09-28 12:42 UTC
We are currently investigating this issue.
Affected components
4pypi.org - Generalpypi.org - BackendsPyPI - pypi.org - GeneralPyPI - pypi.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=pypiSlack
/feed subscribe https://outages.cc/feed.xml?providers=pypiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane