outages.live
Live
CloudsmithIncident ·

Increase in 503 errors for NPM requests

ResolvedOfficial update
0

Cloudsmith reported an increase in 503 errors for NPM requests. Cloudsmith identified and mitigated the issue, then monitored it. The issue is resolved, and it lasted about 32 minutes.

State

Resolved

Started

Lasted

32 min

Worst impact

Degraded

Timeline

2 updates
15:2715:3515:4215:5015:58
DegradedUpdate postedTimes in UTC

Monitoring

32 min 100%

Updates

Times in UTC

As posted by Cloudsmith

Resolved

This issue has now been resolved.

Monitoring

Users may have experienced 503 errors between 14:33 and 14:43 on 9th November 2026. Our Engineering team identified and mitigated the issue. We are continuing to monitor.

Cloudsmith in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

17

Median duration

1 h 10 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 10 min
90 days agoToday

Other Cloudsmith incidents

All incidents

Cloudsmith·Experiencing 502/504 errors for Maven uploads

This issue has now been resolved.

Resolved

Cloudsmith·Intermittent 500 errors on Package Downloads

All services are operating normally

Resolved

Cloudsmith·Issues with package downloads

We have deployed the fix and confirmed resolution

Resolved

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.

Resolved

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.

Resolved

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.live/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.live/feed.xml?providers=cloudsmith
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudsmith

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane