Cloudsmith incident

404s on Python Metadata URLs

Minor Resolved View vendor source →
Started
May 01, 2026, 04:33 PM UTC
Resolved
May 01, 2026, 04:33 PM UTC
Duration
Detected by Pingoru
May 01, 2026, 04:33 PM UTC

Affected components

Package Downloads

Update timeline

  1. monitoring May 01, 2026, 04:31 PM UTC

    Status: Monitoring On Friday May 1st 2026, Cloudsmith introduced PEP 658-compliant metadata to Python indexes. Packages uploaded prior to this functionality being introduced (excluding upstream packages) were unable to have this metadata fetched. Package downloads themselves remained unaffected. However, Python-native clients such as uv and newer versions of pip treat metadata fetch failures as general failures, and refused to download the affected artifacts. Upstream fetches, non-wheel artifacts, and newly uploaded wheels were unaffected. For affected packages, the result was failed Python installs. We've now removed these metadata URLs from Python indexes while we backfill the data for packages that were missing it. Affected installs should now succeed on retry. We sincerely apologize for the disruption. Affected components Package Downloads (Partial outage)

  2. resolved May 01, 2026, 04:33 PM UTC

    Status: Resolved This issue has now been resolved. Affected components Package Downloads (Operational)

Looking to track Cloudsmith downtime and outages?

Pingoru polls Cloudsmith's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cloudsmith reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cloudsmith alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cloudsmith for free

5 free monitors · No credit card required