Is Fleetio Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

This incident has been resolved.

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

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

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

This incident has been resolved.

Our engineers have identified a system problem that is causing delays for DVIR Defects coming into Fleetio as Issues. We are working with our colleagues at Motive on this and will report back when there is an update.

This incident has been resolved.

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

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

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end.

This incident has been resolved.

Our engineers have identified a system problem that is causing delays for DVIR Defects coming into Fleetio as Issues. We are working with our colleagues at Motive on this and will report back when there is an update.

This incident has been resolved.

We have resolved the issue preventing successful email responses and are working through re-sending a backlog of emails to ensure all customers receive the intended response.

We are currently aware of an issue preventing successful email responses. Our team is investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as we have more information. In the interim, please reach out to our Support Team through Live Chat or Phone for any support inquiries. Thank you for your patience!

This incident has been resolved.

We are currently aware of an issue preventing successful email responses. Our team is investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as we have more information. In the interim, please reach out to our Support Team through Live Chat or Phone for any support inquiries. Thank you for your patience!

This incident has been resolved.

Fleetcor continues to work on backfilling the data. New transactions should be coming in as expected daily, but the historical transactions that would have settled between Dec. 27, 2024 and Jan. 6, 2025 are still not all in Fleetio at this time.

Fleetcor has implemented a fix, but they are still in the process of uploading the backdated transactions. We will provide an update here once those transactions have posted to Fleetio.

Fleetcor has identified the issue with their systems, it is affecting all Fleetcor integration partners. They are currently working on a fix. Estimated completion is Sunday, January 12th.

Our engineers have discovered delays in Fleetcor Transactions posting to Fleetio. It appears to be due to an issue with Fleetcor's systems. We are waiting for Fleetcor to address this issue on their end. Transactions that would have settled between the dates of Dec. 27, 2024 and Jan. 6, 2025 have not yet appeared in Fleetio. We expect these transactions to appear shortly, but they have not posted to Fleetio yet. Transactions that had already settled before Dec. 27 or after Jan. 6 and going forward have all posted to Fleetio properly.

This incident has been resolved.

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

We're currently aware of an issue causing slowness and loading errors in Fleetio's web application. Our team is investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as we have more information. Thank you for your patience!

This incident has been resolved.

We're currently aware of an issue causing slowness and timeout errors in Fleetio's web and mobile applications. Our team is investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as we have more information. Thank you for your patience!

This incident has been resolved.

We're currently aware of an issue causing slowness and timeout errors in Fleetio's web application. Our team is investigating and working to resolve the issue as quickly as possible. We’ll provide updates as soon as we have more information. Thank you for your patience.

This incident has been resolved.

We are continuing to investigate this issue.

Fleetio is currently experiencing slowness and timeout errors on both our web and mobile platforms. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

Users were experiencing issues logging in via username on Web and Fleetio Go. However, our team has resolved the issue and the system should be back to normal performance. We apologize for any inconvenience this may have caused. If you need additional information, please contact our support team at help@fleetio.com.

Our team has identified an issue where users are unable to login using their Usernames on the Web and Fleetio Go app. Logging into Fleetio via an email address or SSO/SAML is still working as intended. We appreciate your patience while our team is working hard to get this resolved and we will keep this page updated with the latest information. We apologize for the inconvenience. If you need additional information, please contact our support team at help@fleetio.com.

Between 9:00 AM and 12:00 PM (CT), a configuration issue with our email security settings caused incoming emails to bounce. Our IT Operations team is actively reviewing logs to identify and address the affected messages. The issue has been resolved, and our email system is now functioning normally.

This incident has been resolved.

We are currently experiencing an outage on our marketing website, Fleetio.com. However, you can still access your account and continue using Fleetio at secure.fleetio.com. We are working to resolve the issue as quickly as possible and appreciate your patience.

