Cloudsmith Outage History

Cloudsmith is up right now

Pingoru has recorded 66 incidents for Cloudsmith: 66 in the last 12 months and 18 in the last 90 days.

Source: status.cloudsmith.com

66incidents recorded
66last 12 months
18last 90 days
8 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Cloudsmith in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026499 of 720 (14%)
May 2026826 of 744 (3%)
June 2026478 of 720 (11%)
July 2026918 of 744 (2%)
August 2026725 of 744 (3%)
September 2026613 of 720 (2%)
October 202655 of 744 (1%)
November 202600 of 19 (0%)

Incidents, newest first

Minor October 26, 2026 Experiencing 502/504 errors for Maven uploads 1h 9m Core (Package Uploads)

Started Oct 26, 2026, 02:22 PM UTC· resolved Oct 26, 2026, 03:32 PM UTC

  1. investigating Oct 26, 2026, 02:22 PM UTC

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

  2. monitoring Oct 26, 2026, 02:35 PM UTC

    We have deployed a fix and are actively monitoring results.

  3. resolved Oct 26, 2026, 03:32 PM UTC

    This issue has now been resolved.

  4. resolved Oct 26, 2026, 03:32 PM UTC

    This issue has now been resolved.

Read the full incident report →

Minor October 20, 2026 Intermittent 500 errors on Package Downloads 2m

Started Oct 20, 2026, 12:02 PM UTC· resolved Oct 20, 2026, 12:05 PM UTC

  1. monitoring Oct 20, 2026, 12:02 PM 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 Oct 20, 2026, 12:05 PM UTC

    Impact is currently ended

  3. resolved Oct 20, 2026, 12:05 PM UTC

    All services are operating normally

Read the full incident report →

Minor October 13, 2026 Issues with package downloads 1h 8m Core (Package Downloads)

Started Oct 13, 2026, 04:39 PM UTC· resolved Oct 13, 2026, 05:47 PM UTC

  1. investigating Oct 13, 2026, 04:39 PM UTC

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

  2. identified Oct 13, 2026, 04:54 PM 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 Oct 13, 2026, 05:41 PM UTC

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

  4. resolved Oct 13, 2026, 05:47 PM UTC

    We have deployed the fix and confirmed resolution

  5. resolved Oct 13, 2026, 05:47 PM UTC

    We have deployed the fix and confirmed resolution

Read the full incident report →

Minor October 12, 2026 Intermittent 503 Errors on Download Requests 46m Core (Package Downloads)

Started Oct 12, 2026, 06:39 PM UTC· resolved Oct 12, 2026, 07:25 PM UTC

  1. investigating Oct 12, 2026, 06:39 PM 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 Oct 12, 2026, 07:05 PM UTC

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

  3. monitoring Oct 12, 2026, 07:08 PM 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 Oct 12, 2026, 07:25 PM 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.

  5. resolved Oct 12, 2026, 07:25 PM 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.

Read the full incident report →

Minor October 5, 2026 Intermittent Issue pushing NuGet packages 2h 10m Core (Package Uploads)

Started Oct 05, 2026, 06:19 AM UTC· resolved Oct 05, 2026, 08:30 AM UTC

  1. investigating Oct 05, 2026, 06:19 AM UTC

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

  2. identified Oct 05, 2026, 06:26 AM 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.

  3. identified Oct 05, 2026, 06:44 AM 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 Oct 05, 2026, 07:13 AM 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 Oct 05, 2026, 07:34 AM 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.

  6. monitoring Oct 05, 2026, 07:55 AM 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 Oct 05, 2026, 08:14 AM 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 Oct 05, 2026, 08:30 AM 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 pushes have returned to normal. Pulling and downloading packages was unaffected throughout, as were all other package formats.

  9. resolved Oct 05, 2026, 08:30 AM 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 pushes have returned to normal. Pulling and downloading packages was unaffected throughout, as were all other package formats.

Read the full incident report →

