Eleos Technologies Status Page

Jun 7, 2026 · resolved Jun 7

## Post-incident report \(17 June 2026 15:41 UTC\) From 14:36 UTC to 16:29 UTC on Sunday, June 7, 2026, for a total of one hour and 53 minutes, the Eleos Platform was unable to provide navigation routes to drivers, render trip plans through the API, and show trip plans in Trip Planner Studio in App Manager. Engineering was able to restore routing functionality by 16:29 UTC by applying a mitigation. The mitigation prioritized restoring routing and navigation functionality, but intentionally suppressed current location information from being shown in TPS snapshots and in the `trip_plan.stops.user_navigation_location` property from Trip Plans API calls for routes computed prior to the incident window. Current location information was redirected to an alternate location while the mitigation was applied, so no data was lost. Engineering backfilled approximately half of the entries in TPS snapshots on 2026-06-07 and finished the remaining on 2026-06-08. If trip plans were retrieved via the Trip Plans API endpoints during the time that the backfill was in progress \(2026-06-07 16:28 UTC – 2026-06-08 14:45 UTC\), please pull the snapshot from the API again to have the `trip_plan.stops.user_navigation_location` property populated with corrected data. We immediately store trip snapshots in our database for routing requests to ensure what is shown in Trip Planner Studio and through the Trip Plans API is exactly what was provided to drivers. Unfortunately, the process for storing trip snapshots in the database failed due to a misconfigured database limit for the number of generated routes. This failure resulted in drivers not receiving routes during the incident window \(2026-06-07 14:36 UTC – 2026-06-07 16:29 UTC\). We corrected the misconfiguration that was specific to current location information to resolve the routing outage, but this required us to move new current location information elsewhere. The backfill operation moved all previous current location information from the misconfigured location to the new, correctly configured location. With the completion of this operation, the underlying cause of the incident is now fixed. We understand that routing is a critical 24×7 service for many drivers—if they can’t get a route, they often can’t do their jobs. While reliability and fault tolerance are key design goals for our routing solution, we missed the mark here. We’re sorry for the disruption to your drivers and to your business. Moving forward, we are implementing automated safeguards to prevent this type of database misconfiguration from happening again. ## Update \(8 June 2026 15:47 UTC\) We have completed the backfill of driver current location information for historical trip plans. The driver’s current location will now be displayed in Trip Planner Studio in App Manager on user navigation routes. If trip plans were retrieved via the Trip Plans API endpoints during the time that the backfill was in progress \(6/7/2026 16:28 UTC - 6/8/2026 14:45 UTC\), pull the snapshot from the API again to have the trip\_plan.stops.user\_navigation\_location property populated. If you experience any issues or have questions, please reach out to Eleos Support. We will provide an incident report on the status page once we complete our investigation.

May 28, 2026 · resolved May 28

At this time the login issues seem to be resolved. We apologize again for the inconvenience and if you continue to have problems logging into App Manager please reach out to support@eleostech.com.

May 26, 2026 · resolved May 26

Between 15:55 UTC and 16:16 UTC the Eleos Platform had elevated error rates for the Points of Interest (POI) API. This would have manifested as failing requests to the API for managing POI layers, along with POI layers and icons failing to render in the routing overview screen in the mobile apps. At this time, the error rates have resolved and POI functionality is back to nominal.

May 8, 2026 · resolved May 9

Error rates have remained at normal operating status for POI layers and we've maintained our extra server capacity throughout this time with no fluctuations. Drivers can expect to see POI layers loading in the mobile apps, and our API for managing POIs and POI layers are functioning as normal.

May 8, 2026 · resolved May 8

Error rates for POI layers have dropped and the Eleos Platform is operating as normal.