Histórico de interrupções do Cloudsmith

1. 6 Eost 2026 da 12:24 UTCinvestigating

   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. 6 Eost 2026 da 13:29 UTCidentified

   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

3. 6 Eost 2026 da 13:59 UTCresolved

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

1. 5 Eost 2026 da 16:26 UTCinvestigating

   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. 5 Eost 2026 da 16:28 UTCinvestigating

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

3. 5 Eost 2026 da 18:11 UTCresolved

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

1. 30 Gouere 2026 da 20:01 UTCinvestigating

   Atualmente estamos investigando latência elevada para downloads de pacotes Python. Os usuários podem experimentar tempos de solicitação lentos ou timeouts ao baixar pacotes. A nossa equipa de engenharia está a investigar, e vamos actualizar o estado de acordo.

2. 30 Gouere 2026 da 20:34 UTCidentified

   Nossa equipe de engenharia identificou a causa e está trabalhando para resolver o problema.

3. 30 Gouere 2026 da 20:56 UTCresolved

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

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Gouere 2026 da 09:50 UTCinvestigating

   Estamos investigando relatórios de falhas intermitentes de autenticação que afetam logins Docker e Helm OCI para clientes em todas as regiões, a partir de aproximadamente 09:24UTC. Publicaremos nossa próxima atualização em 09:54 UTC. Isso não afetou os domínios Enterprise (custom) ou Enterprise Customers com domínios personalizados.

2. 30 Gouere 2026 da 09:54 UTCresolved

   Revertemos uma mudança e confirmamos a resolução. Isso não afetou os domínios Enterprise (custom) ou Enterprise Customers com domínios personalizados.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 16:23 UTCinvestigating

   Estamos investigando relatórios de falhas de sincronização de upload de pacotes RPM intermitentes que afetam a sincronização de pacotes para clientes a partir de aproximadamente 15:53 UTC hoje. Nossa equipe de engenharia está trabalhando ativamente na questão e já implementou mitigação imediata. Publicaremos nossa próxima atualização até 17:51 UTC.

2. 29 Gouere 2026 da 16:51 UTCidentified

   Estamos investigando relatórios de falhas de sincronização de upload de pacotes RPM intermitentes que afetam a sincronização de pacotes para clientes a partir de aproximadamente 15:53 UTC hoje. Nossa equipe de engenharia está trabalhando ativamente no problema e atualmente está implementando uma correção. Publicaremos nossa próxima atualização até 18:20 UTC.

3. 29 Gouere 2026 da 17:17 UTCmonitoring

   Estamos investigando relatórios de falhas de sincronização de upload de pacotes RPM intermitentes que afetam a sincronização de pacotes para clientes a partir de aproximadamente 15:53 UTC hoje. Nossos engenheiros implantaram com sucesso uma correção e atualmente estão re-sincronizando pacotes afetados. Publicaremos nossa próxima atualização até 18:37 UTC, o mais tardar.

4. 29 Gouere 2026 da 17:36 UTCresolved

   Os pacotes foram resincronizados com sucesso e a sincronização de pacotes está funcionando como esperado

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 09:04 UTCinvestigating

   Atualmente estamos investigando latência elevada para downloads de pacotes Python nas regiões Oeste e Oeste dos EUA. Os usuários podem experimentar tempos de solicitação lentos ou timeouts ao baixar pacotes. A nossa equipa de engenharia está a investigar, e vamos actualizar o estado de acordo.

2. 16 Gouere 2026 da 09:52 UTCinvestigating

   Continuamos a investigar a latência elevada dos downloads de pacotes Python nas regiões Oeste e Oeste dos EUA. Os usuários podem experimentar tempos de solicitação lentos ou timeouts ao baixar pacotes. A nossa equipa de engenharia está actualmente a empreender várias acções para voltar às operações normais, e vamos actualizar o estado em conformidade

3. 16 Gouere 2026 da 10:39 UTCmonitoring

   Confirmamos a causa da latência elevada dos downloads de pacotes Python nas regiões Oeste e Oeste dos EUA. A equipa de engenharia liberou uma mudança interna e estamos a monitorizar o serviço para confirmar a estabilidade contínua.

4. 16 Gouere 2026 da 11:11 UTCresolved

   Confirmamos que a nossa mudança devolveu estabilidade ao serviço

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 08:23 UTCinvestigating

   Os clientes podem experimentar falhas de sincronização intermitente para imagens de docker. Os nossos engenheiros estão a investigar.

2. 14 Gouere 2026 da 09:25 UTCidentified

   O problema foi identificado e nossa equipe de engenharia está atualmente trabalhando na implantação de uma correção. Vamos partilhar a próxima atualização assim que a correção for implantada.

3. 14 Gouere 2026 da 10:38 UTCidentified

   A sincronização do pacote foi restaurada. Alguns resultados de verificação de segurança podem ser atrasados enquanto terminamos de executar a correção restante.

