Latitude.sh Outage History
Latitude.sh is up right nowPingoru has recorded 49 incidents for Latitude.sh: 30 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 2 | 4 of 744 (1%) |
| June 2026 | 5 | 28 of 720 (4%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 24 of 744 (3%) |
| September 2026 | 1 | 2 of 720 (0%) |
| October 2026 | 1 | 4 of 515 (1%) |
Incidents, newest first
Minor October 9, 2026 Network Connectivity Issues - São Paulo 3h 55m SAO
Started Oct 09, 2026, 12:50 PM UTC· resolved Oct 09, 2026, 04:45 PM UTC
- investigating Oct 09, 2026, 12:50 PM UTC
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.
- monitoring Oct 09, 2026, 01:39 PM UTC
A fix has been applied and network connectivity has been fully restored. Our team is currently monitoring traffic to ensure ongoing stability.
- resolved Oct 09, 2026, 04:45 PM UTC
This incident has been resolved.
Major September 10, 2026 Network issue affecting services in Sao Paulo location 2h SAO
Started Sep 10, 2026, 10:03 PM UTC· resolved Sep 11, 2026, 12:03 AM UTC
- investigating Sep 10, 2026, 10:03 PM UTC
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.
- investigating Sep 10, 2026, 10:13 PM UTC
We are continuing to investigate this issue.
- monitoring Sep 10, 2026, 11:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 11, 2026, 12:03 AM UTC
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.
Major August 8, 2026 Power Issue - LON2 23h 37m LON, LON2
Started Aug 08, 2026, 12:17 AM UTC· resolved Aug 08, 2026, 11:54 PM UTC
- investigating Aug 08, 2026, 12:17 AM UTC
We are currently investigating this issue.
- investigating Aug 08, 2026, 12:29 AM UTC
We are continuing to investigate this issue.
- identified Aug 08, 2026, 03:05 AM UTC
Some devices are being recovered. Our team are still working with the DCO to fully recover the site.
- identified Aug 08, 2026, 11:06 AM UTC
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.
- resolved Aug 08, 2026, 11:54 PM UTC
This incident has been resolved. Our team will keep the communication for the affected customers via ongoing tickets.
Minor June 26, 2026 Network Connectivity Issues - New York 1h 16m NYC
Started Jun 26, 2026, 10:09 PM UTC· resolved Jun 26, 2026, 11:26 PM UTC
- investigating Jun 26, 2026, 10:09 PM UTC
We are currently investigating this issue.
- monitoring Jun 26, 2026, 11:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 11:26 PM UTC
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.
Critical June 25, 2026 Increased error rate for Reinstalling and Deploying 12h 8m Automation Tool
Started Jun 25, 2026, 09:16 AM UTC· resolved Jun 25, 2026, 09:25 PM UTC
- investigating Jun 25, 2026, 09:16 AM UTC
We are currently investigating this issue and will provide more details as soon as they are available.
- monitoring Jun 25, 2026, 11:40 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 25, 2026, 09:25 PM UTC
This incident has been resolved.
Notice June 23, 2026 Network Connectivity Incident - Miami 11h 5m SAO, SP1, API, MIA2 and 25 more
Started Jun 23, 2026, 10:23 PM UTC· resolved Jun 24, 2026, 09:29 AM UTC
- investigating Jun 23, 2026, 10:23 PM UTC
We are currently investigating this issue.
- investigating Jun 23, 2026, 10:41 PM UTC
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.
- monitoring Jun 24, 2026, 12:35 AM UTC
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.
- resolved Jun 24, 2026, 09:29 AM UTC
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.
Minor June 19, 2026 Increased error rate for deployments in Dallas 38m DAL
Started Jun 19, 2026, 05:58 PM UTC· resolved Jun 19, 2026, 06:36 PM UTC
- investigating Jun 19, 2026, 05:58 PM UTC
We are currently investigating this issue.
- monitoring Jun 19, 2026, 06:24 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 19, 2026, 06:36 PM UTC
This incident has been resolved.
Minor June 18, 2026 IPMI Access Errors Increasing - Dallas 2h 46m DAL
Started Jun 18, 2026, 09:43 PM UTC· resolved Jun 19, 2026, 12:30 AM UTC
- investigating Jun 18, 2026, 09:43 PM UTC
We are currently investigating this issue.
- resolved Jun 19, 2026, 12:30 AM UTC
This incident has been resolved.
Notice May 22, 2026 Intermittent 5xx errors on Dashboard and API 3h 10m
Started May 22, 2026, 02:00 PM UTC· resolved May 22, 2026, 05:10 PM UTC
- resolved May 22, 2026, 08:12 PM UTC
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.
Critical May 7, 2026 Network Outage - Silicon Valley 1h 7m SJC2
Started May 07, 2026, 06:11 PM UTC· resolved May 07, 2026, 07:18 PM UTC
- investigating May 07, 2026, 06:11 PM UTC
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.
- monitoring May 07, 2026, 06:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 07, 2026, 07:18 PM UTC
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.
Minor March 25, 2026 Cloud Gateway Connectivity Issues - Dallas 2h 47m DAL
Started Mar 25, 2026, 04:40 PM UTC· resolved Mar 25, 2026, 07:27 PM UTC
- investigating Mar 25, 2026, 04:40 PM UTC
We are currently investigating this issue.
- monitoring Mar 25, 2026, 07:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 25, 2026, 07:27 PM UTC
This incident has been resolved.
Major March 18, 2026 Increased error rate on provisioning actions and VMs 1h 32m API, MIA2, CHI, LAX and 23 more
Started Mar 18, 2026, 07:03 PM UTC· resolved Mar 18, 2026, 08:35 PM UTC
- 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.
- monitoring Mar 18, 2026, 07:45 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 18, 2026, 08:35 PM UTC
This incident has been resolved.
Major March 17, 2026 Increased error rate for provisinings 3h 43m SAO, SP1, MIA2, CHI and 21 more
Started Mar 17, 2026, 02:23 PM UTC· resolved Mar 17, 2026, 06:07 PM UTC
- 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
- monitoring Mar 17, 2026, 02:33 PM UTC
A fix has been implemented and we are monitoring the results.
- investigating Mar 17, 2026, 02:51 PM UTC
We are currently investigating this issue.
- monitoring Mar 17, 2026, 04:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 17, 2026, 06:07 PM UTC
This incident has been resolved.
Minor March 11, 2026 Network Connectivity Issues - SAO1 3h 11m SAO
Started Mar 11, 2026, 04:21 PM UTC· resolved Mar 11, 2026, 07:32 PM UTC
- investigating Mar 11, 2026, 04:21 PM UTC
We are currently investigating this issue.
- identified Mar 11, 2026, 04:44 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 11, 2026, 07:32 PM UTC
This incident has been resolved.
Major March 4, 2026 Increased error rate for deployments and Dallas connectivity 1h 42m SAO, SP1, MIA2, CHI and 18 more
Started Mar 04, 2026, 06:05 PM UTC· resolved Mar 04, 2026, 07:47 PM UTC
- 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.
- investigating Mar 04, 2026, 06:06 PM UTC
We are continuing to investigate this issue.
- monitoring Mar 04, 2026, 06:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 04, 2026, 07:47 PM UTC
This incident has been resolved.
Minor February 16, 2026 Network Connectivity Incident - SAO and SAO2 6h 42m SAO, SAO2
Started Feb 16, 2026, 03:07 PM UTC· resolved Feb 16, 2026, 09:49 PM UTC
- 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.
- 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.
- 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.
Minor February 11, 2026 Intermittent deployments on US regions impacting Ubuntu 24/22 and Debian 12 5h 12m MIA2, CHI, LAX, NYC and 4 more
Started Feb 11, 2026, 02:41 PM UTC· resolved Feb 11, 2026, 07:53 PM UTC
- 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.
- identified Feb 11, 2026, 02:48 PM UTC
We are continuing to work on a fix for this issue.
- identified Feb 11, 2026, 02:53 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 11, 2026, 05:40 PM UTC
The fix has been applied, and we are monitoring the situation.
- 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.
Minor February 5, 2026 Increased error rate for deployments with Ubuntu 24.04 12h 19m SAO, Dashboard, SP1, API and 19 more
Started Feb 05, 2026, 11:35 AM UTC· resolved Feb 05, 2026, 11:55 PM UTC
- 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.
- 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.
- identified Feb 05, 2026, 01:34 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- identified Feb 05, 2026, 06:19 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- resolved Feb 05, 2026, 11:55 PM UTC
This incident has been resolved.
Minor December 21, 2025 IPMI Access Issues – London (LON) 6h 5m LON, IPMI Access, LON2
Started Dec 21, 2025, 02:35 PM UTC· resolved Dec 21, 2025, 08:41 PM UTC
- investigating Dec 21, 2025, 02:35 PM UTC
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.
- resolved Dec 21, 2025, 08:41 PM UTC
This incident has been resolved.
Major December 15, 2025 Increased errors on bandwidth usage (API/Dashboard) 2h 59m Dashboard, API
Started Dec 15, 2025, 02:57 PM UTC· resolved Dec 15, 2025, 05:57 PM UTC
- investigating Dec 15, 2025, 02:57 PM UTC
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.
- monitoring Dec 15, 2025, 03:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 15, 2025, 05:57 PM UTC
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.
Notice December 11, 2025 Increased error rate for deployments and power check 4h 11m
Started Dec 11, 2025, 02:13 PM UTC· resolved Dec 11, 2025, 06:25 PM UTC
- identified Dec 11, 2025, 02:13 PM UTC
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.
- resolved Dec 11, 2025, 06:25 PM UTC
After a fix from Tier 1 provider Cirion, the communication has been completely restored.
Notice December 11, 2025 Connection Instability at SAO1 and SAO2 5h 50m SAO, SAO2
Started Dec 11, 2025, 12:30 PM UTC· resolved Dec 11, 2025, 06:21 PM UTC
- monitoring Dec 11, 2025, 12:30 PM UTC
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.
- resolved Dec 11, 2025, 06:21 PM UTC
This incident has been resolved.
Notice December 10, 2025 Increased failure rate for deployments and power actions in Dallas 3h 1m
Started Dec 10, 2025, 12:03 PM UTC· resolved Dec 10, 2025, 03:05 PM UTC
- identified Dec 10, 2025, 12:03 PM UTC
We are aware of an increasing error failure rate for deployments and power actions in Dallas. Our team is already working to solve the issue.
- identified Dec 10, 2025, 12:03 PM UTC
We are continuing to work on a fix for this issue.
- resolved Dec 10, 2025, 03:05 PM UTC
This incident has been resolved.
Major December 3, 2025 Network Connectivity Incident – Megatelecom Link (SAO ↔ SAO2) 6h 1m SAO
Started Dec 03, 2025, 11:09 AM UTC· resolved Dec 03, 2025, 05:11 PM UTC
- identified Dec 03, 2025, 11:09 AM UTC
We are currently experiencing a connectivity issue affecting the a dark fiber provider links between our SAO and SAO2 sites. Provider has reported overnight issues with their core network equipment, which is causing instability on the inter-site link. This circuit is responsible for carrying several extended VLANs between the locations, resulting in some devices appearing unavailable. Provider is working on resolving the issue, and the estimated time for service restoration is 08:40 BRT. We will continue to monitor and provide updates as soon as new information becomes available.
- identified Dec 03, 2025, 12:02 PM UTC
We are continuing to work on the incident. The dark fiber provider has requested additional time to complete the remediation. We will post another update shortly with a confirmed resolution timeline.
- identified Dec 03, 2025, 01:05 PM UTC
A fix has been implemented and we are currently monitoring the service. Some connections may already be coming back online. We will continue working toward full resolution and provide updates as progress continues.
- monitoring Dec 03, 2025, 01:28 PM UTC
All services have returned to normal after corrective actions were applied by the provider. We will continue to monitor the connection for a while before closing this incident. If you are still experiencing any issues or need further details about the occurrence, please feel free to reach out.
- resolved Dec 03, 2025, 05:11 PM UTC
This incident has been resolved.
Minor December 1, 2025 Increased errors on the Dashboard/API 1h 11m Dashboard, API
Started Dec 01, 2025, 08:43 PM UTC· resolved Dec 01, 2025, 09:54 PM UTC
- identified Dec 01, 2025, 08:43 PM UTC
We are investigating an increased error rate affecting multiple actions in our systems, especially Remote Access, VMs, Custom image deployments, and Databases. It is only affecting the creation of resource actions. Your server is not impacted. We already identified and are working to address this issue as soon as possible, it should take only a few minutes.
- monitoring Dec 01, 2025, 09:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 01, 2025, 09:54 PM UTC
This incident has been resolved.