All Systems Operational
Eleos Platform
Operational
API
Operational
App Manager
Operational
Mobile Apps
Operational
Telematics Integrations
Operational
Document Delivery
Operational
Document Hub and Drive Axle
Operational
Customer Support
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Oct 7, 2026
No incidents reported today.
Oct 6, 2026
No incidents reported.
Oct 5, 2026
No incidents reported.
Oct 4, 2026
Completed -
The maintenance is complete. We appreciate your understanding and patience as we worked to perform necessary system upgrades.
Oct 4, 06:57 UTC
Oct 4, 06:57 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 4, 05:01 UTC
Oct 4, 05:01 UTC
Scheduled -
In our ongoing and continuous efforts to improve the performance, reliability, and capacity of the services we offer you, we will be performing scheduled maintenance on the Eleos Platform in the coming weeks. On Sunday, October 4, 2026, beginning at 1:00 AM EDT and ending at 3:00 AM EDT (for a total of two hours), we will need to take our systems offline to perform a set of database upgrades.
We work to design and operate systems that, in general, can be maintained and upgraded without a full outage, and we’ve applied regular software updates and made substantive improvements to performance and reliability over the last two years without a scheduled outage. However, the nature of this change requires all Platform activity to be temporarily halted. We are sorry for the impact to your business and drivers this may cause.
During the maintenance period, most Platform features will be unavailable or will exhibit different behavior:
Mobile apps
• The mobile apps will continue to show the load, message, payroll, and truck information last retrieved from the server.
• Trip Planner will show stop locations overlaid on a map, but it will not compute a route for display.
Turn-by-turn guidance will not be able to compute new routes during the maintenance window. Drivers will not be able to start navigation to a new location during this time. Turn-by-turn navigation will continue to provide guidance for drivers who start their turn-by-turn session prior to the maintenance window, but they will not receive an updated route if they deviate from the guided route.
• Workflow actions will behave as though the application is offline: if an offline workflow is defined for the load or stop, it will be used, and workflow actions performed while offline will be queued and sent to your systems after the Platform comes back online. If no offline workflow is defined, the driver will see a brief spinner followed by an error message.
• Messages (chat messages or forms) sent by drivers will be queued on their mobile device and sent after the Platform comes back online. However, workflow actions and messages performed or sent after the maintenance period begins will be lost if the driver logs out before the maintenance period ends. If drivers send messages or perform workflow actions after 1:00 AM EDT, they must stay logged into the device until the maintenance period is complete to ensure no data is lost.
• In-motion locking and duty status information will be handled in the mobile app as though Internet connectivity is not available and duty status is unknown. For more information about how in-motion locking uses duty status, see the In-Motion Locking section of our documentation. Weather information shown on each stop will also fail to load.
• Drivers will remain logged in to the app. If a driver is starting a shift on a shared device, or if they manually log out, they will not be able to log back in until the maintenance is complete.
• If you use the Eleos Geotab integration, your drivers will be able to continue to use the Geotab Drive app normally during the maintenance period, assuming they use the app at least once prior to the start of the maintenance.
• Documents and photographs captured by drivers will be queued on their device and will finish sending upon completion of the maintenance. However, documents and photographs captured by drivers after the maintenance period begins will be lost if the driver logs out before the maintenance period ends. If drivers scan documents after 1:00 AM EDT, they must stay logged into the device until all pending documents display a confirmation number, indicating successful upload.
• Difficult maneuver decisions, added stops, and similar activities will be recorded on each driver’s device and collected as snapshots after the maintenance period ends, at which point these activities will be delivered via your configured trip changes endpoint, if any.
API, App Manager, and Document Hub
• The public APIs at https://platform.driveaxleapp.com/api/v1, including the Action Request, outbound messaging and document retrieval APIs, will return HTTP 503 errors for all requests. These requests can and should be retried as normal, and they will succeed after the maintenance is complete.
• App Manager, including news and media library management, App Configuration, and the Error Console will be inaccessible.
• The Document Hub, including backend user management, the document inbox, document search, and the document review queue will be inaccessible.
Sep 10, 14:14 UTC
We work to design and operate systems that, in general, can be maintained and upgraded without a full outage, and we’ve applied regular software updates and made substantive improvements to performance and reliability over the last two years without a scheduled outage. However, the nature of this change requires all Platform activity to be temporarily halted. We are sorry for the impact to your business and drivers this may cause.
During the maintenance period, most Platform features will be unavailable or will exhibit different behavior:
Mobile apps
• The mobile apps will continue to show the load, message, payroll, and truck information last retrieved from the server.
• Trip Planner will show stop locations overlaid on a map, but it will not compute a route for display.
Turn-by-turn guidance will not be able to compute new routes during the maintenance window. Drivers will not be able to start navigation to a new location during this time. Turn-by-turn navigation will continue to provide guidance for drivers who start their turn-by-turn session prior to the maintenance window, but they will not receive an updated route if they deviate from the guided route.
• Workflow actions will behave as though the application is offline: if an offline workflow is defined for the load or stop, it will be used, and workflow actions performed while offline will be queued and sent to your systems after the Platform comes back online. If no offline workflow is defined, the driver will see a brief spinner followed by an error message.
• Messages (chat messages or forms) sent by drivers will be queued on their mobile device and sent after the Platform comes back online. However, workflow actions and messages performed or sent after the maintenance period begins will be lost if the driver logs out before the maintenance period ends. If drivers send messages or perform workflow actions after 1:00 AM EDT, they must stay logged into the device until the maintenance period is complete to ensure no data is lost.
• In-motion locking and duty status information will be handled in the mobile app as though Internet connectivity is not available and duty status is unknown. For more information about how in-motion locking uses duty status, see the In-Motion Locking section of our documentation. Weather information shown on each stop will also fail to load.
• Drivers will remain logged in to the app. If a driver is starting a shift on a shared device, or if they manually log out, they will not be able to log back in until the maintenance is complete.
• If you use the Eleos Geotab integration, your drivers will be able to continue to use the Geotab Drive app normally during the maintenance period, assuming they use the app at least once prior to the start of the maintenance.
• Documents and photographs captured by drivers will be queued on their device and will finish sending upon completion of the maintenance. However, documents and photographs captured by drivers after the maintenance period begins will be lost if the driver logs out before the maintenance period ends. If drivers scan documents after 1:00 AM EDT, they must stay logged into the device until all pending documents display a confirmation number, indicating successful upload.
• Difficult maneuver decisions, added stops, and similar activities will be recorded on each driver’s device and collected as snapshots after the maintenance period ends, at which point these activities will be delivered via your configured trip changes endpoint, if any.
API, App Manager, and Document Hub
• The public APIs at https://platform.driveaxleapp.com/api/v1, including the Action Request, outbound messaging and document retrieval APIs, will return HTTP 503 errors for all requests. These requests can and should be retried as normal, and they will succeed after the maintenance is complete.
• App Manager, including news and media library management, App Configuration, and the Error Console will be inaccessible.
• The Document Hub, including backend user management, the document inbox, document search, and the document review queue will be inaccessible.
Sep 10, 14:14 UTC
Oct 3, 2026
No incidents reported.
Oct 2, 2026
No incidents reported.
Oct 1, 2026
No incidents reported.
Sep 30, 2026
No incidents reported.
Sep 29, 2026
Resolved -
From September 29th at 12:41 AM UTC to 2:52 AM UTC, a significant portion of drivers using the iOS mobile app experienced crashes while using the app. This affected all versions of the iOS mobile app.
Between 2:52 AM UTC and 3:52 AM UTC, the issue was resolved for the majority of drivers, but a smaller number of drivers continued to experience crashes. By 3:52 AM UTC, the issue was fully resolved for all drivers.
The cause of these crashes stemmed from an upstream service provider that provides mobile app analytics. This provider engaged with the issue by 1:52 AM UTC, leading to a resolution within an hour. The provider is investigating the root cause. We’ll update this page with additional information as further details are provided, but due to the limitations of the status page tool, no notifications will be sent.
---
Updated October 7, 2026, 5:30 PM UTC:
Our upstream analytics provider has shared the results of their investigation and the preventative steps they intend to take.
The incident was caused by the incomplete removal of a configuration flag used by the provider during feature deployments. The provider indicated that this resulted in a one-time crash for iOS users active during the affected time period. While we cannot independently verify that the crash was limited to once per driver in all cases, this aligns with the behavior we observed internally during the incident.
The preventative measures the provider has committed to include the following:
• Releasing an SDK update to harden app-side validation of server data
• Auditing other SDKs for validation weaknesses
• Extending verification steps for similar changes to configuration flags
• Improving phased rollouts of similar changes to limit affected customers during incidents
Although the provider is taking the incident seriously after the fact, we plan to continue our effort, already underway, to move off this provider for analytics and replace them with another offering that better meets our—and your—standards for reliability and quality. This effort will have no outward-facing impact on your mobile app and does not require changes to your systems or integration.
We are sorry for the disruption this incident caused to your drivers and your business. If you have further questions, please reach out to support for assistance.
Sep 29, 00:41 UTC
Between 2:52 AM UTC and 3:52 AM UTC, the issue was resolved for the majority of drivers, but a smaller number of drivers continued to experience crashes. By 3:52 AM UTC, the issue was fully resolved for all drivers.
The cause of these crashes stemmed from an upstream service provider that provides mobile app analytics. This provider engaged with the issue by 1:52 AM UTC, leading to a resolution within an hour. The provider is investigating the root cause. We’ll update this page with additional information as further details are provided, but due to the limitations of the status page tool, no notifications will be sent.
---
Updated October 7, 2026, 5:30 PM UTC:
Our upstream analytics provider has shared the results of their investigation and the preventative steps they intend to take.
The incident was caused by the incomplete removal of a configuration flag used by the provider during feature deployments. The provider indicated that this resulted in a one-time crash for iOS users active during the affected time period. While we cannot independently verify that the crash was limited to once per driver in all cases, this aligns with the behavior we observed internally during the incident.
The preventative measures the provider has committed to include the following:
• Releasing an SDK update to harden app-side validation of server data
• Auditing other SDKs for validation weaknesses
• Extending verification steps for similar changes to configuration flags
• Improving phased rollouts of similar changes to limit affected customers during incidents
Although the provider is taking the incident seriously after the fact, we plan to continue our effort, already underway, to move off this provider for analytics and replace them with another offering that better meets our—and your—standards for reliability and quality. This effort will have no outward-facing impact on your mobile app and does not require changes to your systems or integration.
We are sorry for the disruption this incident caused to your drivers and your business. If you have further questions, please reach out to support for assistance.
Sep 29, 00:41 UTC
Sep 28, 2026
No incidents reported.
Sep 27, 2026
No incidents reported.
Sep 26, 2026
No incidents reported.
Sep 25, 2026
No incidents reported.
Sep 24, 2026
No incidents reported.
Sep 23, 2026
No incidents reported.