- 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 1h 44m it lasted.
Anything that failed between 2026-08-05 16:26 UTC and 2026-08-05 18:11 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 investigating reports of intermittent 500 errors affecting API and web requests across all regions, starting from approximately 17:14 UTC and finishing at 17:15 UTC (Approx 31 seconds impact), related to Database connection exhaustion. We detected a small number of errors across millions of successful requests in the window. The team is investigating the cause
provider
- investigating
Impact has been confirmed as ended. The engineering team is investigating & monitoring.
provider
- resolved
No further impact to API or Web applications outside of the 1 minute window
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-49ba2a23eb
Is Cloudsmith still down?
No, this incident was resolved 2026-08-05 18:11 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.
How long did it last?
1h 44m, from 2026-08-05 16:26 UTC to 2026-08-05 18:11 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.