Cloudsmith outage history

We’re seeing an increase in 502/504 errors against Maven upload requests. Our engineers are investigating.

We have deployed a fix and are actively monitoring results.

This issue has now been resolved.

We are implementing a fix for intermittent 500 errors on package downloads that occurred between 22:20 & 22:27 UTC on 19th October 2026. Impact is not ongoing, and we have resumed normal service operations

All services are operating normally

We are investigating an issue causing 404s for downloads of 'pre-release' package versions

We are investigating an issue causing 404s for downloads of 'pre-release' package versions We have identified the issue and are deploying a fix.

We have released a fix for this issue and are working through backfilling a few outstanding packages

We have deployed the fix and confirmed resolution

We are investigating intermittent HTTP 503 errors on package download requests, beginning at approximately 14:40 UTC on 12 October 2026. We will provide an update within 30 minutes.

We are continuing to investigate intermittent HTTP 503 errors on package download requests. We will provide another update within 30 minutes.

Our Engineering team has identified the issue with HTTP 503 errors affecting download requests and has applied a fix. We will continue to monitor the situation and provide updates accordingly.

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.

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

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.

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.

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.

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.

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.

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.

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.

We're experiencing intermittent 504s on our API in the US region, Our engineering team is currently investigating

We're experiencing intermittent 504s on our API in the US region, Our engineering team is releasing a fix, and we'll provide further updates shortly.

We have identified the issue causing 504's intermittently on our API. Our Engineering team has released a fix, and we are continuing to monitor performance. We'll provide updates accordingly.

We have identified the issue causing intermittent 504s on our API. Our Engineering team has released a fix, and we are continuing to monitor performance. We'll provide updates accordingly.

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

We have identified an issue impacting customers' ability to push and pull Docker images. Our engineering team is working on resolving the issue.

We have identified an issue impacting customers' ability to push and pull Docker images. Our Engineering team has released a fix, and we are continuing to monitor performance

We have resolved the issue with pulling Docker images

The engineering team is investigating increased latency for requests to our OIDC service; no impact is currently observed.

The engineering team is investigating increased latency for requests to our OIDC service; we've determined a potential cause and are working on a fix

We have identified the issue, and a fix has been deployed. We are monitoring the issue.

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

We experienced a delay in package synchronisation. Mitigation steps have been taken and we are monitoring.

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

Policies that use upstream tags fail to evaluate correctly and block packages when Block Until Scanned is enabled. A fix is being implemented for this.

The issue has been identified, and steps have been taken to mitigate it. We continue to work on a permanent fix.

We have triggered a re-evaluation, and all impacted packages have been successfully quarantined. The issue is mitigated, and we continue to work on a permanent fix.

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

We are experiencing delays in OSV vulnerability data. New advisories may take longer to appear against affected packages and trigger policy evaluation. Our engineers are investigating.

We continue to experience delays in OSV vulnerability data. New advisories may take longer to appear against affected packages and trigger policy evaluation. Our engineers are investigating

We've made some configuration changes to help process the backlog of OSV vulnerability data. New advisories may take longer to appear against affected packages and trigger policy evaluation. Our engineers are currently monitoring the backlog.

Following the configuration changes, we're seeing improvement in processing the backlog of OSV vulnerability data. New advisories may still take longer than usual to appear against affected packages and trigger policy evaluation while the backlog clears. Our engineers are continuing to monitor progress.

We're seeing improvement in processing the backlog of OSV vulnerability data. Please note that the new advisories may still take longer than usual to appear against affected packages and trigger policy evaluation while the backlog clears. Our engineers are continuing to monitor progress. Next update at 07:00 PM UTC.

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

We have identified an issue causing request latency and timeouts in the us-east-2 region.

We are continuing to investigate the issue causing request latency and timeouts in the US East region. Our engineering team have taken mitigative actions and are monitoring their effect. Next update by 20:27 UTC.

Following mitigative actions, we are seeing request latency and error rates return to normal levels in the US East region. We are continuing to monitor.

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.

We are currently investigating a delay in policy evaluations. As a result, some vulnerability data in the UI may be delayed.

We've identified the cause of the delay in policy evaluations and are working on a fix. Some vulnerability data in the UI may remain delayed.

We're continuing to work on a fix for the delay in policy evaluations. Some vulnerability data in the UI may remain delayed in the meantime.

Normal operation has been restored. We will continue to monitor.

We have confirmed that all services are operating as normal.

We have identified an issue causing request latency and timeouts affecting metadata requests and package downloads.

We have taken steps to mitigate customer impact, but continue to see latency and timeouts affecting metadata and package download requests. Next update by 17:30 UTC.

We have returned to normal operations, but will continue to monitor.

Between 16:04 and 17:13 UTC, customers experienced latency and timeouts affecting metadata and package download requests. We have confirmed normal operations.

We observed increased latency and timeouts between 18:48 and 19:08 UTC. We continue to closely monitor.

We have confirmed that our services have returned to normal operations.

We are seeing a delay in advisories being populated on [OSV.dev](http://OSV.dev), the last advisory update was at 05:03 UTC. We are monitoring the feed to review the data. New Vulnerability data may be delayed.

OSV advisory processing resumed at 23:50 UTC on August 25, and advisory freshness returned to normal at 04:35 UTC on August 26. All systems are now operating normally.

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.

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.

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.

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.

We are investigating reports of intermittent UI timeouts affecting the Package view, starting at approximately 12:16 PM UTC. Our engineering team is actively working to identify and resolve the underlying cause. We will post our next update by 12:51 PM UTC.

We are investigating reports of intermittent UI timeouts affecting the Package view, starting at approximately 12:16 PM UTC. Users may experience 504 timeout errors on the Packages view. Our engineering team has identified the issue, and mitigation steps are being deployed. Next Update by 16:00 UTC

Scope has been determined to be non-production only, so the incident is marked as non-impacting.

We are investigating reports of intermittent 500 errors affecting API and web requests across all regions, starting from approximately 17:14 UTC and finishing at 17:15 UTC (Approx 31 seconds impact), related to Database connection exhaustion. We detected a small number of errors across millions of successful requests in the window. The team is investigating the cause

Impact has been confirmed as ended. The engineering team is investigating & monitoring.

No further impact to API or Web applications outside of the 1 minute window

We are currently investigating elevated latency for Python package downloads. Users may experience slow request times or timeouts when downloading packages. Our engineering team is actively investigating, and we'll update the status accordingly.

Our engineering team has identified the cause and is working to resolve the issue.

We have confirmed that our work has returned services to normal operations.

We are investigating reports of intermittent authentication failures affecting Docker and Helm OCI logins for customers in all regions, starting from approximately 09:24UTC. We will post our next update by 09:54 UTC. This did not impact Enterprise (custom) domains or Enterprise Customers with custom domains.

We've reverted a change and confirmed resolution. This did not impact Enterprise (custom) domains or Enterprise Customers with custom domains.