Users were experiencing issues integrating new Motive GPS integration within the Fleetio integrations page. However, our product team has resolved this issue and the Motive integration setup should be back to normal. We apologize for any inconvenience this may have caused users when attempting to integrate their Motive GPS devices. If you need additional information, please contact our support team at help@fleetio.com.

Users are currently unable to setup a new Motive GPS Integration within the Fleetio integrations page. We apologize for any inconvenience as we investigate the root cause. Please know our teams are working hard to get this resolved and we will update this page with the latest information. If you need additional information, please contact our support team at help@fleetio.com.

Users who downloaded Fleetio Go version 5.32.0 between 8/14/24 - 8/15/24 on iOS devices were experiencing an error message upon signing into the mobile application. However, our teams have pushed an update to resolve this issue and everything should be back to operational. If you or your staff downloaded the latest update and are experiencing issues after logging in, we recommend uninstalling and reinstalling Fleetio Go, which should resolve the error message. We apologize for any inconvenience this may have caused to our mobile users. If you need additional information, please contact our support team directly at help@fleetio.com.

Users were experiencing issues logging into Auto Integrate. However, our team has resolved the issue and the system should be back to normal performance. We apologize for any inconvenience this may have caused. If you need additional information, please contact our support team at help@fleetio.com.

Users are currently experiencing an error when logging into Auto Integrate. We apologize for the inconvenience. Please know our teams are working hard to get this resolved and we will update this page with the latest information. If you need additional information, please contact our support team at help@fleetio.com.

Fleetio Go users on iOS devices were experiencing session time outs when resuming the mobile app. However, our team has resolved the issue with the recent release of Fleetio Go 5.30.0 within the App Store. We recommend iOS users update to the latest version at their earliest convenience. We apologize for any inconvenience this may have caused our mobile users. If you need additional information, please contact our support team at help@fleetio.com.

Fleetio Go users on iOS devices are currently experiencing session time outs once resuming the mobile app. We apologize for the inconvenience. Please know our teams are working hard to get this resolved and we will update this page with the latest information. As a workaround, we recommend keeping the Fleetio Go app open and not minimized on your device. Or you can always utilize www.fleetio.com directly on your mobile device. If you need additional information, please contact our support team at help@fleetio.com.

Users were experiencing inaccurate widget displays within the Vehicle Overview and Contact Overview pages. However, our team has resolved the issue and the system should be back to normal performance. We apologize for any inconvenience this may have caused. If you need additional information, please contact our support team at help@fleetio.com.

Our team is currently investigating widget displays within the Vehicle Overview and Contact Overview pages. Two of the impacted areas are the Open Issues widget (Vehicle Overview) and the Vehicle Assignments widget (Contact Overview) displaying data that should not appear there. We apologize for this inconvenience this may cause when navigating these Overview pages. In the meantime, we recommend accessing your Issues List and Vehicle Assignments through the left blue menu and filtering as needed. Please know our teams are working hard to get this resolved and we will update this page with the latest information. If you need additional information, please contact our support team at help@fleetio.com.

There was an issue where users were experiencing slowness in completing tasks on Fleetio's website. However, our team has resolved the issue and the system should be back to normal performance. We apologize for any inconvenience this may have caused. If you need additional information, don't hesitate to get in touch with our support team at help@fleetio.com.

Users were experiencing slow completion of tasks on Fleetio's website. However, our team has resolved the issue and is monitoring the results. If you need additional information, don't hesitate to contact our support team at help@fleetio.com. We are very sorry for any inconvenience this may have caused.

Some users are currently experiencing slowness in completing tasks on Fleetio's website. We apologize for the inconvenience. Please know that our teams are working hard to resolve this, and we will update this page with the latest information. If you need additional information, please get in touch with our support team at help@fleetio.com.

This incident has been resolved.

We've identified the problem and have a fix in place.

We are investigating an elevated number of errors to our applications.

We have identified the source of the issues and have implemented a fix. We apologize for any inconvenience.

