- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 17h 31m it lasted.
Anything that failed between 2026-08-25 14:09 UTC and 2026-08-26 07:40 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 2
- investigating
We are seeing a delay in advisories being populated on [OSV.dev](http://OSV.dev), the last advisory update was at 05:03 UTC. We are monitoring the feed to review the data. New Vulnerability data may be delayed.
provider
- resolved
OSV advisory processing resumed at 23:50 UTC on August 25, and advisory freshness returned to normal at 04:35 UTC on August 26. All systems are now operating normally.
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-a7bcaec193
Is Cloudsmith still down?
No, this incident was resolved 2026-08-26 07:40 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.
How long did it last?
17h 31m, from 2026-08-25 14:09 UTC to 2026-08-26 07:40 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.