Cronologia delle interruzioni di Latitude

1. 9 ottobre 2026 alle ore 12:50 UTCinvestigating

   Il nostro team di rete è a conoscenza e indaga attivamente i problemi di connettività che interessano la regione SAO. Ulteriori aggiornamenti saranno forniti non appena ulteriori informazioni saranno disponibili.

2. 9 ottobre 2026 alle ore 13:39 UTCmonitoring

   Una correzione è stata applicata e la connettività di rete è stata completamente restaurata. Il nostro team sta monitorando il traffico per garantire una stabilità costante.

3. 9 ottobre 2026 alle ore 16:45 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 10 settembre 2026 alle ore 22:03 UTCinvestigating

   Numero di rete che interessa i servizi nella nostra sede di San Paolo, identificato oggi a circa 21:00 UTC. Il nostro team di Network Operations sta attivamente indagando sul problema e lavorando per ripristinare completamente le condizioni normali.

2. 10 settembre 2026 alle ore 22:13 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 10 settembre 2026 alle ore 23:37 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 11 settembre 2026 alle ore 00:03 UTCresolved

   Un degrado di collegamento è stato identificato con uno dei nostri fornitori. Come misura di mitigazione, il traffico dal data center è stato reindirizzato attraverso collegamenti alternativi. Dopo il monitoraggio continuo, il collegamento si è stabilizzato e le prestazioni sono tornate alla normalità.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 8 agosto 2026 alle ore 00:17 UTCinvestigating

   Stiamo attualmente indagando su questo problema.

2. 8 agosto 2026 alle ore 00:29 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 8 agosto 2026 alle ore 03:05 UTCidentified

   Alcuni dispositivi vengono recuperati. Il nostro team sta ancora lavorando con il DCO per recuperare completamente il sito.

4. 8 agosto 2026 alle ore 11:06 UTCidentified

   Diversi server sono stati recuperati, ma l'estensione completa del sito è ancora in fase di lavorazione. Il nostro team sta ancora lavorando con il DCO per la risoluzione completa.

5. 8 agosto 2026 alle ore 23:54 UTCresolved

   Questo incidente è stato risolto. Il nostro team manterrà la comunicazione per i clienti interessati tramite biglietti in corso.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 26 giugno 2026 alle ore 22:09 UTCinvestigating

   We are currently investigating this issue.

2. 26 giugno 2026 alle ore 23:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 giugno 2026 alle ore 23:26 UTCresolved

   We experienced an issue on one of our border routers in New York. The router did not fail completely, however some services were impacted, which required a reboot to fully restore normal operation. During this time, our redundant infrastructure ensured that only part of the traffic was affected. Traffic is now fully stable, we are monitoring the health status closely and will share a full update once our investigation is complete.

1. 25 giugno 2026 alle ore 09:16 UTCinvestigating

   We are currently investigating this issue and will provide more details as soon as they are available.

2. 25 giugno 2026 alle ore 11:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 25 giugno 2026 alle ore 21:25 UTCresolved

   This incident has been resolved.

1. 23 giugno 2026 alle ore 22:23 UTCinvestigating

   We are currently investigating an outage in Miami HQ. Is it impacting all of our services, Dashboard and API.

2. 23 giugno 2026 alle ore 22:41 UTCinvestigating

   We have a preliminary diagnosis that the incident was caused by a power outage affecting all the customers on the same floor. We are pushing the DC operator for an update. Is it impacting all of our services, Dashboard and API.

3. 24 giugno 2026 alle ore 00:35 UTCmonitoring

   Services have been restored following a power outage. We are currently monitoring the environment closely and awaiting final confirmation from the data center team. Further updates to follow.

4. 24 giugno 2026 alle ore 09:29 UTCresolved

   This incident has been resolved. We will follow up with a post-mortem as soon as a complete RCA is finished between Latitude.sh and our DCO.

1. 19 giugno 2026 alle ore 17:58 UTCinvestigating

   We are currently investigating this issue.

2. 19 giugno 2026 alle ore 18:24 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 19 giugno 2026 alle ore 18:36 UTCresolved

   This incident has been resolved.

1. 18 giugno 2026 alle ore 21:43 UTCinvestigating

   We are currently investigating this issue.

2. 19 giugno 2026 alle ore 00:30 UTCresolved

   This incident has been resolved.

1. 22 maggio 2026 alle ore 20:12 UTCresolved

   Between 14:00 BRT and 14:10 BRT (17:00 UTC — 17:10 UTC) on May 22, 2026, a subset of customers experienced intermittent 5xx errors on the Dashboard and API. The issue was identified, mitigated, and services are fully operational. We apologize for the inconvenience. If you continue to experience issues, please reach out to our support team.

1. 7 maggio 2026 alle ore 18:11 UTCinvestigating

   We are aware and currently investigating an ongoing outage at Silicon Valley DC. We apologize for any inconvenience and will provide updates as more information becomes available.

2. 7 maggio 2026 alle ore 18:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 7 maggio 2026 alle ore 19:18 UTCresolved

   The issue has already been resolved, and services have been fully restored. We're currently investigating the case together with the Colocation Provider, and we will provide a post-mortem report as soon as possible.

1. 25 marzo 2026 alle ore 16:40 UTCinvestigating

   We are currently investigating this issue.

2. 25 marzo 2026 alle ore 19:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 25 marzo 2026 alle ore 19:27 UTCresolved

   This incident has been resolved.

1. 18 marzo 2026 alle ore 19:03 UTCidentified

   We are resolving an increased error rate affecting provisioning actions and virtual machines. It was related to a connection issue with internal services and should be solved within the next 30 minutes. This issue only affects new provisioning action requests. We are truly sorry about the inconvenience.

