- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Cloudsmith. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 17m it lasted.
Anything that failed between 2026-09-14 16:13 UTC and 2026-09-14 18:30 UTC may need a replay.Subscribe to Cloudsmith's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudsmith works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudsmith 4
- investigating
Policies that use upstream tags fail to evaluate correctly and block packages when Block Until Scanned is enabled. A fix is being implemented for this.
provider
- identified
The issue has been identified, and steps have been taken to mitigate it. We continue to work on a permanent fix.
provider
- identified
We have triggered a re-evaluation, and all impacted packages have been successfully quarantined. The issue is mitigated, and we continue to work on a permanent fix.
provider
- resolved
The root cause was identified and the issue is now resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-0a8e23fede
Is Cloudsmith still down?
No, this incident was resolved 2026-09-14 18:30 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.
How long did it last?
2h 17m, from 2026-09-14 16:13 UTC to 2026-09-14 18:30 UTC, by the times Cloudsmith posted.
What caused it?
Cloudsmith hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudsmith's official status page, https://status.cloudsmith.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.