We are currently investigating degraded performance in the Fleetio application, which is preventing affecting actions like signing in and creating new records. We apologize for the inconvenience and will update this page as soon as more information becomes available.

This incident has been resolved.

We are currently investigating an outage with our 3rd party file hosting provider. This is currently impacting users' ability to upload, view, and download documents and photos as well as the ability to attach photos to inspection items in Fleetio Go. We apologize for the inconvenience and will update this page as soon as more information becomes available.

Filestack services, like viewing documents/photos, exporting files, attaching inspection items in Fleetio Go, retrieving reports, etc. is currently degraded. Our team is investigating and working to resolve the issue as quickly as possible.

This incident has been resolved.

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

Fleetio is investigating a major outage affecting web and mobile applications. We'll update with more information as it becomes available.

This incident has been resolved.

Our search provider has implemented a fix and we are monitoring the results.

Our backend search provider is experiencing an outage. Search on Fleetio, including Shop Directory, is unavailable. The rest of Fleetio continues to work as expected.

Overview: On May 17th, 2023 at 1:04 PM CST, Fleetio experienced a partial outage of our systems. This outage lasted for approximately 30 minutes and impacted all users and services, including the browser app, iOS and Android apps, and the API. The root cause of the issue was a rapid, unexpected increase in blocking events on our database servers, which prevented web requests from completing successfully. Impact: The outage resulted in a significant impact on our users and services. During the event, users experienced major performance degradation and in most cases were unable to access the system altogether. The outage also impacted our API, which prevented users from accessing the system via our mobile apps. Resolution: To resolve the issue, we worked to identify the blocking events, purged them, and performed a restart of all applications. This restored connectivity to our services. We are continuing to investigate the root cause of the blocking events and have implemented additional monitoring and alerting to prevent this issue from recurring. Conclusion: As always, we understand that Fleetio is mission critical for our customers, and that any disruption has a real world impact on their operations. We apologize for any inconvenience caused by this outage and appreciate your patience and understanding as we worked to resolve the issue. We remain committed to providing a reliable and resilient system for our users and will continue to prioritize the ongoing improvement of our processes and systems.

This incident has been resolved.

Service has been restored and we are investigating root cause.

We are investigating an elevated number of errors to our applications.

This incident has been resolved.

The elevated errors have subsided and Fleetio is operating normally. We are continuing to monitor it.

Fleetio is experiencing elevated errors caused by issues within our hosting provider. We have reached out to their support to expedite a resolution. We are continuing to monitor.

**Overview:** On March 10th, 2023 at 12:55 PM CST, Fleetio experienced a complete outage of our systems. This outage lasted for approximately 48 minutes and impacted all users and services, including the browser app, iOS and Android apps, and the API. The root cause of the issue was a failed deployment initiated by our team, which resulted in an interruption to our database services. **Root Cause:** The root cause of the outage was identified as a failed deployment in our Amazon Web Services \(AWS\) instance that was intended to improve internal system configuration. An unexpected error occurred during the deployment process, causing all database connections to fail. As a result, our production systems were unable to connect to these databases and our users were met with error messages when attempting to access Fleetio. **Impact:** The outage resulted in a significant impact on our users and services. During the event, users were completely unable to access Fleetio applications. **Resolution:** To resolve the issue, our team worked to identify the errors which led to the deployment failure. We were able to find the root cause and rolled back these changes. We then performed a comprehensive review of our deployment processes to identify areas for improvement, and to prevent similar incidents from occurring in the future. **Conclusion:** As always, we understand that Fleetio is mission critical for our customers, and that any disruption has a real world impact on their operations.We apologize for any inconvenience caused by this outage and appreciate your patience and understanding as we worked to resolve the issue. We remain committed to providing a reliable and resilient system for our users and will continue to prioritize the ongoing improvement of our processes and systems.

This incident has been resolved. We aim to provide a full breakdown explaining this downtime and what we're doing to prevent similar events in the future in the coming days.

We have identified the cause of the problem and have implemented a fix. We are continuing to monitor the recovery.