4. 14 Gouere 2026 da 11:18 UTCmonitoring

   A sincronização do pacote está totalmente operacional. Alguns clientes podem ter experimentado falhas na geração de SBOMs durante a mitigação. Estamos a fazer uma reserva.

5. 14 Gouere 2026 da 13:03 UTCmonitoring

   O enchimento está em andamento. Vamos compartilhar a próxima atualização uma vez concluída.

6. 14 Gouere 2026 da 16:07 UTCresolved

   Os serviços tornaram-se plenamente operacionais e o enchimento dos SBOMs impactados já foi concluído. Continuamos a monitorar a plataforma para garantir a estabilidade.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 10:26 UTCmonitoring

   Nós experimentamos a degradação do serviço menor em eu-west-1 entre 1:15 e 7:25 UTC. Durante esse tempo, alguns clientes podem ter experimentado elevadas taxas de erro ao usar o aplicativo web, API ou baixar pacotes. Nossos engenheiros identificaram a causa raiz e implementaram uma mitigação. Os serviços recuperaram e continuamos a monitorar a plataforma para garantir a estabilidade.

2. 14 Gouere 2026 da 10:29 UTCresolved

   Os serviços recuperaram e continuamos a monitorar a plataforma para garantir a estabilidade.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Gouere 2026 da 00:59 UTCinvestigating

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

2. 11 Gouere 2026 da 01:07 UTCmonitoring

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

3. 11 Gouere 2026 da 01:26 UTCresolved

   System has returned to normal operational levels.

1. 9 Gouere 2026 da 13:33 UTCinvestigating

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

2. 9 Gouere 2026 da 14:06 UTCidentified

   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. 9 Gouere 2026 da 15:14 UTCmonitoring

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

4. 9 Gouere 2026 da 17:27 UTCresolved

   All systems are operational.

1. 9 Gouere 2026 da 01:51 UTCinvestigating

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

2. 9 Gouere 2026 da 02:48 UTCmonitoring

   We have taken steps to mitigate the issue and are actively monitoring the results.

3. 9 Gouere 2026 da 02:56 UTCresolved

   The mitigation steps taken have resolved the issue. Latency has returned to normal levels, and we will continue monitoring for stability.

1. 23 Mezheven 2026 da 08:34 UTCinvestigating

   We're currently investigating performance issues affecting continuous policy evaluations for existing packages. As a precaution, we've temporarily disabled this feature while our team works on a resolution. Newly ingested packages continue to be evaluated as normal, and index-level cooldown policies remain unaffected. We're actively working to restore full functionality and will provide updates as we make progress.

2. 23 Mezheven 2026 da 09:38 UTCinvestigating

   We're currently investigating performance issues affecting continuous policy evaluations for existing packages. As a precaution, we've temporarily disabled this feature while our team works on a resolution. Newly ingested packages continue to be evaluated as normal, and index-level cooldown policies remain unaffected. No other operations for package upload, processing, or download are affected. We've identified several actions and will continue to keep you updated on progress.

3. 24 Mezheven 2026 da 08:21 UTCidentified

   We've identified the root cause and have a fix in progress. We've re-enabled continuous policy evaluations and are actively monitoring platform performance. We'll provide a further update once the fix is fully rolled out.

4. 24 Mezheven 2026 da 11:01 UTCmonitoring

   We've re-enabled continuous policy evaluations and are actively monitoring platform performance. The system is operational, and we're continuing to work on backfill and further performance enhancements.

5. 24 Mezheven 2026 da 15:58 UTCmonitoring

   We've re-enabled continuous policy evaluations and are continuing to monitor platform performance. The system is operational, and we're continuing our work on the backfill and additional performance enhancements. We'll provide additional updates on Thursday 25th June.

6. 25 Mezheven 2026 da 16:37 UTCmonitoring

   The system is operational, and we're continuing our work on the backfill and additional performance enhancements. We'll provide additional updates as we progress

7. 26 Mezheven 2026 da 09:06 UTCresolved

   The system is operational, and we've resolved the backfill operation and our additional performance enhancements.

1. 17 Mezheven 2026 da 14:10 UTCinvestigating

   We’re seeing an increase in request times. API and Web UI requests are impacted. Our engineers are investigating.

2. 17 Mezheven 2026 da 14:18 UTCmonitoring

   We have mitigated the issue and request queuing has reduced. API requests & Web App are returning to normal response times. We are actively monitoring.

3. 17 Mezheven 2026 da 15:57 UTCresolved

   No further impacts were noted during the monitoring. All services are working as expected.

1. 3 Mezheven 2026 da 14:09 UTCinvestigating

   We are investigating reports of degraded performance to package downloads and apis in the Europe region

2. 3 Mezheven 2026 da 14:37 UTCresolved

   Performance has returned to normal in the Europe region.