Minor September 30, 2026 Service Degradation On Our Web API 1h 24m

Started Sep 30, 2026, 04:02 PM UTC· resolved Sep 30, 2026, 05:26 PM UTC

  1. investigating Sep 30, 2026, 04:02 PM UTC

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

  2. identified Sep 30, 2026, 04:23 PM 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 Sep 30, 2026, 04:44 PM 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 Sep 30, 2026, 04:55 PM 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 Sep 30, 2026, 05:26 PM UTC

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

  6. resolved Sep 30, 2026, 05:26 PM UTC

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

Read the full incident report →

Minor September 28, 2026 Issues Pulling Docker Images 33m

Started Sep 28, 2026, 04:55 PM UTC· resolved Sep 28, 2026, 05:28 PM UTC

  1. investigating Sep 28, 2026, 04:55 PM 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 Sep 28, 2026, 05:12 PM 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 Sep 28, 2026, 05:28 PM UTC

    We have resolved the issue with pulling Docker images

  4. resolved Sep 28, 2026, 05:28 PM UTC

    We have resolved the issue with pulling Docker images

Read the full incident report →

Minor September 23, 2026 Increase in latency for OIDC requests 3h 21m Integrations (OpenID Connect)

Started Sep 23, 2026, 08:18 AM UTC· resolved Sep 23, 2026, 11:40 AM UTC

  1. investigating Sep 23, 2026, 08:18 AM UTC

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

  2. investigating Sep 23, 2026, 08:50 AM 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 Sep 23, 2026, 10:33 AM UTC

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

  4. resolved Sep 23, 2026, 11:40 AM UTC

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

  5. resolved Sep 23, 2026, 11:40 AM UTC

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

Read the full incident report →

Minor September 22, 2026 Package synchronization delays 32m Core (Package Sync)

Started Sep 22, 2026, 11:13 AM UTC· resolved Sep 22, 2026, 11:46 AM UTC

  1. monitoring Sep 22, 2026, 11:13 AM UTC

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

  2. resolved Sep 22, 2026, 11:46 AM UTC

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

  3. resolved Sep 22, 2026, 11:46 AM UTC

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

Read the full incident report →

Minor September 14, 2026 Policies with upstream tags are not blocking packages when Block Until Scanned is enabled. 2h 16m

Started Sep 14, 2026, 04:13 PM UTC· resolved Sep 14, 2026, 06:30 PM UTC

  1. investigating Sep 14, 2026, 04:13 PM 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 Sep 14, 2026, 04:59 PM UTC

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

  3. identified Sep 14, 2026, 05:22 PM 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 Sep 14, 2026, 06:30 PM UTC

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

  5. resolved Sep 14, 2026, 06:30 PM UTC

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

Read the full incident report →

Minor September 8, 2026 OSV vulnerability data delays. 4h 49m Core (Policy Management)

Started Sep 08, 2026, 02:14 PM UTC· resolved Sep 08, 2026, 07:03 PM UTC

  1. investigating Sep 08, 2026, 02:14 PM 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 Sep 08, 2026, 02:53 PM 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 Sep 08, 2026, 03:58 PM 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 Sep 08, 2026, 05:03 PM 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 continuing to monitor progress.

  5. monitoring Sep 08, 2026, 06:01 PM 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 progress. Next update at 07:00 PM UTC.

  6. resolved Sep 08, 2026, 07:03 PM UTC

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

  7. resolved Sep 08, 2026, 07:03 PM UTC

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

Read the full incident report →

Minor August 31, 2026 Request Latency and Timeout in US region 1h 7m Core (Package Downloads)

Started Aug 31, 2026, 07:27 PM UTC· resolved Aug 31, 2026, 08:34 PM UTC

  1. investigating Aug 31, 2026, 07:27 PM UTC

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

  2. investigating Aug 31, 2026, 07:58 PM 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 Aug 31, 2026, 08:14 PM 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 Aug 31, 2026, 08:34 PM 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.

  5. resolved Aug 31, 2026, 08:34 PM 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.