Fleetio is currently experiencing an outage that may be preventing users from accessing the system, We are investigating and will follow up with another update soon

This incident has been resolved.

This has been resolved.

There is currently an issue preventing purchase orders from being received. Our team is aware of the issue and we are currently investigating.

This incident has been resolved for all customers and all delayed fuel transaction data has been processed.

The EFS integration has been restored for most customers and we are continuing to monitor the situation. There may be a slight delay in new fuel entries being created while the integration comes back online.

We have identified the issue and we are working on a solution.

We are currently investigating an issue affecting EFS integrations and will update this incident with more information as we receive it.

This incident has been resolved. We're still investigating what caused the outage and provide an update.

The EFS integration has been restored for most customers and we are continuing to monitor the situation. There may be a slight delay in new fuel entries being created while the integration comes back online.

We are continuing to investigate this issue.

We are currently investigating an issue affecting EFS integrations and will update this incident with more information as we receive it.

The incident has been resolved; web performance is operational.

We are investigating reports of a potential outage on the web version of Fleetio.

This incident has been resolved.

We are continuing to monitor for any further issues.

Users were experiencing issues logging into Fleetio. However, this has been resolved and our team is currently monitoring the results. If you need additional information, please contact our support team at help@fleetio.com. We apologize for any inconvenience this may have caused.

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!

This incident has been resolved.

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.

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.

Our Product Team has released a fix to resolve the issue. Users should no longer receive any reference id errors when accessing some vehicle indexes.

Our Product Team sas identified an issue with vehicle indexes producing a reference id error. They are actively working on and testing a fix to be released as soon as possible.

Our Product Team has deployed a fix to production to resolve the Access Denied error page.

Our Product Team is aware and currently investigating users receiving an "Access Denied" message when attempting to edit Work Orders.

Our mobile team has pushed a hotfix out to the App Store for Fleetio Go version 4.8.2.2 for iOS. We recommend all iOS users update to the latest version of Fleetio Go when available for an optimal mobile experience.

Our product team has identified a fix that has entered QA and will be submitted to Apple for approval shortly. We still recommend users with iOS devices take advantage of using www.fleetio.com to complete their inspection forms to ensure the best user experience.

Our product team is actively investigating an issue where inspection items are freezing while completing inspection forms on Fleetio Go version 4.8.3 on iOS devices. We recommend users with iOS devices take advantage of using www.fleetio.com to complete their inspection forms to ensure the best user experience.

The hotfix has passed Apple review and should be published to all iOS users by the end of the day. Please note, app releases can sometimes be delayed by region, so please check your app store later if you do not see the update immediately.

The hotfix has passed Apple review and should be published to all iOS users by the end of the day. Please note, app releases can sometimes be delayed by region, so please check your app store later if you do not see the update immediately.

Fleetio is still awaiting approval from Apple for the Fleetio Go update to become available in the App Store. We still recommend advising users on iOS to utilize fleetio.com on their mobile devices until the hotfix is released and available for download.

A hotfix has been rolled out for the impacted iOS users, and we are only waiting for Apple to complete the update review so that the fix can be published. The hotfix has been awaiting Apple's approval for several hours at this time.

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

An issue has been identified, preventing users from completing inspections where the 'Pass' or 'Fail' confirmation must be selected. Our developer team has been actively working towards a resolution, and we hope to have this solved as soon as possible. As a workaround in the meantime, users can be directed to log inspections through Fleetio.com instead of the Fleetio Go app while this is being fixed. Although not as efficient as using fleetio.com, users can also exit from the "pass/fail" item screen and go back into the inspection item, and it will let them choose an option.

The Motive integration issue affecting DVIR Defect syncing has been resolved

The issue has been identified, we are in progress towards implementing a fix

Fleetio is in contact with Motive (KeepTruckin), which is assisting to identify the issue

