Cloudsmith

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-20 12:02 UTC

   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

2. resolved 2026-10-20 12:05 UTC

   All services are operating normally

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 16:39 UTC

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

2. identified 2026-10-13 16:54 UTC

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

3. monitoring 2026-10-13 17:41 UTC

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

4. resolved 2026-10-13 17:47 UTC

   We have deployed the fix and confirmed resolution

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 18:39 UTC

   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.

2. investigating 2026-10-12 19:05 UTC

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

3. monitoring 2026-10-12 19:08 UTC

   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.

4. resolved 2026-10-12 19:25 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 06:19 UTC

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

2. identified 2026-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...

3. identified 2026-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.

4. identified 2026-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.

5. monitoring 2026-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...

6. monitoring 2026-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.

7. monitoring 2026-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.

8. resolved 2026-10-05 08:30 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 16:02 UTC

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

2. identified 2026-09-30 16:23 UTC

   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.

3. monitoring 2026-09-30 16:44 UTC

   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.

4. monitoring 2026-09-30 16:55 UTC

   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.

5. resolved 2026-09-30 17:26 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-28 16:55 UTC

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

2. monitoring 2026-09-28 17:12 UTC

   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

3. resolved 2026-09-28 17:28 UTC

   We have resolved the issue with pulling Docker images

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 08:18 UTC

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

2. investigating 2026-09-23 08:50 UTC

   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

3. monitoring 2026-09-23 10:33 UTC

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

4. resolved 2026-09-23 11:40 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-22 11:13 UTC

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

2. resolved 2026-09-22 11:46 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 16:13 UTC

   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.

2. identified 2026-09-14 16:59 UTC

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

3. identified 2026-09-14 17:22 UTC

   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.

4. resolved 2026-09-14 18:30 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 14:14 UTC

   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.

2. investigating 2026-09-08 14:53 UTC

   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

3. monitoring 2026-09-08 15:58 UTC

   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.

4. monitoring 2026-09-08 17:03 UTC

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

5. monitoring 2026-09-08 18:01 UTC

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

6. resolved 2026-09-08 19:03 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 19:27 UTC

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

2. investigating 2026-08-31 19:58 UTC

   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.

3. monitoring 2026-08-31 20:14 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.

4. resolved 2026-08-31 20:34 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 14:56 UTC

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

2. identified 2026-08-27 15:21 UTC

   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.

3. identified 2026-08-27 16:11 UTC

   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.

4. monitoring 2026-08-27 16:33 UTC

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

5. resolved 2026-08-27 17:13 UTC

   We have confirmed that all services are operating as normal.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 16:38 UTC

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

2. investigating 2026-08-25 17:06 UTC

   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.

3. monitoring 2026-08-25 17:29 UTC

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

4. resolved 2026-08-25 18:09 UTC

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

5. monitoring 2026-08-25 19:45 UTC

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

6. resolved 2026-08-26 07:55 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 14:09 UTC

   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.

2. resolved 2026-08-26 07:40 UTC

   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.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-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.

2. investigating 2026-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...

3. identified 2026-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.

4. resolved 2026-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...

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-06 12:16 UTC

   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.

2. identified 2026-08-06 13:29 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...

3. resolved 2026-08-06 13:59 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 16:26 UTC

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

2. investigating 2026-08-05 16:28 UTC

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

3. resolved 2026-08-05 18:11 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 20:01 UTC

   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.

2. identified 2026-07-30 20:34 UTC

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

3. resolved 2026-07-30 20:56 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 09:50 UTC

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

2. resolved 2026-07-30 09:54 UTC

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

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 16:23 UTC

   We are investigating reports of Intermittent RPM package upload sync failures affecting package synchronisation for customers starting from approximately 15:53 UTC today. Our engineering team is actively working on the issue and has already implemented immediate mitigations. We...

2. identified 2026-07-29 16:51 UTC

   We are investigating reports of Intermittent RPM package upload sync failures affecting package synchronisation for customers starting from approximately 15:53 UTC today. Our engineering team is actively working on the issue and is currently deploying a fix. We will post our...

3. monitoring 2026-07-29 17:17 UTC

   We are investigating reports of Intermittent RPM package upload sync failures affecting package synchronisation for customers starting from approximately 15:53 UTC today. Our engineers have successfully deployed a fix and are currently re-syncing affected packages. We will post...

4. resolved 2026-07-29 17:36 UTC

   Packages have successfully resynced and package syncing is operating as expected

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 09:04 UTC

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

2. investigating 2026-07-16 09:52 UTC

   We are continuing to investigate elevated latency for Python package downloads across the US West & EU West regions. Users may experience slow request times or timeouts when downloading packages. Our engineering team is currently undertaking several actions to return to normal...

3. monitoring 2026-07-16 10:39 UTC

   We have confirmed the cause of elevated latency for Python package downloads across the US West & EU West regions. The Engineering team has released a change internally and we're monitoring the service to confirm continued stability.

4. resolved 2026-07-16 11:11 UTC

   We have confirmed that our change has returned stability to the service

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-14 07:15 UTC

   We experienced minor service degradation in eu-west-1 between 1:15am and 7:25am UTC. During this time, some customers may have experienced elevated error rates when using the web application, API, or downloading packages. Our engineers identified the root cause and implemented a...

2. resolved 2026-07-14 07:35 UTC

   Services have recovered and we are continuing to monitor the platform to ensure stability.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 08:23 UTC

   Customers may experience intermittent sync failures for docker images. Our engineers our currently investigating.

2. identified 2026-07-14 09:25 UTC

   The issue has been identified and our engineering team is currently working on deploying a fix. We will share the next update once the fix is deployed.

3. identified 2026-07-14 10:38 UTC

   Package syncing has been restored. Some security scan results may be delayed while we finish rolling out the remaining fix.

4. monitoring 2026-07-14 11:18 UTC

   Package sync is now fully operational. Some customers may have experienced failures in generating SBOMs during mitigation. We are running a backfill.

5. monitoring 2026-07-14 13:03 UTC

   Backfill is currently in progress. We will share the next update once it is completed.

6. resolved 2026-07-14 16:07 UTC

   Services have become fully operational and the backfill for the impacted SBOMs have completed. We are continuing to monitor the platform to ensure stability.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-11 00:59 UTC

   We are experiencing elevated error rates across all regions. Our engineers are investigating the cause.

2. monitoring 2026-07-11 01:07 UTC

   Our Engineers have identified and resolved the issue. We will continue to monitor.

3. resolved 2026-07-11 01:26 UTC

   System has returned to normal operational levels.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-09 13:33 UTC

   We are investigating reports of degraded performance to package downloads and APIs in the Europe and US East regions.

2. identified 2026-07-09 14:06 UTC

   We have taken steps to mitigate the issue. We are seeing operations return to normal levels in most regions. Customers may still experience some degradation in us-west-2.

3. monitoring 2026-07-09 15:14 UTC

   The system has returned to normal operations across all regions, and we will continue to monitor stability.

4. resolved 2026-07-09 17:27 UTC

   All systems are operational.

Excerpts are shortened. Read the full incident on Cloudsmith's status page.