Eleos Technologies Status Page

Sep 29, 2026 · resolved Sep 29

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 21, 2026 · resolved Sep 22

Points-of-interest feature error rates that were elevated between 22:55 UTC to 00:05 UTC, such as truck stop layers and corridor search, are back to normal. If you receive reports of drivers experiencing issues loading points-of-interest within Trip Planner along their route, please submit a ticket with the appropriate urgency set and we'll investigate. We apologize for the interruption this may have caused your drivers or operation.

Jul 16, 2026 · resolved Jul 16

We've processed all delayed documents and new documents are being processed within our target processing time. We're sorry for the disruption. If you see unexpected behavior or remaining issues, please contact support for assistance.

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 [email protected].

Is Eleos Technologies down right now?

No — Eleos Technologies is up. All systems operational as of Oct 12, 4:53 AM UTC.

What is Eleos Technologies's current status?

Eleos Technologies: All Systems Operational. Alert24 checks Eleos Technologies's status page continuously and can notify you the moment it changes.

How do I get alerted when Eleos Technologies goes down?

Alert24 monitors Eleos Technologies and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.