Fleetio experienced a critical incident on August 23, 2022 affecting Fleetio Web Application & API and Fleetio Go Mobile Application, lasting 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 23, 2022, 11:33 PM UTC
At 6:16 PM Central Time, our automated system monitoring alerted us that our servers were not handling requests properly. Investigation revealed that our service provider's DNS has stopped responding. This is one of the largest hosting providers in the country, and they are having a major outage. You can read more about this incident here: https://status.heroku.com/incidents/2453 We will update this thread as we learn more.
- monitoring Aug 24, 2022, 12:24 AM UTC
Our service provider has still not been able to implement a solution, it appears the problem is at a significantly lower level in the internet infrastructure with DNS resolution as a number of different types of services have been impacted. That said, our engineers have implemented a temporary workaround though to get Fleetio back online so that you can resume using the application. We will continue monitoring this situation.
- resolved Aug 24, 2022, 12:26 AM UTC
This incident has been resolved.
- postmortem Aug 24, 2022, 03:35 PM UTC
At 7:58 PM Central Time last night, our hosting provider implemented a fix in their systems as well. You can read more about it here: [https://status.heroku.com/incidents/2453](https://status.heroku.com/incidents/2453) We are truly sorry this DNS system problem cascaded into our platform and caused downtime for Fleetio. Thank you for being a Fleetio customer!