Cloudsmith reported "Intermittent Issue pushing NuGet packages" on its status page at 2026-10-05 06:19 UTC.

Cloudsmith did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-05 06:19 UTC and ended at 2026-10-05 08:30 UTC. It lasted 2 h 11 min.

How do I get alerts for Cloudsmith?

Subscribe to the Cloudsmith live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cloudsmith. outages.live reads it every few minutes and keeps every update.

CloudsmithIncident · 2026-10-05 06:19 UTC

Intermittent Issue pushing NuGet packages

ResolvedOfficial update

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.

The latest update from Cloudsmith.

State

Resolved

Started

27 d ago

2026-10-05 06:19 UTC

Lasted

2 h 11 min

until 2026-10-05 08:30 UTC

Worst impact

Degraded

Timeline

8 updates

06:1906:5207:2407:5708:30

DegradedUpdate postedTimes in UTC

Investigating

7 min 5%

Identified

1 h 7 min 52%

Monitoring

56 min 43%

Updates

Times in UTC

As posted by Cloudsmith

Resolved2026-10-05 08:30 UTC

Monitoring2026-10-05 08:14 UTC

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.

Monitoring2026-10-05 07:55 UTC

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.

Monitoring2026-10-05 07:34 UTC

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.

Identified2026-10-05 07:13 UTC

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.

Identified2026-10-05 06:44 UTC

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.

Identified2026-10-05 06:26 UTC

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.

Investigating2026-10-05 06:19 UTC

We're looking into an intermittent issue with pushing NuGet packages. Engineering is currently investigating

Cloudsmith in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 28 min

This incident

1.5× 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·Service Degradation On Our Web API

This incident is now resolved. We have confirmed that the API has returned to normal operations.

Resolvedresolved 32 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