Latitude.sh Outage History

Latitude.sh is up right now

There were 8 Latitude.sh outages since February 5, 2026 totaling 37h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.latitude.sh

Minor March 25, 2026

Cloud Gateway Connectivity Issues - Dallas

Detected by Pingoru
Mar 25, 2026, 04:40 PM UTC
Resolved
Mar 25, 2026, 07:27 PM UTC
Duration
2h 47m
Affected: DAL
Timeline · 3 updates
  1. investigating Mar 25, 2026, 04:40 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 25, 2026, 07:14 PM UTC

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

  3. resolved Mar 25, 2026, 07:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 18, 2026

Increased error rate on provisioning actions and VMs

Detected by Pingoru
Mar 18, 2026, 07:03 PM UTC
Resolved
Mar 18, 2026, 08:35 PM UTC
Duration
1h 32m
Affected: APIMIA2CHILAXNYCSYDDALRemote accessSAN3Automation ToolTYO3LONVirtual networkMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMSFRA2SJC2SYD2TYO4
Timeline · 3 updates
  1. identified Mar 18, 2026, 07:03 PM UTC

    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. monitoring Mar 18, 2026, 07:45 PM UTC

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

  3. resolved Mar 18, 2026, 08:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Increased error rate for provisinings

Detected by Pingoru
Mar 17, 2026, 02:23 PM UTC
Resolved
Mar 17, 2026, 06:07 PM UTC
Duration
3h 43m
Affected: SAOSP1MIA2CHILAXNYCSYDDALSAN3TYO3LONMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMSFRA2SJC2SYD2TYO4
Timeline · 5 updates
  1. investigating Mar 17, 2026, 02:23 PM UTC

    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. monitoring Mar 17, 2026, 02:33 PM UTC

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

  3. investigating Mar 17, 2026, 02:51 PM UTC

    We are currently investigating this issue.

  4. monitoring Mar 17, 2026, 04:47 PM UTC

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

  5. resolved Mar 17, 2026, 06:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Network Connectivity Issues - SAO1

Detected by Pingoru
Mar 11, 2026, 04:21 PM UTC
Resolved
Mar 11, 2026, 07:32 PM UTC
Duration
3h 11m
Affected: SAO
Timeline · 3 updates
  1. investigating Mar 11, 2026, 04:21 PM UTC

    We are currently investigating this issue.

  2. identified Mar 11, 2026, 04:44 PM UTC

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

  3. resolved Mar 11, 2026, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 4, 2026

Increased error rate for deployments and Dallas connectivity

Detected by Pingoru
Mar 04, 2026, 06:05 PM UTC
Resolved
Mar 04, 2026, 07:47 PM UTC
Duration
1h 42m
Affected: SAOSP1MIA2CHILAXNYCSYDDALSAN3Automation ToolTYO3LONMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMS
Timeline · 4 updates
  1. investigating Mar 04, 2026, 06:05 PM UTC

    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. investigating Mar 04, 2026, 06:06 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 04, 2026, 06:25 PM UTC

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

  4. resolved Mar 04, 2026, 07:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 16, 2026

Network Connectivity Incident - SAO and SAO2

Detected by Pingoru
Feb 16, 2026, 03:07 PM UTC
Resolved
Feb 16, 2026, 09:49 PM UTC
Duration
6h 42m
Affected: SAOSAO2
Timeline · 3 updates
  1. identified Feb 16, 2026, 03:07 PM UTC

    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. identified Feb 16, 2026, 04:00 PM UTC

    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. resolved Feb 16, 2026, 09:49 PM UTC

    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.

Read the full incident report →

Minor February 11, 2026

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

Detected by Pingoru
Feb 11, 2026, 02:41 PM UTC
Resolved
Feb 11, 2026, 07:53 PM UTC
Duration
5h 12m
Affected: MIA2CHILAXNYCDALAutomation ToolASHLAX2
Timeline · 5 updates
  1. identified Feb 11, 2026, 02:41 PM UTC

    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. identified Feb 11, 2026, 02:48 PM UTC

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

  3. identified Feb 11, 2026, 02:53 PM UTC

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

  4. monitoring Feb 11, 2026, 05:40 PM UTC

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

  5. resolved Feb 11, 2026, 07:53 PM UTC

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

Read the full incident report →

Minor February 5, 2026

Increased error rate for deployments with Ubuntu 24.04

Detected by Pingoru
Feb 05, 2026, 11:35 AM UTC
Resolved
Feb 05, 2026, 11:55 PM UTC
Duration
12h 19m
Affected: SAODashboardSP1APIMIA2CHILAXNYCSYDDALSAN3TYO3LONMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMS
Timeline · 7 updates
  1. investigating Feb 05, 2026, 11:35 AM UTC

    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. identified Feb 05, 2026, 12:23 PM UTC

    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. identified Feb 05, 2026, 01:34 PM UTC

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

  4. identified Feb 05, 2026, 05:03 PM UTC

    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.

  5. identified Feb 05, 2026, 06:19 PM UTC

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

  6. monitoring Feb 05, 2026, 06:22 PM UTC

    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.

  7. resolved Feb 05, 2026, 11:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Latitude.sh downtime and outages?

Pingoru polls Latitude.sh's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Latitude.sh reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Latitude.sh alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Latitude.sh for free

5 free monitors · No credit card required