Operational Cloudsmith status
cloudsmith.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Cloudsmith problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 47 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Intermittent Issue pushing NuGet packages”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Cloudsmith's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Cloudsmith. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Cloudsmith, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Cloudsmith may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Cloudsmith. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Intermittent Issue pushing NuGet packages
minor resolved · started · resolved
8 updates
- investigating
We're looking into an intermittent issue with pushing NuGet packages. Engineering is currently investigating
- identified
We have identified the cause of intermittent failures when pushing NuGet packages for customers in Europe (eu-west-1), affecting some package uploads since approximately 12:00 UTC on 3 October. Pulling and downloading packages is unaffected, as are all other package formats. We are rolling back the change responsible. Retrying a failed push may succeed in the meantime.
- identified
We are continuing to apply the change needed to restore normal NuGet package update for customers in Europe (eu-west-1). Pulling and downloading packages remains unaffected.
- identified
Work to restore normal NuGet package pushes for customers in Europe (eu-west-1) is still in progress. We will confirm here as soon as the service operations return to normal.
- monitoring
Between approximately 12:00 UTC on 3 October and 07:30 UTC, customers in Europe (eu-west-1) experienced intermittent failures when pushing NuGet packages. We have applied a change to the affected service and confirmed that package pushes have returned to normal. Pulling and downloading packages was unaffected throughout, as were all other package formats.
- monitoring
Most customers in Europe (eu-west-1) can now push NuGet packages normally, and we are monitoring to confirm. A small number of customers may still see intermittent push failures, and work to restore those is ongoing.
- monitoring
We are monitoring NuGet package pushes in Europe (eu-west-1) following the changes applied earlier. Pushes are completing normally for most customers, and we are continuing to verify the remaining cases.
- resolved
This incident is now resolved. Between approximately 12:00 UTC on 3 October and 07:30 UTC on 5 October, customers in Europe (eu-west-1) experienced intermittent failures when pushing NuGet packages. We have applied changes to the affected services and confirmed that package pushes have returned to normal. Pulling and downloading packages was unaffected throughout, as were all other package formats.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.