Skip to main content
Cloudsmith

Request Latency and Timeout in US region

Degraded Lasted 1h 7m · started · Cloudsmith's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-east-2
Down Index
26of 100

What to do

  • Check whether you use Cloudsmith in us, us-east-2. 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 7m it lasted.

    Anything that failed between 2026-08-31 19:27 UTC and 2026-08-31 20:34 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

  1. investigating

    We have identified an issue causing request latency and timeouts in the us-east-2 region.

    provider

  2. investigating

    We are continuing to investigate the issue causing request latency and timeouts in the US East region. Our engineering team have taken mitigative actions and are monitoring their effect. Next update by 20:27 UTC.

    provider

  3. monitoring

    Following mitigative actions, we are seeing request latency and error rates return to normal levels in the US East region. We are continuing to monitor.

    provider

  4. resolved

    This incident is now resolved. Between 19:16 and 20:11 UTC, customers experienced request latency and timeouts affecting package downloads and API requests in the US East region. We have confirmed that these services have now returned 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-cde8a7a93f

Is Cloudsmith still down?

No, this incident was resolved 2026-08-31 20:34 UTC. For Cloudsmith's live state, see https://down.guide/cloudsmith.

How long did it last?

1h 7m, from 2026-08-31 19:27 UTC to 2026-08-31 20:34 UTC, by the times Cloudsmith posted.

What was affected?

Cloudsmith named in us, us-east-2.

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.