Cigo Tracker incident

Network DNS errors from our hosting provider

Critical Resolved View vendor source →

Cigo Tracker experienced a critical incident on April 1, 2021 affecting Dispatch Web Platform and Public API and 1 more component, lasting 2h 12m. The incident has been resolved; the full update timeline is below.

Started
Apr 01, 2021, 09:55 PM UTC
Resolved
Apr 02, 2021, 12:08 AM UTC
Duration
2h 12m
Detected by Pingoru
Apr 01, 2021, 09:55 PM UTC

Affected components

Dispatch Web PlatformPublic APIiOSRouting and Itinerary OptimizationOperator APIAndroidMapsNotificationsOutbound Email ServiceOutbound SMS Service

Update timeline

  1. identified Apr 01, 2021, 09:55 PM UTC

    Our cloud hosting provider seems to be experiencing some major service disruption. Our team has contacted them and we are actively looking into the service disruption.

  2. identified Apr 01, 2021, 09:56 PM UTC

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

  3. identified Apr 01, 2021, 10:05 PM UTC

    Microsoft Azure, our cloud hosting provider, is currently experiencing a widespread outage affecting our platform, and many others. For more information, you can visit: https://status.azure.com/en-us/status We apologize for the inconvenience, we're waiting for more information and resolution from them.

  4. monitoring Apr 01, 2021, 10:41 PM UTC

    According to the last update issued by the Microsoft Azure engineering team (see: https://status.azure.com/en-us/status), traffic has been rerouted to an alternative DNS. Our services seem to have resumed. We are continuing to monitor the situation, and we will continue to provide updates.

  5. monitoring Apr 01, 2021, 11:15 PM UTC

    Cigo Tracker and its services have recovered according to our monitoring systems. With that said, Microsoft Azure has no fully closed the incident report on their end. We will continue to monitor their infrastructure status updates and we will provide updates accordingly.

  6. resolved Apr 02, 2021, 12:08 AM UTC

    Microsoft Azure has confirmed that the underlying DNS outage has been mitigated.