Read the full incident report →

Minor August 27, 2026 Delay in Policy Evaluations 2h 16m Core (Policy Management)

Started Aug 27, 2026, 02:56 PM UTC· resolved Aug 27, 2026, 05:13 PM UTC

  1. investigating Aug 27, 2026, 02:56 PM UTC

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

  2. identified Aug 27, 2026, 03:21 PM 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 Aug 27, 2026, 04:11 PM 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 Aug 27, 2026, 04:33 PM UTC

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

  5. resolved Aug 27, 2026, 05:13 PM UTC

    We have confirmed that all services are operating as normal.

  6. resolved Aug 27, 2026, 05:13 PM UTC

    We have confirmed that all services are operating as normal.

Read the full incident report →

Minor August 25, 2026 Request latency and timeout 15h 17m Core (Package Downloads)

Started Aug 25, 2026, 04:38 PM UTC· resolved Aug 26, 2026, 07:55 AM UTC

  1. investigating Aug 25, 2026, 04:38 PM UTC

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

  2. investigating Aug 25, 2026, 05:06 PM 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 Aug 25, 2026, 05:29 PM UTC

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

  4. resolved Aug 25, 2026, 06:09 PM UTC

    This incident is now resolved. Between 17:04 and 18:13 UTC, customers experienced latency and timeouts affecting metadata and package download requests. We have confirmed normal operations.

  5. monitoring Aug 25, 2026, 07:45 PM UTC

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

  6. resolved Aug 26, 2026, 07:55 AM UTC

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

  7. resolved Aug 26, 2026, 07:55 AM UTC

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

Read the full incident report →

Minor August 25, 2026 Delay in advisory data published on osv.dev 17h 31m

Started Aug 25, 2026, 02:09 PM UTC· resolved Aug 26, 2026, 07:40 AM UTC

  1. investigating Aug 25, 2026, 02:09 PM 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 Aug 26, 2026, 07:40 AM 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.

  3. resolved Aug 26, 2026, 07:40 AM 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.

Read the full incident report →

Minor August 21, 2026 New upstream packages may not appear in repositories 39m Core (Upstreams)

Started Aug 21, 2026, 06:15 PM UTC· resolved Aug 21, 2026, 06:54 PM UTC

  1. investigating Aug 21, 2026, 06:15 PM 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 Aug 21, 2026, 06:30 PM 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.

  3. identified Aug 21, 2026, 06:40 PM 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 Aug 21, 2026, 06:54 PM UTC

    The issue is now resolved. The packages have started caching again. The packages pulled during 17:00 to 18:45 UTC would be missing from the repositories. The missing packages will get cached in the consecutive pulls. NOTE: Only caching of packages to the repository was impacted. Package pulls remained unaffected during the duration of the incident.

  5. resolved Aug 21, 2026, 06:54 PM 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.

Read the full incident report →

Minor August 6, 2026 Intermittent UI timeouts affecting the Package view 1h 43m

Started Aug 06, 2026, 12:16 PM UTC· resolved Aug 06, 2026, 01:59 PM UTC

  1. investigating Aug 06, 2026, 12:16 PM 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 Aug 06, 2026, 01:29 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.

  3. resolved Aug 06, 2026, 01:59 PM UTC

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

  4. resolved Aug 06, 2026, 01:59 PM UTC

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

Read the full incident report →

Minor August 5, 2026 Errors affecting API and web requests 1h 44m

Started Aug 05, 2026, 04:26 PM UTC· resolved Aug 05, 2026, 06:11 PM UTC

  1. investigating Aug 05, 2026, 04:26 PM 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 across millions of successful requests in the window. The team is investigating the cause

  2. investigating Aug 05, 2026, 04:28 PM UTC

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

  3. resolved Aug 05, 2026, 06:11 PM UTC

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

  4. resolved Aug 05, 2026, 06:11 PM UTC

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

