Latitude.sh incident

Increased error rate on provisioning actions and VMs

Major Resolved View vendor source →
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 ToolTYO3LONVirtual networkMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMSFRA2SJC2SYD2TYO4

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.

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