- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 55m it lasted.
Anything that failed between 2026-07-30 20:01 UTC and 2026-07-30 20:56 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 3
- investigating
We are currently investigating elevated latency for Python package downloads. Users may experience slow request times or timeouts when downloading packages. Our engineering team is actively investigating, and we'll update the status accordingly.
provider
- identified
Our engineering team has identified the cause and is working to resolve the issue.
provider
- resolved
We have confirmed that our work has returned services to normal operations.
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-b203b2f8d5
Is Cloudsmith still down?
No, this incident was resolved 2026-07-30 20:56 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.
How long did it last?
55m, from 2026-07-30 20:01 UTC to 2026-07-30 20:56 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.