PyPI
PyPI is operational
Checked 2 min ago Operational
History
90 days agoToday
Incidents in 90 days
4
Days with an incident
5
Median duration
3 h 10 min
Longest incident
12 h 42 min
Components
122python.org
python.org - CDN Operational
90 days agoNo incidentsToday
python.org - Backends Operational
90 days agoNo incidentsToday
python.org - Downloads Backends Operational
90 days agoNo incidentsToday
mail.python.org
Message Handling Services Operational
90 days agoNo incidentsToday
Mailing Lists and Archives - Mailman Operational
90 days agoNo incidentsToday
Mailing Lists and Archives - Mailman 3 Operational
90 days agoNo incidentsToday
docs.python.org
docs.python.org - Backends Operational
90 days ago1 day with an incidentToday
docs.python.org - CDN Operational
90 days agoNo incidentsToday
PyPI Hosting Platforms
AWS elasticache-us-east-2 Operational
90 days agoNo incidentsToday
AWS elb-us-east-2 Operational
90 days agoNo incidentsToday
AWS ec2-us-east-2 Operational
90 days agoNo incidentsToday
AWS rds-us-east-2 Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Cloud Storage Operational
90 days agoNo incidentsToday
PyPI
pypi.org - General Operational
90 days ago3 days with an incidentToday
pypi.org - CDN Operational
90 days agoNo incidentsToday
pypi.org - Backends Operational
90 days ago4 days with an incidentToday
pypi.org - Email Operational
90 days agoNo incidentsToday
files.pythonhosted.org - Files Operational
90 days agoNo incidentsToday
files.pythonhosted.org - Redirects Operational
90 days agoNo incidentsToday
files.pythonhosted.org - Redirects Backends Operational
90 days agoNo incidentsToday
PyPy
speed.pypy.org Operational
90 days agoNo incidentsToday
Content Delivery Network
Fastly Asia/Pacific (HK) Operational
90 days agoNo incidentsToday
Fastly US East (IAD) Operational
90 days agoNo incidentsToday
Fastly US East (MIA) Operational
90 days agoNo incidentsToday
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=pypiGo from tracking outages to fixing production issues with Polylane.
Try Polylane