Is there an Fleetio outage?
Fleetio status: Systems Active
Last checked: 14 seconds ago
Get notified about any outages, downtime or incidents for Fleetio and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 14 seconds ago
Get notified about any outages, downtime or incidents for Fleetio and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Fleetio.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API Docs | Active |
| AutoIntegrate RO Text Notifications | Active |
| Dialpad Telephony Infrastructure: Inbound Calls | Active |
| Dialpad Telephony Infrastructure: Outbound Calls | Active |
| Fleetio Go Mobile Application | Active |
| Fleetio Web Application & API | Active |
| Web Notifications | Active |
| Web Notifications | Active |
| File Storage | Active |
| File Downloads | Active |
| File Storage | Active |
| File Uploads | Active |
| Fuel Card Integrations | Active |
| Comdata Fuel Integration | Active |
| Fleetcor Fuel Integration | Active |
| Wex EFS | Active |
| Wex Fuel Integration | Active |
| GPS Integrations | Active |
| Ford Integration | Active |
| Geotab Integration | Active |
| GPS Trackit Integration | Active |
| KeepTruckin Integration | Active |
| Samsara Integration | Active |
| Verizon Connect Fleet (Telogis) Integration | Active |
| Verizon Connect Reveal (Fleetmatics) Integration | Active |
| Verizon Networkfleet Integration | Active |
| Webfleet Solutions (TomTom) Integration | Active |
| Zubie Integration | Active |
| Hosting Infrastructure | Active |
| CDN/Cache | Active |
| Content Delivery Network | Active |
| DNS Servers | Active |
| Emails | Active |
| Firewall | Active |
| Hosting Platform | Active |
| Legal documents for Fuel and Maintenance Integrations | Active |
View the latest incidents for Fleetio and check for official updates:
Description: On Tuesday, August 24th at 8:43 PM EDT we released Fleetio Go version 4.3.1 for Android. This version contained an oversight which caused users to see outdated information and allowed them to create records that were not visible in the iOS or web apps. This continued until Fleetio Go version 4.3.1.1 for Android was released on August 25th at 11:19 AM EDT and those users upgraded, but lingering issues continued until Friday, August 27th. We’d like to sincerely apologize for any issues this may have caused, and wanted to share with you the events that occurred and the steps we’re taking to mitigate this in the future. ## **Who was affected?** Only users who downloaded Fleetio Go 4.3.1 on Android devices were affected. iOS and web app users were not affected in any way. Ultimately, only a small minority of customer accounts were affected. These users continued to experience issues until upgrading to 4.3.1.1. ## **What happened?** The Fleetio Go version 4.3.1 for Android release was erroneously configured to point to Fleetio’s staging environment, not our production environment. Since our staging server is automatically populated with recent production data for testing purposes, many users were able to successfully log in to Fleetio Go and use it in a seemingly normal way. These users were largely unaware that the data they were viewing was not up to date. Any data created by users was done so on our staging server, not our production server. These new records were then only visible to other users of Fleetio Go 4.3.1 on Android, but no one else. When users began reporting seeing outdated information, we realized the mistake and immediately began taking steps to remediate the issue. We quickly released Fleetio Go 4.3.1.1, which solved the underlying problem. However, since neither Apple \(iOS\) or Google \(Android\) provide native functionality to prevent users from using a specific version, we were left with no choice but to block Fleetio Go traffic to our staging environment. This had the benefit of preventing users from creating more data, but had the downside of essentially locking out users from Fleetio Go with zero explanation. These users were unable to continue using Fleetio Go until they upgraded to 4.3.1.1, but had no way of knowing this. ## **Data recovery** An important goal for us was to ensure our customers were made whole by recovering any data that was added to staging and applying it to production. By the end of the day on Friday, August 27th we were able to recover over 99% of all records that were erroneously created on our staging environment. ## **What will we do to mitigate problems like this in the future?** This ordeal revealed several shortcomings with our Android release processes, and we're taking several steps to mitigate problems of this nature going forward. First, we're adding visibility to our internal app builds when they're not pointing to a production environment. Part of the reason this issue went unnoticed during testing and peer-review is that the current environment is not made explicitly clear during key stages. Going forward our team will always be explicitly aware which environment an app build is configured to consume. We'll also be adding better automated checks to our build process to catch this sort of mistake, ensuring that we're not solely relying on human eyes to catch future problems. Secondly, we'll be adding improved alerts and traffic detection for our non-production environments. We should never have more than a handful of users at a time on staging, adding specific alerts around traffic from Fleetio Go will help spot anomalies. Finally, we'll be adding multiple features to Fleetio Go to allow us to invalidate specific versions and urge users to upgrade. Much of the data loss could have been prevented early on if we had a better way of preventing users from continuing to use Fleetio Go 4.3.1. This is something we'll focus on in the coming days. ## **In conclusion** We realize that Fleetio is mission critical for our users. All of us at Fleetio would like to apologize for the adverse effects this had on our customers. We’ll continue to analyze the events leading up to this incident and will use these learnings to improve our apps and processes. Jorge Valdivia CTO
Status: Postmortem
Impact: None | Started At: Aug. 25, 2021, 2:38 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Aug. 12, 2021, 5:36 p.m.
Description: This incident has been resolved. Thank you for your patience while we worked on this resolution. If you have any further questions, please reach out to the Support Team at [email protected]
Status: Resolved
Impact: Minor | Started At: Aug. 11, 2021, 9:36 p.m.
Description: Last night around midnight, our engineers deployed a set of internal upgrades to Fleetio’s GPS Integrations to enable new types of GPS Integrations in the future. Unfortunately, this introduced a bug that prevented viewing the vehicle detail page for vehicles that had location entries but no native GPS Integration. This morning, we realized the problem and shipped a fix. We are going to add automated testing to prevent this sort of problem with the vehicle details page not loading from happening again. Thank you for your understanding, and we are sincerely sorry for the inconvenience.
Status: Postmortem
Impact: Minor | Started At: Aug. 10, 2021, 12:15 p.m.
Description: We have released a fix for this issue. Thank you for your patience while we worked on this resolution. If you have any questions, please reach out to our Support team at [email protected] Have an excellent weekend!
Status: Resolved
Impact: None | Started At: July 23, 2021, 1:26 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