Fleetio is investigating some issues affecting some of its KeepTruckin (Motive) integrations. The issue is currently affecting DVIR Defect syncing. We are investigating and will provide updates when we learn more.

On Thursday, May 5th at 1:17 PM CST version 4.7.1 of Fleetio Go on Android was promoted to Production and began to be available for update on Google Play. We received our first customer report of the app crashing on launch on Friday, May 6th at 7:43 AM CST. Upon investigation, we determined that a development build had inadvertently replaced the 4.7.1 release that was originally staged. We then rolled back to the previous working release version 4.7.0 and deployed the hot fix as version 4.7.0.1 which was made available for update on Google Play at 11:40 AM CST. With every release of Fleetio Go we perform rigorous regression testing of the app to ensure problems like these don’t arise. This testing occurred with the 4.7.1 release that was originally prepared for deployment, but a development build inadvertently overwrote the staged build from a developer’s local machine after QA had already occurred. We are taking the following steps to safeguard against these type of scenarios in the future: * Restrict the access in which a build can be uploaded to Google Play for release. * Change our promotion process to take advantage of alpha and beta lanes to ensure the build being tested is what is deployed to production. * Utilize phased rollouts and beta testing groups to ensure app quality with a smaller user base before a release makes it out to all customers. We realize that Fleetio Go is mission critical for our users. We would like to apologize for the adverse effects this outage had on our customers. As always, we'll continue to analyze the events involving this incident and will use these learnings to improve Fleetio.

We've released a hotfix Android version of Fleetio Go via the Google Play Store, version 4.7.7.1, which corrects this issue. Please have you and your team update to this latest version. Please let us know if we can be of further assistance by reaching out to our Support Team at help@fleetio.com Thank you for being so patient while we worked on this resolution!

We've identified an issue in our system that is causing some Android Fleetio Go users to not log in and some Webap users receiving Reference ID error codes. Our Engineers are actively working to correct this. We'll update this page as soon as we have more information. If you have any questions please reach out to our Support Team at help@fleetio.com.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating reports of slow speeds and customers not being able to log into Fleetio. We apologize for the inconvenience and will update this Status Page as soon as we have more information. If you are affected or have any questions, please reach out to our Support Team at help@fleetio.com

Fleetcor has backfilled the data on their servers and the Fleetcor integration is operational again. The last of the data is now flowing into Fleetio and our two systems should be back in sync in a few minutes.

Fleetcor is working on their data services component and they have restored some days of historical fuel history, and these have been imported into Fleetio, but they still have some days that are missing. We will pull these into Fleetio as soon as they are restored in Fleetcor's systems.

Fleetcor's server began having issues yesterday. As such, Fleetcor data has not come into Fleetio since then. We have notified Fleetcor about the issue and they are working on a fix. Once a fix is in place, historical data will flow back into Fleetio and the two systems will re-sync.

Samsara has fixed their application and API's. As such, the Fleetio / Samsara integration is back online.

Samsara's application and API have just gone down. This has caused Fleetio's Samsara integration to stop functioning. You can track the status of this in Samsara's Status tracker here: https://www.samsarastatus.com/incidents/rb58wggy9r00

A fix has been deployed and users can now successfully export and download reports. Thank you for your patience while we worked on a resolution.

We are currently investigating an issue with the exporting of reports. We apologize for the inconvenience and will update this status as we learn more. If you are experiencing this issue or have questions, please reach out to our Support Team at help@fleetio.com

On Thursday, February 24th at 11:33 AM EST we began to notice degraded performance affecting the Fleetio web app, mobile apps, and API. This outage continued until 12:09 PM EST, when all systems returned to normal and users were once again able to access Fleetio. The outage was caused by technical difficulties experienced by our hosting platform. Fleetio, and many other businesses running on the platform were unable to process requests from all sources \(browser, mobile, API\), resulting in users receiving errors. The platform was able to resolve the issue, but unfortunately this took nearly 40 minutes. Our hosting platform is one of the largest in the industry and trusted by several companies across the globe. They have served us well going back to the initial days of Fleetio and have allowed us to ship new features quickly, while maintaining greater than 99.9% uptime. That said, we're currently upgrading our systems to make Fleetio even more robust, and we're working diligently toward minimizing outages and improving uptime. Expect to see improvements soon. We realize that Fleetio is mission critical for our users. We would like to apologize for the adverse effects this outage had on our customers. As always, we'll continue to analyze the events involving this incident and will use these learnings to improve Fleetio.

