Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Latitude outage history

    57 recorded Latitude incidents since April 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Network Connectivity Issues - São Paulo

    Started October 9, 2026 at 12:50 PM UTC · 3h 55m

    IssuesMinor incident
    Affected components
    SAO
    1. October 9, 2026 at 12:50 PM UTCinvestigating

      Our Network team is aware of and actively investigating connectivity issues affecting the SAO region. Further updates will be provided as soon as more information becomes available.

    2. October 9, 2026 at 1:39 PM UTCmonitoring

      A fix has been applied and network connectivity has been fully restored. Our team is currently monitoring traffic to ensure ongoing stability.

    3. October 9, 2026 at 4:45 PM UTCresolved

      This incident has been resolved.

    Network issue affecting services in Sao Paulo location

    Started September 10, 2026 at 10:03 PM UTC · 2h 1m

    OutageMajor incident
    Affected components
    SAO
    1. September 10, 2026 at 10:03 PM UTCinvestigating

      Network issue affecting services in our Sao Paulo location, identified today at approximately 21:00 UTC. Our Network Operations team is actively investigating the issue and working to fully restore normal conditions.

    2. September 10, 2026 at 10:13 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. September 10, 2026 at 11:37 PM UTCmonitoring

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

    4. September 11, 2026 at 12:03 AM UTCresolved

      A link degradation was identified with one of our providers. As a mitigation measure, traffic from the data center was rerouted through alternative links. Following continuous monitoring, the link has stabilized and performance has returned to normal.

    Power Issue - LON2

    Started August 8, 2026 at 12:17 AM UTC · 23h 37m

    OutageMajor incident
    Affected components
    LON2LON
    1. August 8, 2026 at 12:17 AM UTCinvestigating

      We are currently investigating this issue.

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

      We are continuing to investigate this issue.

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

      Some devices are being recovered. Our team are still working with the DCO to fully recover the site.

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

      Several servers have been recovered but the full extension of the site is still being worked on at the moment. Our team is still working with the DCO for the full resolution.

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

      This incident has been resolved. Our team will keep the communication for the affected customers via ongoing tickets.

    Network Connectivity Issues - New York

    Started June 26, 2026 at 10:09 PM UTC · 1h 17m

    IssuesMinor incident
    Affected components
    NYC
    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.

    Increased error rate for Reinstalling and Deploying

    Started June 25, 2026 at 9:16 AM UTC · 12h 9m

    OutageCritical incident
    Affected components
    Automation Tool
    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.

    Network Connectivity Incident - Miami

    Started June 23, 2026 at 10:23 PM UTC · 11h 6m

    Pending
    Affected components
    BUEMEX2APISAOTYO3LAX2LON2NYCSYD2SP1LONFRA2ASHDALSAO2Remote accessTYO4SJC2CHILAXSAN3SYDAMSMIA2FRASGPBGTVirtual networkIPMI Access
    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.

    Increased error rate for deployments in Dallas

    Started June 19, 2026 at 5:58 PM UTC · 38m

    IssuesMinor incident
    Affected components
    DAL
    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.

    IPMI Access Errors Increasing - Dallas

    Started June 18, 2026 at 9:43 PM UTC · 2h 47m

    IssuesMinor incident
    Affected components
    DAL
    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.

    Intermittent 5xx errors on Dashboard and API

    Started May 22, 2026 at 5:00 PM UTC · 0m

    Pending
    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.

    Network Outage - Silicon Valley

    Started May 7, 2026 at 6:11 PM UTC · 1h 8m

    OutageCritical incident
    Affected components
    SJC2
    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.

    Cloud Gateway Connectivity Issues - Dallas

    Started March 25, 2026 at 4:40 PM UTC · 2h 47m

    IssuesMinor incident
    Affected components
    DAL
    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.

    Increased error rate on provisioning actions and VMs

    Started March 18, 2026 at 7:03 PM UTC · 1h 32m

    OutageMajor incident
    Affected components
    BUEMEX2APIAutomation ToolTYO3LAX2LON2NYCSYD2LONFRA2ASHDALSAO2Remote accessTYO4SJC2CHILAXSAN3SYDAMSMIA2FRASGPBGTVirtual network
    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.

    Increased error rate for provisinings

    Started March 17, 2026 at 2:23 PM UTC · 3h 44m

    OutageMajor incident
    Affected components
    BUEMEX2SAOTYO3LAX2LON2NYCSYD2SP1LONFRA2ASHDALSAO2TYO4SJC2CHILAXSAN3SYDAMSMIA2FRASGPBGT
    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.

    Network Connectivity Issues - SAO1

    Started March 11, 2026 at 4:21 PM UTC · 3h 11m

    IssuesMinor incident
    Affected components
    SAO
    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.

    Increased error rate for deployments and Dallas connectivity

    Started March 4, 2026 at 6:05 PM UTC · 1h 42m

    OutageMajor incident
    Affected components
    BUEMEX2Automation ToolSAOTYO3LAX2LON2NYCSP1LONASHDALSAO2CHILAXSAN3SYDAMSMIA2FRASGPBGT
    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.

    Network Connectivity Incident - SAO and SAO2

    Started February 16, 2026 at 3:07 PM UTC · 6h 43m

    IssuesMinor incident
    Affected components
    SAOSAO2
    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.

    Intermittent deployments on US regions impacting Ubuntu 24/22 and Debian 12

    Started February 11, 2026 at 2:41 PM UTC · 5h 12m

    IssuesMinor incident
    Affected components
    Automation ToolLAX2NYCASHDALCHILAXMIA2
    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.

    Increased error rate for deployments with Ubuntu 24.04

    Started February 5, 2026 at 11:35 AM UTC · 12h 19m

    IssuesMinor incident
    Affected components
    BUEMEX2APISAOTYO3DashboardLAX2LON2NYCSP1LONASHDALSAO2CHILAXSAN3SYDAMSMIA2FRASGPBGT
    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.

    IPMI Access Issues – London (LON)

    Started December 21, 2025 at 2:35 PM UTC · 6h 6m

    IssuesMinor incident
    Affected components
    LON2LONIPMI Access
    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.

    Increased errors on bandwidth usage (API/Dashboard)

    Started December 15, 2025 at 2:57 PM UTC · 3h 0m

    OutageMajor incident
    Affected components
    APIDashboard
    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.