Latitude.sh incident

Increased error rate for deployments and Dallas connectivity

Major Resolved View vendor source →
Started
Mar 04, 2026, 06:05 PM UTC
Resolved
Mar 04, 2026, 07:47 PM UTC
Duration
1h 42m
Detected by Pingoru
Mar 04, 2026, 06:05 PM UTC

Affected components

SAOSP1MIA2CHILAXNYCSYDDALSAN3Automation ToolTYO3LONMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMS

Update timeline

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

  2. investigating Mar 04, 2026, 06:06 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 04, 2026, 06:25 PM UTC

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

  4. resolved Mar 04, 2026, 07:47 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