Our third party hosting platform has marked this incident as fully resolved.

Our third party hosting platform is now reporting they are restoring access. Fleetio customers should now be able to log on to the Fleetio apps. We'll continue to monitor their status page and update our own status page when this incident is fully resolved.

Our third party hosting platform is currently experiencing an outage which is causing Fleetio apps to not load. We apologize for this inconvenience and we will update this status page once the hosting platform has confirmed they are up and running once again.

We have resolved this incident by releasing Android Fleetio Go version 4.5.1 to the Google Play Store. If you have been affected by this issue, please update your device(s) to this latest version. Thank you for your patience while we worked on a resolution and have a great weekend!

We are continuing to work on a fix for this issue. We'll update this Status Page as soon as we release an updated Android version of Fleetio Go with the fix in place. If you are affected or have any questions or concerns, please follow up with our Support Team at help@fleetio.com.

This issue has been identified and we are working on a fix. In the meantime, if you are affected or have any questions or concerns, please follow up with our Support Team at help@fleetio.com.

We are currently investigating an issue on Fleetio Go version 4.5.0 on Android where the app crashes when a user attempt to clock out or stop work on a Work Order in the mobile app. We apologize for this inconvenience and are working to address this issue as soon as possible. If you are affected by this issue or have any questions or concerns, please reach out to our Support Team at help@fleetio.com

The underlying infrastructure is starting to come back online, and Faults and DVIR's are now flowing back into Fleetio as normal. Historical data should be caught up shortly. We will continue to monitor this situation and will post more updates here if any more issues arise.

Today Amazon had a major issue with some of their data centers, and this has caused cascading effects across the Internet. These cascading effects have caused GPS Integrations in Fleetio to lag behind when it comes to importing DVIR's and Engine Faults. We expect these to be fully imported into Fleetio eventually, but they are not currently coming over at the normal pace. We are monitoring the situation and will report updates here. Additionally, information about the underlying issue can be found here: https://status.aws.amazon.com/ https://status.heroku.com/

Filestack has confirmed they are now fully operational. Fleetio Support has also confirmed that documents/photos can now be viewed in our apps. Have a great rest of your day!

Users are experiencing a "503 backend read error" when trying to view, access and/or upload/download photos and documents that are hosted on our third party solution, Filestack. You can view Filestack's Status Page here: https://status.filestack.com/ We'll update this Status Page when Filestack has confirmed their outage is resolved.

This incident has been resolved.

We're experiencing an elevated level of memory errors and are currently looking into the issue.

This incident has been resolved.

We're experiencing an elevated level of memory errors and are currently looking into the issue.

This incident has been resolved.

We're experiencing an elevated level of memory errors and are currently looking into the issue.

A hot fix, version 4.4.2.1 for Android, has been released fixing the issue that some Android users were encountering when opening the app on an older version. If you have been affected by this issue, please update to this latest version. Thank you for your patience while we worked on a resolution! If you have any additional questions or concerns, please contact our Support Team at help@fleetio.com

We've identified an issue that is causing some Android users to not be able to open the new version of Fleetio Go, version 4.4.2. We are working on a hot fix to correct this issue and will update this status page as soon as we have more information. If you have not yet updated to version 4.4.2, please wait until the hot fix is released to the Google Play store to avoid any potential disruption. Please also reach out to our Support Team at help@fleetio.com with any questions or concerns.

This incident has been resolved.

We're experiencing an elevated level of memory errors and are currently looking into the issue.