outages.live
Live
CloudsmithIncident · 2026-08-21 18:15 UTC

New upstream packages may not appear in repositories

ResolvedOfficial update

The issue has now been resolved, and package caching to the repositories has resumed. Packages pulled between **17:00 and 18:45 UTC** will be missing from the repositories. These missing packages will be cached during subsequent pulls. **Note:** Package caching to the repositories was impacted. Package pulls remained unaffected throughout the incident. Webhooks subscribed to the **Package Downloaded** event were also impacted during this period, and missed events will not be replayed.

The latest update from Cloudsmith.

State

Resolved

Started

72 d ago

2026-08-21 18:15 UTC

Lasted

39 min

until 2026-08-21 18:54 UTC

Worst impact

Partial outage

Timeline

4 updates
18:1518:2518:3518:4518:54
Partial outageUpdate postedTimes in UTC

Investigating

24 min 62%

Identified

15 min 38%

Updates

Times in UTC

As posted by Cloudsmith

Resolved2026-08-21 18:54 UTC

The issue has now been resolved, and package caching to the repositories has resumed. Packages pulled between **17:00 and 18:45 UTC** will be missing from the repositories. These missing packages will be cached during subsequent pulls. **Note:** Package caching to the repositories was impacted. Package pulls remained unaffected throughout the incident. Webhooks subscribed to the **Package Downloaded** event were also impacted during this period, and missed events will not be replayed.

Identified2026-08-21 18:40 UTC

We have identified the cause of new upstream packages not appearing in repositories globally and are applying a fix to restore package syncing. We will post our next update by 19:08 UTC.

Investigating2026-08-21 18:30 UTC

We are continuing to investigate reports of new upstream packages not appearing in repositories globally. There is no material change since our last update. We will post our next update by 19:00 UTC. Please note that the packages caching and webhooks subscribed to **Package Downloaded** event are impacted. Packages pull was not impacted.

Investigating2026-08-21 18:15 UTC

We are investigating reports of new upstream packages not appearing in repositories, starting from approximately 17:00 UTC. We will post our next update by 18:30 UTC.

Cloudsmith in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

18

Median duration

1 h 28 min

This incident

55% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

17 h 31 min
median 1 h 28 min
90 days agoToday

Other Cloudsmith incidents

All incidents

Cloudsmith·Experiencing 502/504 errors for Maven uploads

This issue has now been resolved.

Resolvedresolved 6 d ago

Cloudsmith·Intermittent 500 errors on Package Downloads

All services are operating normally

Resolvedresolved 12 d ago

Cloudsmith·Issues with package downloads

We have deployed the fix and confirmed resolution

Resolvedresolved 19 d ago

Cloudsmith·Intermittent 503 Errors on Download Requests

This incident is now resolved. Between 14:40 UTC and 18:53 UTC on 12 October 2026, some users may have experienced intermittent HTTP 503 errors affecting package downloads. We have applied a fix, and after monitoring, we confirmed normal operation for download requests.

Resolvedresolved 20 d ago

Cloudsmith·Intermittent Issue pushing NuGet packages

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.

Resolvedresolved 27 d ago

Follow Cloudsmith

Your coding agent knows when Cloudsmith is down, and tells you when a failure is theirs, not yours. You can also get Cloudsmith incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudsmith" and tell me if Cloudsmith has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=cloudsmith
Slack
/feed subscribe https://outages.cc/feed.xml?providers=cloudsmith

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane