Latitude.sh Outage History

Latitude.sh is up right now

Latitude.sh had 38 outages in the last 2 years totaling 129h 26m of downtime — averaging 1.6 incidents per month.

There were 38 Latitude.sh outages since April 23, 2025 totaling 129h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.latitude.sh

Notice August 21, 2025

Connection Instability in São Paulo region

Detected by Pingoru
Aug 21, 2025, 02:33 PM UTC
Resolved
Aug 21, 2025, 06:03 PM UTC
Duration
3h 30m
Affected: SAOSP1SAO2
Timeline · 3 updates
  1. 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.

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

  3. resolved Aug 21, 2025, 06:03 PM UTC

    No further actions were taken. The issue has not happened again since the last interaction.

Read the full incident report →

Notice August 14, 2025

Connection Instability at Dallas region

Detected by Pingoru
Aug 14, 2025, 08:37 PM UTC
Resolved
Aug 14, 2025, 10:01 PM UTC
Duration
1h 24m
Affected: DAL
Timeline · 4 updates
  1. investigating Aug 14, 2025, 08:37 PM UTC

    We are currently investigating this issue.

  2. identified Aug 14, 2025, 08:49 PM UTC

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

  3. monitoring Aug 14, 2025, 09:14 PM UTC

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

  4. resolved Aug 14, 2025, 10:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2025

Network Intermittency at Dallas

Detected by Pingoru
Jul 24, 2025, 01:43 PM UTC
Resolved
Jul 24, 2025, 10:25 PM UTC
Duration
8h 41m
Affected: DAL
Timeline · 2 updates
  1. 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.

  2. resolved Jul 24, 2025, 10:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2025

Connection Instability at Tokyo and Singapore regions

Detected by Pingoru
Jul 16, 2025, 12:08 PM UTC
Resolved
Jul 16, 2025, 08:39 PM UTC
Duration
8h 30m
Affected: TYO3SGP
Timeline · 4 updates
  1. 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.

  2. investigating Jul 16, 2025, 12:10 PM UTC

    We are continuing to investigate this issue.

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

  4. resolved Jul 16, 2025, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 14, 2025

Incident with API

Detected by Pingoru
Jul 14, 2025, 05:27 PM UTC
Resolved
Jul 14, 2025, 05:35 PM UTC
Duration
8m
Affected: DashboardAPIRemote accessAutomation Tool
Timeline · 2 updates
  1. identified Jul 14, 2025, 05:27 PM UTC

    We have identified an issue with our API cluster which has impacted the application availability.

  2. resolved Jul 14, 2025, 05:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 28, 2025

LAX2 Outage

Detected by Pingoru
Jun 28, 2025, 02:33 PM UTC
Resolved
Jun 28, 2025, 08:00 PM UTC
Duration
5h 27m
Affected: LAX2
Timeline · 2 updates
  1. 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.

  2. resolved Jun 28, 2025, 08:00 PM UTC

    This incident has been resolved. A follow up RCA will be sent to the affected customers.

Read the full incident report →

Minor June 17, 2025

Connection Instability at Asburn region

Detected by Pingoru
Jun 17, 2025, 12:52 PM UTC
Resolved
Jun 17, 2025, 05:58 PM UTC
Duration
5h 5m
Affected: ASH
Timeline · 3 updates
  1. investigating Jun 17, 2025, 12:52 PM UTC

    We are currently experiencing intermittent connection issues affecting the Ashburn region. 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.

  2. monitoring Jun 17, 2025, 01:35 PM UTC

    The issue has been delivered, and a fix has been applied. Connection now is completely reestablished, and no intermittence has been noted since. We will keep monitoring the connection in ASH.

  3. resolved Jun 17, 2025, 05:58 PM UTC

    After the fix applied earlier, no new issues were observed or reported. We apologize for any inconvenience it may have caused.

Read the full incident report →

Minor May 30, 2025

Incident with Support Center

Detected by Pingoru
May 30, 2025, 04:48 PM UTC
Resolved
May 31, 2025, 01:01 AM UTC
Duration
8h 12m
Affected: Dashboard
Timeline · 3 updates
  1. identified May 30, 2025, 04:48 PM UTC

    Creating and seeing support tickets is currently unavailable. We are working to reestablish the service.

  2. identified May 30, 2025, 04:49 PM UTC

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

  3. resolved May 31, 2025, 01:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2025

Slow response times on the API

Detected by Pingoru
May 27, 2025, 12:08 PM UTC
Resolved
May 27, 2025, 07:04 PM UTC
Duration
6h 55m
Affected: DashboardAPIRemote accessAutomation Tool
Timeline · 3 updates
  1. investigating May 27, 2025, 12:08 PM UTC

    We are seeing slow response times with recurring timeouts in the API, which is also affecting the dashboard.

  2. monitoring May 27, 2025, 04:10 PM UTC

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

  3. resolved May 27, 2025, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 19, 2025

Incident with API and Dashboard

Detected by Pingoru
May 19, 2025, 09:27 AM UTC
Resolved
May 19, 2025, 01:21 PM UTC
Duration
3h 54m
Affected: DashboardAPI
Timeline · 3 updates
  1. investigating May 19, 2025, 09:27 AM UTC

    We are investigating an error with our API and Dashboard. 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 May 19, 2025, 10:39 AM UTC

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

  3. resolved May 19, 2025, 01:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2025

[NY] - Increased error rate for deployments

Detected by Pingoru
May 08, 2025, 07:21 PM UTC
Resolved
May 08, 2025, 08:39 PM UTC
Duration
1h 17m
Affected: NYC
Timeline · 4 updates
  1. investigating May 08, 2025, 07:21 PM UTC

    We are currently investigating an increased error rate impacting deployments, reinstalls, and private VLAN assignments. Our team is actively working to identify the root cause and implement the necessary fixes. We will share updates as more information becomes available.

  2. identified May 08, 2025, 08:05 PM UTC

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

  3. monitoring May 08, 2025, 08:06 PM UTC

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

  4. resolved May 08, 2025, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2025

Connection Instability at Tokyo region

Detected by Pingoru
Apr 23, 2025, 02:45 PM UTC
Resolved
Apr 24, 2025, 03:17 PM UTC
Duration
1d
Affected: TYO3
Timeline · 3 updates
  1. investigating Apr 23, 2025, 02:45 PM UTC

    We are currently experiencing intermittent connection issues affecting the Tokyo region. 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.

  2. monitoring Apr 23, 2025, 06:09 PM UTC

    An incident has happened with one of our transit providers (GSL), whose link was unavailable. All DC traffic automatically commuted to our backup links. However, the backup link started to show packet losses for many destinations. After reviewing, we migrated a part of the traffic to another provider, which gradually improved the performance of the site. Currently our link with GSL has returned to its normal. Traffic has balanced through all providers, and the site has recovered its performance.

  3. resolved Apr 24, 2025, 03:17 PM UTC

    This incident has been resolved.

Read the full incident report →