Latitude.sh Outage History
Latitude.sh is up right nowPingoru has recorded 49 incidents for Latitude.sh: 29 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 588 (1%) |
Incidents, newest first
Minor October 30, 2025 Incident Increased error rate for deployments in United States 1h 35m MIA2, CHI, LAX, NYC and 3 more
Started Oct 30, 2025, 11:21 AM UTC· resolved Oct 30, 2025, 12:57 PM UTC
- identified Oct 30, 2025, 11:21 AM UTC
We've identified and are looking into issues with Increased error rate for deployments in United States.
- resolved Oct 30, 2025, 12:57 PM UTC
This incident has been resolved.
Minor October 28, 2025 Increased error rate for deployments in United States 1h 29m MIA2, CHI, LAX, NYC and 3 more
Started Oct 28, 2025, 12:29 PM UTC· resolved Oct 28, 2025, 01:58 PM UTC
- investigating Oct 28, 2025, 12:29 PM UTC
We are investigating an increased error rate affecting deployments/reinstalls in the United States. This issue only affects new deployments and reinstallation 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 Oct 28, 2025, 01:55 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 28, 2025, 01:58 PM UTC
All services are stable and the issue is considered resolved. If you have questions, please reach out to [email protected].
Minor October 23, 2025 Increased error rate for deployments in SAO PAULO 46m SAO, SAO2
Started Oct 23, 2025, 10:58 PM UTC· resolved Oct 23, 2025, 11:45 PM UTC
- investigating Oct 23, 2025, 10:58 PM UTC
We are currently investigating this issue.
- monitoring Oct 23, 2025, 11:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 23, 2025, 11:45 PM UTC
This incident has been resolved.
Notice October 7, 2025 INCREASED ERROR RATE FOR DEPLOYMENTS, REINSTALL AND POWER-ACTIONS 5h 49m SAO, SP1, MIA2, CHI and 17 more
Started Oct 07, 2025, 06:38 PM UTC· resolved Oct 08, 2025, 12:28 AM UTC
- investigating Oct 07, 2025, 06:38 PM UTC
We are currently investigating an increased error rate impacting deployments, reinstall and power-actions. Our team is actively working to identify the root cause and implement the necessary fixes. We will share updates as more information becomes available.
- monitoring Oct 07, 2025, 11:51 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 08, 2025, 12:28 AM UTC
This incident has been resolved, a post-mortem will be provided soon.
Critical September 29, 2025 Network Outage at Bogotá 37m BGT
Started Sep 29, 2025, 12:49 AM UTC· resolved Sep 29, 2025, 01:26 AM UTC
- investigating Sep 29, 2025, 12:49 AM UTC
We are aware and currently investigating an ongoing outage at Bogotá DC. We apologize for any inconvenience and will provide updates as more information becomes available.
- resolved Sep 29, 2025, 01:26 AM UTC
This incident has been resolved.
Critical September 28, 2025 Power Failure - Buenos Aires 8h 24m BUE
Started Sep 28, 2025, 03:57 PM UTC· resolved Sep 29, 2025, 12:22 AM UTC
- identified Sep 28, 2025, 03:57 PM UTC
We are currently experiencing a large-scale service impact in Buenos Aires. The power provider for the colo company is performing work at the local substation; our infrastructure team is fully engaged and working to restore normal operations. We do not have an ETA yet. We will keep you updated via this status page and through your any support channel you request contact.
- monitoring Sep 28, 2025, 11:28 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 29, 2025, 12:22 AM UTC
This incident has been resolved.
Major September 10, 2025 Increased error rate for US deployments 1h 30m API, Remote access
Started Sep 10, 2025, 07:45 PM UTC· resolved Sep 10, 2025, 09:15 PM UTC
- investigating Sep 10, 2025, 07:45 PM UTC
We are currently investigating this issue.
- resolved Sep 10, 2025, 09:15 PM UTC
This incident has been resolved.
Notice September 5, 2025 Increased error rate for deployments 1h 41m
Started Sep 05, 2025, 11:38 PM UTC· resolved Sep 06, 2025, 01:20 AM UTC
- monitoring Sep 05, 2025, 11:38 PM UTC
Our server deployments have been affected by a global incident in the Canonical (Ubuntu) repositories. The issue was caused by a failure that generated a very large backlog of package and update processing, impacting mirrors and security updates. Deployments should gradually return to normal as the backlog of package processing decreases. We are actively monitoring and will update this status as the situation progresses.
- resolved Sep 06, 2025, 01:20 AM UTC
This incident has been resolved.
Notice August 21, 2025 Connection Instability in São Paulo region 3h 30m SAO, SP1, SAO2
Started Aug 21, 2025, 02:33 PM UTC· resolved Aug 21, 2025, 06:03 PM UTC
- investigating Aug 21, 2025, 02:33 PM UTC
We are currently experiencing intermittent connection issues affecting the São Paulo region. Our team is actively investigating the situation and working to address the issue as quickly as possible. We apologize for any inconvenience and will provide updates as more information becomes available.
- monitoring Aug 21, 2025, 03:10 PM UTC
A routing issue on PTT-IX.br was identified. A fix has been implemented by our Network team, and the connections are stable again. We will keep monitoring for the next hours.
- resolved Aug 21, 2025, 06:03 PM UTC
No further actions were taken. The issue has not happened again since the last interaction.
Notice August 14, 2025 Connection Instability at Dallas region 1h 24m DAL
Started Aug 14, 2025, 08:37 PM UTC· resolved Aug 14, 2025, 10:01 PM UTC
- investigating Aug 14, 2025, 08:37 PM UTC
We are currently investigating this issue.
- identified Aug 14, 2025, 08:49 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 14, 2025, 09:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 14, 2025, 10:01 PM UTC
This incident has been resolved.
Critical July 29, 2025 Incident with Databases and Filesystems 2d 3h Databases, Filesystem
Started Jul 29, 2025, 03:07 PM UTC· resolved Jul 31, 2025, 06:52 PM UTC
- investigating Jul 29, 2025, 03:07 PM UTC
We have identified an issue with our Databases cluster, which has impacted the application availability. Our team is actively working on restoring these services.
- identified Jul 30, 2025, 02:05 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 31, 2025, 06:52 PM UTC
This incident has been resolved.
- postmortem Jul 31, 2025, 06:56 PM UTC
**Impact:** All customer databases in the Dallas region experienced unavailability during this window. No data loss occurred. On July 28th, 2025, the Latitude.sh Databases cluster in our Dallas region experienced a critical failure due to a broader site-level outage. The incident led to the loss of the cluster’s internal state, rendering it unsalvageable. As a result, all customer databases in this region became unavailable. Our engineering team immediately initiated recovery efforts. We provisioned a new environment, redeployed the database control plane, and restored each customer database from off-site backups. After 35 hours of continuous work, services were fully restored. All customer data is safe and accessible. However, configuration-level metadata \(such as trusted sources\) could not be recovered and must be manually recreated. The failure originated from the control plane node pool of the Dallas cluster. The resulting corruption of the cluster’s internal state made it impossible to safely recover or rejoin the remaining nodes. Compounding the issue was the absence of recent control plane snapshots, which limited restoration options. We are conducting a full forensic analysis to determine the root cause of the corruption and evaluate the failover mechanisms that were expected to mitigate such an event. **Impact** * **All databases in Dallas were unavailable for the period** * **All customer data was preserved** and restored to new clusters * **Trusted sources \(firewall rules\)** were lost and must be reconfigured by customers **Immediate Actions Taken** * Isolated the failed cluster to prevent further damage * Deployed a new cluster in Dallas * Restored customer databases from off-site backups * Validated database integrity and access for each tenant **Customer Actions Required** Since all databases were recreated in a new environment, customers **must take the following steps**: 1. **Update Database Connection URIs and Credentials** Your database URI and credentials have changed. Please check your dashboard or reach out to support to retrieve your new connection details. 2. **Recreate Trusted Sources** Any previously configured trusted sources \(firewall allowlists\) were not recoverable and need to be manually re-added. 3. **Review Application Integrations** If you have automated services or applications depending on the old URI or IPs, ensure those are updated to avoid connectivity issues.
Minor July 24, 2025 Network Intermittency at Dallas 8h 41m DAL
Started Jul 24, 2025, 01:43 PM UTC· resolved Jul 24, 2025, 10:25 PM UTC
- identified Jul 24, 2025, 01:43 PM UTC
We are currently experiencing network intermittencies in our Dallas region. Our Network Engineering team is actively investigating the issue and working to implement a solution as quickly as possible. We will provide updates here as more information becomes available. Thank you for your patience and understanding.
- resolved Jul 24, 2025, 10:25 PM UTC
This incident has been resolved.
Minor July 16, 2025 Connection Instability at Tokyo and Singapore regions 8h 30m TYO3, SGP
Started Jul 16, 2025, 12:08 PM UTC· resolved Jul 16, 2025, 08:39 PM UTC
- investigating Jul 16, 2025, 12:08 PM UTC
We are currently experiencing intermittent connection issues affecting the Tokyo and Singapore regions. Our team is actively investigating the situation and working to solve the issue as quickly as possible. We apologize for any inconvenience and will provide updates as more information becomes available.
- investigating Jul 16, 2025, 12:10 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 16, 2025, 01:17 PM UTC
After a review, a change has been applied, and the traffic in both regions has been restored. The issue has happened due to intermittencies in one of our Asia providers.
- resolved Jul 16, 2025, 08:39 PM UTC
This incident has been resolved.
Major July 14, 2025 Incident with API 8m Dashboard, API, Remote access, Automation Tool
Started Jul 14, 2025, 05:27 PM UTC· resolved Jul 14, 2025, 05:35 PM UTC
- identified Jul 14, 2025, 05:27 PM UTC
We have identified an issue with our API cluster which has impacted the application availability.
- resolved Jul 14, 2025, 05:35 PM UTC
This incident has been resolved.
Critical June 28, 2025 LAX2 Outage 5h 27m LAX2
Started Jun 28, 2025, 02:33 PM UTC· resolved Jun 28, 2025, 08:00 PM UTC
- investigating Jun 28, 2025, 02:33 PM UTC
We are currently investigating a major outage affecting all devices in our LAX2 region. Our teams are actively working to identify the root cause and restore services as quickly as possible. We will provide further updates as soon as we have more information. Thank you for your patience.
- resolved Jun 28, 2025, 08:00 PM UTC
This incident has been resolved. A follow up RCA will be sent to the affected customers.