Historial de interrupciones de Latitude

1. August 8, 2026 at 12:17 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. August 8, 2026 at 12:29 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. August 8, 2026 at 3:05 AM UTCidentified

   Se están recuperando algunos dispositivos. Nuestro equipo sigue trabajando con el DCO para recuperar completamente el sitio.

4. August 8, 2026 at 11:06 AM UTCidentified

   Varios servidores han sido recuperados pero la extensión completa del sitio todavía se está trabajando en el momento. Nuestro equipo sigue trabajando con el DCO para la resolución completa.

5. August 8, 2026 at 11:54 PM UTCresolved

   Este incidente ha sido resuelto. Nuestro equipo mantendrá la comunicación para los clientes afectados a través de entradas en curso.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 26, 2026 at 10:09 PM UTCinvestigating

   We are currently investigating this issue.

2. June 26, 2026 at 11:09 PM UTCmonitoring

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

3. June 26, 2026 at 11:26 PM 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. June 25, 2026 at 9:16 AM UTCinvestigating

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

2. June 25, 2026 at 11:40 AM UTCmonitoring

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

3. June 25, 2026 at 9:25 PM UTCresolved

   This incident has been resolved.

1. June 23, 2026 at 10:23 PM UTCinvestigating

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

2. June 23, 2026 at 10:41 PM 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. June 24, 2026 at 12:35 AM 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. June 24, 2026 at 9:29 AM 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. June 19, 2026 at 5:58 PM UTCinvestigating

   We are currently investigating this issue.

2. June 19, 2026 at 6:24 PM UTCmonitoring

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

3. June 19, 2026 at 6:36 PM UTCresolved

   This incident has been resolved.

1. June 18, 2026 at 9:43 PM UTCinvestigating

   We are currently investigating this issue.

2. June 19, 2026 at 12:30 AM UTCresolved

   This incident has been resolved.

1. May 22, 2026 at 8:12 PM 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. May 7, 2026 at 6:11 PM 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. May 7, 2026 at 6:25 PM UTCmonitoring

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

3. May 7, 2026 at 7:18 PM 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. March 25, 2026 at 4:40 PM UTCinvestigating

   We are currently investigating this issue.

2. March 25, 2026 at 7:14 PM UTCmonitoring

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

3. March 25, 2026 at 7:27 PM UTCresolved

   This incident has been resolved.

1. March 18, 2026 at 7:03 PM 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. March 18, 2026 at 7:45 PM UTCmonitoring

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

3. March 18, 2026 at 8:35 PM UTCresolved

   This incident has been resolved.

1. March 17, 2026 at 2:23 PM 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. March 17, 2026 at 2:51 PM UTCinvestigating

   We are currently investigating this issue.

3. March 17, 2026 at 4:47 PM UTCmonitoring

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

4. March 17, 2026 at 6:07 PM UTCresolved

   This incident has been resolved.

1. March 11, 2026 at 4:21 PM UTCinvestigating

   We are currently investigating this issue.

2. March 11, 2026 at 4:44 PM UTCidentified

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

3. March 11, 2026 at 7:32 PM UTCresolved

   This incident has been resolved.

1. March 4, 2026 at 6:05 PM 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. March 4, 2026 at 6:06 PM UTCinvestigating

   We are continuing to investigate this issue.

3. March 4, 2026 at 6:25 PM UTCmonitoring

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

4. March 4, 2026 at 7:47 PM UTCresolved

   This incident has been resolved.

1. February 16, 2026 at 3:07 PM 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. February 16, 2026 at 4:00 PM 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. February 16, 2026 at 9:49 PM 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. February 11, 2026 at 2:41 PM 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. February 11, 2026 at 2:53 PM UTCidentified

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

3. February 11, 2026 at 5:40 PM UTCmonitoring

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

4. February 11, 2026 at 7:53 PM 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. February 5, 2026 at 11:35 AM 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. February 5, 2026 at 12:23 PM 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. February 5, 2026 at 5:03 PM 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. February 5, 2026 at 6:19 PM UTCidentified

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

5. February 5, 2026 at 6:22 PM 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. February 5, 2026 at 11:55 PM UTCresolved

   This incident has been resolved.

1. December 21, 2025 at 2:35 PM 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. December 21, 2025 at 8:41 PM UTCresolved

   This incident has been resolved.

1. December 15, 2025 at 2:57 PM 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. December 15, 2025 at 3:14 PM UTCmonitoring

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

3. December 15, 2025 at 5:57 PM 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.

1. December 11, 2025 at 2:13 PM UTCidentified

   We are currently observing increased deployment times and power verification delays in the following regions: US - ASH - LAS - MIA Europe - FRA - LON2 This impact is related to an ongoing global connectivity incident involving the Tier 1 provider Cirion, which is affecting communication paths worldwide. Our engineering team is actively mitigating the issue by adjusting routing within our infrastructure and coordinating route changes with upstream providers. We will continue to share updates as we make progress.

2. December 11, 2025 at 6:25 PM UTCresolved

   After a fix from Tier 1 provider Cirion, the communication has been completely restored.

1. December 11, 2025 at 12:30 PM UTCmonitoring

   Our Network team is aware of reports of a connectivity issue to SAO1 and SAO2 servers. It has been identified that the Tier 1 ISP Cirion is facing an issue in its network, which is causing reachability issues for a variety of networks across the globe. We've removed our traffic from our Cirion circuit and will keep monitoring the traffic.

2. December 11, 2025 at 6:21 PM UTCresolved

   This incident has been resolved.