Latitude.sh incident

Intermittent deployments on US regions impacting Ubuntu 24/22 and Debian 12

Minor Resolved View vendor source →
Started
Feb 11, 2026, 02:41 PM UTC
Resolved
Feb 11, 2026, 07:53 PM UTC
Duration
5h 12m
Detected by Pingoru
Feb 11, 2026, 02:41 PM UTC

Affected components

MIA2CHILAXNYCDALAutomation ToolASHLAX2

Update timeline

  1. identified Feb 11, 2026, 02:41 PM UTC

    We are currently experiencing intermittent issues with server deployments in US regions. The issue affects Ubuntu 24.04, Ubuntu 22.04, and Debian 12 base images, where user data may not be applied correctly during provisioning. Our team is actively investigating and working on a fix. We will provide updates as the situation progresses.

  2. identified Feb 11, 2026, 02:48 PM UTC

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

  3. identified Feb 11, 2026, 02:53 PM UTC

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

  4. monitoring Feb 11, 2026, 05:40 PM UTC

    The fix has been applied, and we are monitoring the situation.

  5. resolved Feb 11, 2026, 07:53 PM UTC

    This incident has been resolved. All services are operating normally, and the system is stable. Monitoring remains in place to ensure continued reliability.

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