Latitude.sh incident

Increased error rate for provisinings

Major Resolved View vendor source →
Started
Mar 17, 2026, 02:23 PM UTC
Resolved
Mar 17, 2026, 06:07 PM UTC
Duration
3h 43m
Detected by Pingoru
Mar 17, 2026, 02:23 PM UTC

Affected components

SAOSP1MIA2CHILAXNYCSYDDALSAN3TYO3LONMEX2ASHBUEBGTFRASAO2SGPLON2LAX2AMSFRA2SJC2SYD2TYO4

Update timeline

  1. investigating Mar 17, 2026, 02:23 PM UTC

    We are investigating an increased error rate affecting provisinings. This issue only affects new provisinings requests. 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 Mar 17, 2026, 02:33 PM UTC

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

  3. investigating Mar 17, 2026, 02:51 PM UTC

    We are currently investigating this issue.

  4. monitoring Mar 17, 2026, 04:47 PM UTC

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

  5. resolved Mar 17, 2026, 06:07 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