Cloudsmith reports normal operation on its official status page.

How often does Cloudsmith have incidents?

Cloudsmith reported 18 incidents in the last 90 days, on 18 different days.

Cloudsmith

Cloudsmith is operational

Checked 56 s ago Operational

History

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 28 min

Longest incident

17 h 31 min

Components

Package Uploads Operational

90 days agoNo incidentsToday

Package Sync Operational

90 days agoNo incidentsToday

Package Downloads Operational

90 days agoNo incidentsToday

REST API (api.cloudsmith.io) Operational

90 days agoNo incidentsToday

Upstreams Operational

90 days agoNo incidentsToday

Security Scanning Operational

90 days agoNo incidentsToday

Policy Management Operational

90 days agoNo incidentsToday

Continuous Risk Detection(OSV) Operational

90 days agoNo incidentsToday

Block Until Scanned (Early Access) Operational

90 days agoNo incidentsToday

Cloudsmith Web App (app.cloudsmith.com) Operational

90 days agoNo incidentsToday

Legacy Web App (cloudsmith.io) Operational

90 days agoNo incidentsToday

Broadcasts (broadcast.cloudsmith.com) Operational

90 days agoNo incidentsToday

Webhooks Operational

90 days agoNo incidentsToday

Audit and Client Log Exports Operational

90 days agoNo incidentsToday

Datadog Operational

90 days agoNo incidentsToday

OpenID Connect Operational

90 days agoNo incidentsToday

Help & Documentation (docs.cloudsmith.com) Operational

90 days agoNo incidentsToday

Blog (cloudsmith.com/blog) Operational

90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration1 h 10 min14:22 to 15:32Experiencing 502/504 errors for Maven uploadsDegraded

This issue has now been resolved.status.cloudsmith.io

Oct 20, 2026

Duration3 min12:02 to 12:05Intermittent 500 errors on Package DownloadsDegraded

All services are operating normallystatus.cloudsmith.io

Oct 13, 2026

Duration1 h 8 min16:39 to 17:47Issues with package downloadsPartial outage

We have deployed the fix and confirmed resolutionstatus.cloudsmith.io

Oct 12, 2026

Duration46 min18:39 to 19:25Intermittent 503 Errors on Download RequestsDegraded

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.status.cloudsmith.io

Oct 5, 2026

Duration2 h 11 min06:19 to 08:30Intermittent Issue pushing NuGet packagesDegraded

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.status.cloudsmith.io

Sep 30, 2026

Duration1 h 25 min16:02 to 17:26Service Degradation On Our Web APIDegraded

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

Sep 28, 2026

Duration33 min16:55 to 17:28Issues Pulling Docker ImagesPartial outage

We have resolved the issue with pulling Docker imagesstatus.cloudsmith.io

Sep 23, 2026

Duration3 h 21 min08:18 to 11:40Increase in latency for OIDC requestsDegraded

We have now release a fix to resolve this issue. Our OIDC service is operating normallystatus.cloudsmith.io

Sep 22, 2026

Duration33 min11:13 to 11:46Package synchronization delaysDegraded

The root cause was identified, and the issue is now resolved.status.cloudsmith.io

Sep 14, 2026

Duration2 h 17 min16:13 to 18:30Policies with upstream tags are not blocking packages when Block Until Scanned is enabled.Degraded

The root cause was identified and the issue is now resolved.status.cloudsmith.io

Sep 8, 2026

Duration4 h 50 min14:14 to 19:03OSV vulnerability data delays.Degraded

OSV advisory backlog processing has completed, and returned to normal processing at 07:00 PM UTC. All systems are now operating normally.status.cloudsmith.io

Aug 31, 2026

Duration1 h 7 min19:27 to 20:34Request Latency and Timeout in US regionDegraded

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.status.cloudsmith.io

Maintenance

STATUS PAGE MIGRATION NOTICE - ACTION REQUIRED

We are migrating our status page from Atlassian to incident.io to improve. incident management and communication. ⚠️ IMPORTANT ACTION REQUIRED BY APRIL 24, 2025 ⚠️ To continue receiving notifications - any existing alerts, subscriptions, or automation tied to our current status page should be updated before April 24th, 2025. New Status Page: https://status.cloudsmith.com After April 24, 2025, https://status.cloudsmith.io will redirect to the new URL. ---------------------- WHAT THIS MEANS FOR YOU ---------------------- - If you are not currently receiving status notifications: Sign up to receive notifications. - If you currently receive status notifications: See below for set-up instructions. --------------------------------- MIGRATING YOUR SUBSCRIPTION CONFIG --------------------------------- Slack: - Action Required: Configuration Change - Instructions: Use the slash command: /feed subscribe https://status.cloudsmith.com/slack.rss RSS: - Action Required: Configuration Change - Instru

Maintenanceupdated 235 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.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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane