Cloudsmith incident
New upstream packages may not appear in repositories
Cloudsmith experienced a minor incident on August 21, 2026 affecting Upstreams, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 21, 2026, 06:15 PM UTC
Status: Investigating We are investigating reports of new upstream packages not appearing in repositories, starting from approximately 17:00 UTC. We will post our next update by 18:30 UTC. Affected components Upstreams (Partial outage)
- investigating Aug 21, 2026, 06:30 PM UTC
Status: Investigating We are continuing to investigate reports of new upstream packages not appearing in repositories globally. There is no material change since our last update. We will post our next update by 19:00 UTC. Affected components Upstreams (Partial outage)
- identified Aug 21, 2026, 06:40 PM UTC
Status: Identified We have identified the cause of new upstream packages not appearing in repositories globally and are applying a fix to restore package syncing. We will post our next update by 19:08 UTC. Affected components Upstreams (Partial outage)
- resolved Aug 21, 2026, 06:54 PM UTC
Status: Resolved The issue is now resolved. The packages have started caching again. The packages pulled during 17:00 to 18:45 UTC would be missing from the repositories. The missing packages will get cached in the consecutive pulls. NOTE: Only caching of packages to the repository was impacted. Package pulls remained unaffected during the duration of the incident. Affected components Upstreams (Operational)