1. 1 Mezheven 2026 da 12:03 UTCinvestigating

   We are currently investigating an issue affecting some analytics and UI queries. A small percentage of requests are experiencing timeouts around 10 seconds or returning errors. Most queries are completing successfully. We're working with our partners on investigating and mitigating this issue.

2. 1 Mezheven 2026 da 12:48 UTCinvestigating

   We are continuing to investigate an issue affecting some analytics and UI queries. A small percentage of requests are timing out (around 10 seconds) or returning errors. We’re continuing to work with our partners to investigate and mitigate the issue.

3. 1 Mezheven 2026 da 13:39 UTCidentified

   We are continuing to monitor the issue affecting analytics and UI queries within the Cloudsmith web app, client log exports, and Datadog integrations. Working alongside our infrastructure partners, a root cause has been identified. Mitigation efforts are currently underway to restore full capacity. A large majority of queries continue to complete successfully. We will provide another update once the issue is fully resolved or within the next 1 hour.

4. 1 Mezheven 2026 da 14:05 UTCmonitoring

   Working with our infrastructure partners, we've received confirmation that the issue has been resolved. We are validating across our platform, and we'll provide another update with confirmation within the next hour.

5. 1 Mezheven 2026 da 14:26 UTCresolved

   We've validated across our platform and confirmed all services are operating normally

1. 27 Mae 2026 da 17:11 UTCinvestigating

   We’re seeing an increase in error rates in the US region. Our engineers are investigating the cause.

2. 27 Mae 2026 da 17:20 UTCmonitoring

   The elevated download errors have been resolved, and all systems are running normally. Impact Windows (UTC): • us-west: 16:35 – 16:47 • us-east: 17:02 – 17:03

3. 27 Mae 2026 da 17:42 UTCresolved

   We can confirm the issue has been resolved.

1. 27 Mae 2026 da 10:42 UTCinvestigating

   We are currently experiencing elevated error rates and increased request latency. Our engineers are actively investigating the cause. Impacted services • Europe: Requests are partially impacted • Uploads: Requests are partially impacted across all regions • Docker: Downloads are partially impacted across all regions • US, Tokyo, Sydney: Downloads are not affected at this time

2. 27 Mae 2026 da 11:44 UTCinvestigating

   We are currently experiencing elevated error rates and increased request latency related to a significant increase in illegitimate network requests Impacted services • Europe: Requests are partially impacted • Uploads: Requests are partially impacted across all regions • Docker: Downloads are partially impacted across all regions • US, Tokyo, Sydney: Downloads are not affected at this time Engineers are engaged and continuing to investigate & mitigate

3. 27 Mae 2026 da 11:49 UTCmonitoring

   We have mitigated the issue related to the significant increase in illegitimate network requests, and we're continuing to monitor service availability & performance.

4. 27 Mae 2026 da 12:30 UTCmonitoring

   We have mitigated the issue related to the significant increase in illegitimate network requests, and we're continuing to monitor service availability & performance. **Impact:** **Region:** EU **Web Applications:** Service Degradation **API:** Partial Service Degradation **Uploads/Downloads:** Partial Service Degradation

5. 27 Mae 2026 da 13:28 UTCresolved

   We can confirm the issue has been fully resolved.

1. 15 Mae 2026 da 12:05 UTCinvestigating

   We are seeing an increase in errors for users accessing the classic web app and our new web app. Our engineers are investigating this issue.

2. 15 Mae 2026 da 12:33 UTCmonitoring

   Error rates for the classic and new web apps have returned to normal levels. Our engineers are continuing to monitor to ensure stability.

3. 15 Mae 2026 da 13:03 UTCresolved

   We have taken measures to ensure continued stability. After continued monitoring, we have confirmed that error rates remain at normal levels for both the classic and new web apps.

1. 15 Mae 2026 da 08:41 UTCinvestigating

   Since 19:00 UTC on 14 May, customers outside the EU may experience intermittent failures when pushing Docker packages. Our engineers are investigating the issue.

2. 15 Mae 2026 da 09:45 UTCmonitoring

   We’ve identified the issue. The main region impacted was Japan. The engineering team has implemented a fix and is now monitoring the system.

3. 15 Mae 2026 da 10:19 UTCresolved

   We can confirm that the issue is now resolved.

1. 14 Mae 2026 da 09:00 UTCinvestigating

   We are aware of an issue affecting session management. Our team has taken mitigative action and customers may notice some session timeouts. Users encountering issues should log back into the webapp, and any failed jobs should succeed on rerun.

2. 14 Mae 2026 da 09:31 UTCmonitoring

   We have resolved the issue affecting session management. The underlying cause has been addressed and our engineers are continuing to monitor. Customers who were experiencing session timeouts should now be able to log in without issue, and any previously failed jobs should complete successfully on rerun. We apologize for any inconvenience this may have caused.

3. 14 Mae 2026 da 09:45 UTCresolved

   We can confirm the session management issue has been fully resolved and all systems are operating normally.