Cloudsmith driftsforstyrrelser

1. 6. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 13.59 UTCresolved

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

1. 5. august 2026 kl. 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. august 2026 kl. 16.28 UTCinvestigating

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

3. 5. august 2026 kl. 18.11 UTCresolved

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

1. 30. juli 2026 kl. 20.01 UTCinvestigating

   Vi er i øjeblikket ved at undersøge forhøjet latency for Python pakke downloads. Brugere kan opleve langsom forespørgsel tider eller timeouts, når du henter pakker. Vores ingeniørhold undersøger sagen, og vi opdaterer status.

2. 30. juli 2026 kl. 20.34 UTCidentified

   Vores ingeniørhold har identificeret årsagen og arbejder på at løse problemet.

3. 30. juli 2026 kl. 20.56 UTCresolved

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

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juli 2026 kl. 09.50 UTCinvestigating

   Vi undersøger rapporter om intermitterende autentificering fejl påvirker Docker og Helm OCI logins for kunder i alle regioner, startende fra omkring 09: 24UTC. Vi vil sende vores næste opdatering inden 09: 54 UTC. Dette påvirkede ikke Enterprise (brugerdefinerede) domæner eller Enterprise Kunder med brugerdefinerede domæner.

2. 30. juli 2026 kl. 09.54 UTCresolved

   Vi har vendt en ændring og bekræftet resolution. Dette påvirkede ikke Enterprise (brugerdefinerede) domæner eller Enterprise Kunder med brugerdefinerede domæner.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 16.23 UTCinvestigating

   Vi undersøger rapporter om intermitterende RPM-pakke upload sync fejl, der påvirker pakkesynkronisering for kunder startende fra ca. 15: 53 UTC i dag. Vores ingeniørteam arbejder aktivt på sagen og har allerede gennemført øjeblikkelige lempelser. Vi sender næste opdatering kl. 17: 51 UTC.

2. 29. juli 2026 kl. 16.51 UTCidentified

   Vi undersøger rapporter om intermitterende RPM-pakke upload sync fejl, der påvirker pakkesynkronisering for kunder startende fra ca. 15: 53 UTC i dag. Vores ingeniørhold arbejder aktivt på spørgsmålet og er i øjeblikket ved at implementere et fix. Vi sender næste opdatering kl. 18: 20 UTC.

3. 29. juli 2026 kl. 17.17 UTCmonitoring

   Vi undersøger rapporter om intermitterende RPM-pakke upload sync fejl, der påvirker pakkesynkronisering for kunder startende fra ca. 15: 53 UTC i dag. Vores ingeniører har med succes indsat en rettelse og er i øjeblikket omsynkronisering berørte pakker. Vi sender vores næste opdatering senest 18: 37 UTC.

4. 29. juli 2026 kl. 17.36 UTCresolved

   Pakker har med succes resynkroniseret og pakke synkronisering fungerer som forventet

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. juli 2026 kl. 09.04 UTCinvestigating

   Vi er i øjeblikket ved at undersøge forhøjet latency for Python pakke downloads på tværs af USA West & EU West regioner. Brugere kan opleve langsom forespørgsel tider eller timeouts, når du henter pakker. Vores ingeniørhold undersøger sagen, og vi opdaterer status.

2. 16. juli 2026 kl. 09.52 UTCinvestigating

   Vi fortsætter med at undersøge forhøjet latency for Python pakke downloads på tværs af USA West & EU West regioner. Brugere kan opleve langsom forespørgsel tider eller timeouts, når du henter pakker. Vores ingeniør team er i øjeblikket i gang med flere handlinger for at vende tilbage til normale operationer, og vi vil opdatere status i overensstemmelse hermed

3. 16. juli 2026 kl. 10.39 UTCmonitoring

   Vi har bekræftet årsagen til forhøjet latency for Python pakke downloads på tværs af USA West & EU West regioner. Teknikerne har udskrevet en ændring internt, og vi overvåger tjenesten for at bekræfte fortsat stabilitet.

4. 16. juli 2026 kl. 11.11 UTCresolved

   Vi har bekræftet, at vores forandring har vendt tilbage stabilitet til tjenesten

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 08.23 UTCinvestigating

   Kunderne kan opleve intermitterende sync fejl for docker billeder. Vores ingeniører undersøger sagen.

2. 14. juli 2026 kl. 09.25 UTCidentified

   Problemet er blevet identificeret, og vores ingeniørhold arbejder i øjeblikket på at implementere et fix. Vi vil dele den næste opdatering, når fixet er indsat.

3. 14. juli 2026 kl. 10.38 UTCidentified

   Pakkensynkronisering er blevet genoprettet. Nogle sikkerhedsscanningsresultater kan blive forsinket, mens vi er færdige med at rulle det resterende fix ud.

4. 14. juli 2026 kl. 11.18 UTCmonitoring

   Pakkesynkronisering er nu fuldt operationel. Nogle kunder kan have oplevet svigt i produktionen af SBOM 'er under afbødning. Vi kører en backfill.

5. 14. juli 2026 kl. 13.03 UTCmonitoring

   Backfill er i gang. Vi deler næste opdatering, når den er færdig.

6. 14. juli 2026 kl. 16.07 UTCresolved

   Tjenesteydelserne er blevet fuldt operationelle, og de ramte SBOM 'er er blevet fuldt udfyldt. Vi overvåger fortsat platformen for at sikre stabilitet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 10.26 UTCmonitoring

   Vi oplevede mindre forringelse i eu- west-1 mellem 1: 15 og 7: 25 UTC. I løbet af denne tid, kan nogle kunder have oplevet forhøjede fejlrater, når du bruger web-applikationen, API, eller downloade pakker. Vores ingeniører identificerede årsagen og gennemførte en afbødning. Tjenesterne er kommet sig, og vi overvåger fortsat platformen for at sikre stabilitet.

2. 14. juli 2026 kl. 10.29 UTCresolved

   Tjenesterne er kommet sig, og vi overvåger fortsat platformen for at sikre stabilitet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. juli 2026 kl. 00.59 UTCinvestigating

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

2. 11. juli 2026 kl. 01.07 UTCmonitoring

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

3. 11. juli 2026 kl. 01.26 UTCresolved

   System has returned to normal operational levels.

1. 9. juli 2026 kl. 13.33 UTCinvestigating

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

2. 9. juli 2026 kl. 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. juli 2026 kl. 15.14 UTCmonitoring

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

4. 9. juli 2026 kl. 17.27 UTCresolved

   All systems are operational.

1. 9. juli 2026 kl. 01.51 UTCinvestigating

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

2. 9. juli 2026 kl. 02.48 UTCmonitoring

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

3. 9. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 09.06 UTCresolved

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

1. 17. juni 2026 kl. 14.10 UTCinvestigating

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

2. 17. juni 2026 kl. 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. juni 2026 kl. 15.57 UTCresolved

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

1. 3. juni 2026 kl. 14.09 UTCinvestigating

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

2. 3. juni 2026 kl. 14.37 UTCresolved

   Performance has returned to normal in the Europe region.

1. 1. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 14.26 UTCresolved

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

1. 27. maj 2026 kl. 17.11 UTCinvestigating

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

2. 27. maj 2026 kl. 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. maj 2026 kl. 17.42 UTCresolved

   We can confirm the issue has been resolved.

1. 27. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 13.28 UTCresolved

   We can confirm the issue has been fully resolved.

1. 15. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 10.19 UTCresolved

   We can confirm that the issue is now resolved.

1. 14. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 09.45 UTCresolved

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