Read the full incident report →

Minor July 30, 2026 Download Request Latency for Python Packages 55m Core (Package Downloads)

Started Jul 30, 2026, 08:01 PM UTC· resolved Jul 30, 2026, 08:56 PM UTC

  1. investigating Jul 30, 2026, 08:01 PM 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 Jul 30, 2026, 08:34 PM UTC

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

  3. resolved Jul 30, 2026, 08:56 PM UTC

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

Read the full incident report →

Minor July 30, 2026 Intermittent authentication failures affecting Docker and Helm OCI logins in all regions 3m Core (Package Uploads), Core (Package Downloads)

Started Jul 30, 2026, 09:50 AM UTC· resolved Jul 30, 2026, 09:54 AM UTC

  1. investigating Jul 30, 2026, 09:50 AM 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 Customers with custom domains.

  2. resolved Jul 30, 2026, 09:54 AM UTC

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

Read the full incident report →

Minor July 29, 2026 Intermittent RPM package upload sync failures affecting package synchronization 1h 12m Core (Package Sync)

Started Jul 29, 2026, 04:23 PM UTC· resolved Jul 29, 2026, 05:36 PM UTC

  1. investigating Jul 29, 2026, 04:23 PM 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 will post our next update by 17:51 UTC.

  2. identified Jul 29, 2026, 04:51 PM 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 next update by 18:20 UTC.

  3. monitoring Jul 29, 2026, 05:17 PM 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 our next update by 18:37 UTC at the latest.

  4. resolved Jul 29, 2026, 05:36 PM UTC

    Packages have successfully resynced and package syncing is operating as expected

Read the full incident report →

Minor July 16, 2026 Download Request Latency for Python Packages 2h 6m Core (Package Downloads)

Started Jul 16, 2026, 09:04 AM UTC· resolved Jul 16, 2026, 11:11 AM UTC

  1. investigating Jul 16, 2026, 09:04 AM 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 accordingly.

  2. investigating Jul 16, 2026, 09:52 AM 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 operations, and we'll update the status accordingly

  3. monitoring Jul 16, 2026, 10:39 AM 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 Jul 16, 2026, 11:11 AM UTC

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

Read the full incident report →

Minor July 14, 2026 Intermittent failures when syncing Docker images. 7h 43m Core (Security Scanning), Core (Package Sync)

Started Jul 14, 2026, 08:23 AM UTC· resolved Jul 14, 2026, 04:07 PM UTC

  1. investigating Jul 14, 2026, 08:23 AM UTC

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

  2. identified Jul 14, 2026, 09:25 AM 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 Jul 14, 2026, 10:38 AM UTC

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

  4. monitoring Jul 14, 2026, 11:18 AM 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 Jul 14, 2026, 01:03 PM UTC

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

  6. resolved Jul 14, 2026, 04:07 PM 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.

Read the full incident report →

Minor July 14, 2026 Minor service degradation in Europe region 20m Core (Package Downloads)

Started Jul 14, 2026, 07:15 AM UTC· resolved Jul 14, 2026, 07:35 AM UTC

  1. monitoring Jul 14, 2026, 07:15 AM 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 mitigation. Services have recovered and we are continuing to monitor the platform to ensure stability.

  2. resolved Jul 14, 2026, 07:35 AM UTC

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

Read the full incident report →

Minor July 11, 2026 Partial outage impacting normal operations globally 26m

Started Jul 11, 2026, 12:59 AM UTC· resolved Jul 11, 2026, 01:26 AM UTC

  1. investigating Jul 11, 2026, 12:59 AM UTC

    We are experiencing elevated error rates in the Europe region. Our engineers are investigating the cause.

  2. monitoring Jul 11, 2026, 01:07 AM UTC

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

  3. resolved Jul 11, 2026, 01:26 AM UTC

    System has returned to normal operational levels.

Read the full incident report →