Cigo Tracker incident

Incident: Web Application Outage

Major Resolved View vendor source →

Cigo Tracker experienced a major incident on July 18, 2025 affecting Dispatch Web Platform and Public API and 1 more component, lasting 2h 41m. The incident has been resolved; the full update timeline is below.

Started
Jul 18, 2025, 04:28 PM UTC
Resolved
Jul 18, 2025, 07:10 PM UTC
Duration
2h 41m
Detected by Pingoru
Jul 18, 2025, 04:28 PM UTC

Affected components

Dispatch Web PlatformPublic APIiOSOperator APIAndroidCustomer TrackerNotifications

Update timeline

  1. investigating Jul 18, 2025, 04:28 PM UTC

    Our web application is currently unavailable. We’re actively investigating the cause of the outage. Earlier today, we performed some database changes which have since been reverted. We're currently assessing whether these changes contributed to the issue and working to restore full functionality as quickly as possible. We sincerely apologize for the inconvenience this is causing and appreciate your patience while we work to resolve the problem. Further updates will follow shortly.

  2. monitoring Jul 18, 2025, 05:59 PM UTC

    The web application is now accessible again at https://app.cigotracker.com. We are closely monitoring system performance to ensure stability and confirm that all services are functioning as expected. We were also seeing some issues accessing the Cigo Tracker landing page (https://cigotracker.com), but this was also just reestablished. Thank you for your continued patience. We’ll provide another update once the incident is fully resolved.

  3. resolved Jul 18, 2025, 07:10 PM UTC

    The web application outage has been resolved, and all systems are currently operating normally. While we've successfully isolated the scope of the issue, there are still some contributing factors that remain under investigation. Our team is continuing to analyze the event to determine the full root cause of today's outage and to implement measures that prevent recurrence. We sincerely appreciate your patience and apologize again for the disruption.