Latitude.sh incident

Increased error rate on provisioning actions and VMs

Major Resolved View vendor source →

Latitude.sh experienced a major incident on March 18, 2026 affecting API and MIA2 and 1 more component, lasting 1h 32m. The incident has been resolved; the full update timeline is below.

Started
Mar 18, 2026, 07:03 PM UTC
Resolved
Mar 18, 2026, 08:35 PM UTC
Duration
1h 32m
Detected by Pingoru
Mar 18, 2026, 07:03 PM UTC

Affected components

APIMIA2CHILAXNYCSYDDALRemote accessSAN3Automation Tool

Update timeline

  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.