- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, eu-west-1
- Down Index
- 16of 100
What to do
Check whether you use Cloudsmith in eu, eu-west-1. 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 0m it lasted.
Anything that failed between 2026-07-14 10:26 UTC and 2026-07-14 07:35 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
- monitoring
We experienced minor service degradation in eu-west-1 between 1:15am and 7:25am UTC. During this time, some customers may have experienced elevated error rates when using the web application, API, or downloading packages. Our engineers identified the root cause and implemented a mitigation. Services have recovered and we are continuing to monitor the platform to ensure stability.
provider
- resolved
Services have recovered and we are continuing to monitor the platform to ensure stability.
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-e183308c58
Is Cloudsmith still down?
No, this incident was resolved 2026-07-14 07:35 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.
How long did it last?
0m, from 2026-07-14 10:26 UTC to 2026-07-14 07:35 UTC, by the times Cloudsmith posted.
What was affected?
Cloudsmith named in eu, eu-west-1.
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.