2. 18 marzo 2026 alle ore 19:45 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18 marzo 2026 alle ore 20:35 UTCresolved

   This incident has been resolved.

1. 17 marzo 2026 alle ore 14:23 UTCinvestigating

   We are investigating an increased error rate affecting provisinings. This issue only affects new provisinings requests. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes

2. 17 marzo 2026 alle ore 14:51 UTCinvestigating

   We are currently investigating this issue.

3. 17 marzo 2026 alle ore 16:47 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 17 marzo 2026 alle ore 18:07 UTCresolved

   This incident has been resolved.

1. 11 marzo 2026 alle ore 16:21 UTCinvestigating

   We are currently investigating this issue.

2. 11 marzo 2026 alle ore 16:44 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 marzo 2026 alle ore 19:32 UTCresolved

   This incident has been resolved.

1. 4 marzo 2026 alle ore 18:05 UTCinvestigating

   We are investigating an increased error rate affecting deployments and a problem with Dallas connectivity We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 4 marzo 2026 alle ore 18:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 marzo 2026 alle ore 18:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 4 marzo 2026 alle ore 19:47 UTCresolved

   This incident has been resolved.

1. 16 febbraio 2026 alle ore 15:07 UTCidentified

   We are currently experiencing a connectivity issue affecting the dark fiber provider links between our SAO and SAO2 sites. This circuit is responsible for carrying several extended VLANs between the locations, resulting in some devices appearing unavailable. The provider is working on resolving the issue. At the moment, no ETA has been provided. We will continue to monitor and provide updates as soon as new information becomes available.

2. 16 febbraio 2026 alle ore 16:00 UTCidentified

   An ETR has been provided by the dark fiber provider. They are currently working on the issue, and the ETR is 7:00 PM (UTC). The fiber cut was caused by an incident during public road renovation works, which resulted in a major outage affecting several other fiber providers in the region. We will continue to monitor the situation and provide updates as soon as new information becomes available.

3. 16 febbraio 2026 alle ore 21:49 UTCresolved

   The fiber cut was restored by the provider at 7:15 PM (UTC). We have been monitoring the link since then and have not observed any new incidents.

1. 11 febbraio 2026 alle ore 14:41 UTCidentified

   We are currently experiencing intermittent issues with server deployments in US regions. The issue affects Ubuntu 24.04, Ubuntu 22.04, and Debian 12 base images, where user data may not be applied correctly during provisioning. Our team is actively investigating and working on a fix. We will provide updates as the situation progresses.

2. 11 febbraio 2026 alle ore 14:53 UTCidentified

   We are continuing to work on a fix for this issue.

3. 11 febbraio 2026 alle ore 17:40 UTCmonitoring

   The fix has been applied, and we are monitoring the situation.

4. 11 febbraio 2026 alle ore 19:53 UTCresolved

   This incident has been resolved. All services are operating normally, and the system is stable. Monitoring remains in place to ensure continued reliability.

1. 5 febbraio 2026 alle ore 11:35 UTCinvestigating

   We are investigating an increased error rate affecting deployments with Ubuntu 24.04. This issue only affects new deployments and reinstallations of existing servers. During the incident, if possible, prefer deploying any other OS over Ubuntu 24.04. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 5 febbraio 2026 alle ore 12:23 UTCidentified

   We have identified the root cause of the issue as an instability on Canonical’s side affecting Ubuntu 24.04 images. This problem impacts new deployments and reinstallations only. Existing servers already running Ubuntu 24.04 are not affected. Our team is monitoring the situation and working on restoring normal deployment operations for Ubuntu 24.04 across the affected regions. As a temporary workaround, we recommend deploying an alternative OS until the issue is fully resolved. Further updates will be shared as more information becomes available.

3. 5 febbraio 2026 alle ore 17:03 UTCidentified

   The issue affecting Ubuntu 24.04 deployments has been resolved in the majority of regions. At this time, deployment issues persist only in the ASH (Ashburn) and CHI (Chicago) regions. All other regions are operating normally. Our team continues to work on a fix to fully restore Ubuntu 24.04 deployments in the remaining affected regions. Further updates will be provided as progress is made.

4. 5 febbraio 2026 alle ore 18:19 UTCidentified

   We are continuing to work on a fix for this issue.

5. 5 febbraio 2026 alle ore 18:22 UTCmonitoring

   This incident has been resolved. The issue affecting Ubuntu 24.04 deployments has been fully mitigated, and all regions are now operating normally. Deployments and reinstallations are functioning as expected across all locations. Thank you for your patience.

6. 5 febbraio 2026 alle ore 23:55 UTCresolved

   This incident has been resolved.

1. 21 dicembre 2025 alle ore 14:35 UTCinvestigating

   We are currently investigating an issue affecting IPMI access in our London (LON) location. Some users may experience failures when establishing VPN sessions required for IPMI connectivity. Our Network Enginnering team is actively working to identify the root cause and apply the necessary configuration changes. Impact: - IPMI access in London may be unavailable or fail to establish - No impact to customer data or running workloads has been identified We will provide further updates as soon as more information is available.

2. 21 dicembre 2025 alle ore 20:41 UTCresolved

   This incident has been resolved.

1. 15 dicembre 2025 alle ore 14:57 UTCinvestigating

   We are investigating an increased error rate affecting the bandwidth usage page. We are working to address this issue as soon as possible and will provide updates as we learn more and implement the necessary fixes.

2. 15 dicembre 2025 alle ore 15:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 15 dicembre 2025 alle ore 17:57 UTCresolved

   The issue affecting the bandwidth usage page has been resolved. The fix has been successfully applied, and monitoring confirms that services are operating normally. We appreciate your patience and apologize for any inconvenience caused.