Cloudsmith incident

High CPU load on our writer database

Minor Resolved View vendor source →
Started
Feb 03, 2026, 11:16 AM UTC
Resolved
Feb 03, 2026, 11:16 AM UTC
Duration
Detected by Pingoru
Feb 03, 2026, 11:16 AM UTC

Affected components

Package Uploads

Update timeline

  1. investigating Feb 03, 2026, 09:35 AM UTC

    Status: Investigating We are investigating an intermittent issue causing a very small percentage of package upload failures. Enterprise Policy Manager (EPM) decision logs also remain delayed due to elevated database load. All other core services, including package downloads, are functioning as normal. Affected components Package Uploads (Degraded performance)

  2. monitoring Feb 03, 2026, 10:26 AM UTC

    Status: Monitoring System performance and package uploads have returned to normal, though we are continuing to investigate the root cause. While a small number of policy evaluations experienced intermittent failures between 08:07 and 09:51 UTC, all other core services remain stable. Enterprise Policy Manager (EPM) decision logs are currently delayed by approximately 6 hours as the backlog is processed. Affected components Package Uploads (Operational)

  3. resolved Feb 03, 2026, 11:16 AM UTC

    Status: Resolved All systems have returned to normal. We are now monitoring the Enterprise Policy Manager (EPM) decision log backlog Affected components Package Uploads (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