Eleos Technologies Outage History

Started Sep 29, 2026, 12:41 AM UTC· resolved Sep 29, 2026, 05:30 PM UTC

1. resolved Sep 29, 2026, 03:21 PM UTC

   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.

Read the full incident report →

Started Sep 21, 2026, 11:18 PM UTC· resolved Sep 22, 2026, 12:46 AM UTC

1. investigating Sep 21, 2026, 11:18 PM UTC

   Beginning at 19:32 UTC the error rate for requesting points of interest data within the Eleos Platform increased making points of interest searches within the App's Trip Planner to fail, and POI API requests to not succeed. No other aspects of the Eleos Platform are affected at this time. We are current investigated this elevated error rate, and will post an update to this incident in the next 20 minutes.

2. investigating Sep 21, 2026, 11:41 PM UTC

   We are continuing to see elevated error rates across POI specific features of the Eleos Platform, and are still actively investigating the root cause of the errors. We will post another update in 20 minutes.

3. investigating Sep 22, 2026, 12:01 AM UTC

   We are continuing to see elevated error rates across POI specific features of the Eleos Platform, and are still actively investigating the root cause of the errors. We will post another update in 20 minutes.

4. investigating Sep 22, 2026, 12:22 AM UTC

   Error rates for POI specific features have improved, but we are still actively investigating the root cause of the errors. We will post another update in 20 minutes.

5. resolved Sep 22, 2026, 12:46 AM UTC

   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.

Read the full incident report →

Started Jul 16, 2026, 12:23 PM UTC· resolved Jul 16, 2026, 12:31 PM UTC

1. monitoring Jul 16, 2026, 12:23 PM UTC

   Document processing times are increased and documents are currently delayed by about 30 minutes. We've mitigated the underlying issue and we are nearly done processing the queue of delayed documents. We'll post another update when the remaining backlog is fully processed.

2. monitoring Jul 16, 2026, 12:23 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jul 16, 2026, 12:31 PM UTC

   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.

Read the full incident report →

Started Jun 07, 2026, 02:53 PM UTC· resolved Jun 07, 2026, 07:34 PM UTC

1. investigating Jun 07, 2026, 02:53 PM UTC

   The error rate for certain Platform actions is elevated. We’re investigating the cause and impact and will provide details as soon as possible.

2. investigating Jun 07, 2026, 03:26 PM UTC

   We are continuing to investigate the issue. We are experiencing issues generating routes in the mobile app and will update as we learn more.

3. identified Jun 07, 2026, 03:57 PM UTC

   We have identified the issue and are working with Senior Engineering to apply a mitigation. We expect to resolve the issue in an about an hour and will continue to provide updates.

4. identified Jun 07, 2026, 04:28 PM UTC

   We are continuing to work on a mitigation for routing issues.

5. monitoring Jun 07, 2026, 04:39 PM UTC

   We applied a fix for the routing issue an have confirmed that routes are now generating. The mitigation has an impact to the display of the driver's current location in historical trip snapshots. We will follow up with additional details about this impact shortly.

6. monitoring Jun 07, 2026, 04:47 PM UTC

   We are now working on a fix to restore visibility of the driver's current location in historical trip snapshots. There was no data loss during the incident and new routes will continue to display the current location information. We will also continue to monitor the original mitigation.

7. resolved Jun 07, 2026, 07:34 PM UTC

   We are working through backfilling data affected by this issue. At the moment, it may not be possible to see the starting location of the driver, indicated by an orange pin on user navigation routes, in historical trip plans in Trip Planner Studio in App Manager, or via the trip_plan.stops.user_navigation_location property in the Trip Plans API endpoints. We will continue to backfill data into the upcoming week and we will post a post mortem to the status page once the backfill is complete.

8. postmortem Jun 08, 2026, 03:36 PM 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.

Read the full incident report →

Started May 28, 2026, 06:06 PM UTC· resolved May 28, 2026, 06:37 PM UTC

1. investigating May 28, 2026, 06:06 PM UTC

   We are currently investigating issues while logging into the App Manager, these issues started around 17:45 UTC. We apologize for this disruption and are working on a mitigation now.

2. monitoring May 28, 2026, 06:10 PM UTC

   We have applied a mitigation which seems to have resolved the login issues, if you continue to encounter problems logging into App Manager please reach out to [email protected].

3. resolved May 28, 2026, 06:37 PM UTC

   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].

Read the full incident report →

Started May 26, 2026, 03:55 PM UTC· resolved May 26, 2026, 04:16 PM UTC

1. resolved May 26, 2026, 04:34 PM UTC

   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.

Read the full incident report →

Started May 08, 2026, 09:04 PM UTC· resolved May 09, 2026, 12:02 AM UTC

1. identified May 08, 2026, 09:04 PM UTC

   We are currently investigating elevated error rates for our Point of Interest (POI) API. This will manifest 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. Server capacity has appeared to drop down again and we're working on an alternate mitigation.

2. identified May 08, 2026, 09:37 PM UTC

   We are working on shifting our POI layer workload to different infrastructure. Error rates are fluctuating for POI layers due to misbehaving server instances, but we're continuing to work towards a stable solution.

3. monitoring May 08, 2026, 10:15 PM UTC

   Error rates have stabilized to normal operating levels for POI layers, but we're going to continue to monitor out of an abundance of caution. We are working with our infrastructure provider to ensure the needed server capacity remains available to us.

4. monitoring May 08, 2026, 11:43 PM UTC

   We are continuing to monitor out of an abundance of caution, but will look to resolve the incident soon. We have been successfully running with expanded and sustained server capacity to mitigate any further issues. We are in active contact with our infrastructure provider to prevent a reoccurrence.

5. resolved May 09, 2026, 12:02 AM UTC

   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.

Read the full incident report →

Started Apr 03, 2026, 06:28 PM UTC· resolved Apr 03, 2026, 07:06 PM UTC

1. investigating Apr 03, 2026, 06:28 PM UTC

   We are currently investigating possible delays in message notifications to drivers, and delays in integrating messages from drivers to messaging services. We will provide an update in 20 minutes.

2. monitoring Apr 03, 2026, 06:46 PM UTC

   Message notifications are no longer delayed as of 18:32 UTC. Notifications were delayed between the period of 18:09 UTC and 18:31 UTC. Upon further investigation, messages integrated to messaging services were not delayed. Only message notifications to drivers - including new messages and updating message counts on app icons were delayed during the incident period.

3. resolved Apr 03, 2026, 07:06 PM UTC

   We have identified the cause of the notification delay, and are continuing to see notifications processed normally. Notifications were delayed between the period of 4/3/2026 18:09 UTC and 4/3/2026 18:31 UTC for a total period of 22 minutes.

Read the full incident report →

Started Mar 12, 2026, 12:12 AM UTC· resolved Mar 12, 2026, 12:33 AM UTC

1. monitoring Mar 12, 2026, 12:12 AM UTC

   Beginning at 23:59 UTC errors rates across the Eleos Mobile Platform, and have decreased to normal rates at 00:09 UTC. We are currently monitoring the system, and will provide an update in 20 minutes.

2. resolved Mar 12, 2026, 12:33 AM UTC

   Error rates have remained stable as the system started to recover at 20:05 UTC. Elevated errors rates across the Eleos Platform lasted for approximately 10 minutes between 23:59 UTC and 00:09 UTC. Platform API request made during this period may have experienced a 500 HTTP response, and mobile apps may have temporary experienced delays in sending any data produced on device, but that data would've been queued and sent along normally within incident the period or shortly there after. Please reach out to Eleos support at [email protected] if you have any questions or concerns about this incident.

Read the full incident report →

Started Jan 29, 2026, 08:23 PM UTC· resolved Jan 29, 2026, 08:54 PM UTC

1. investigating Jan 29, 2026, 08:23 PM UTC

   We are currently investigating delays with document delivery.

2. identified Jan 29, 2026, 08:41 PM UTC

   We have identified the issue and applied a fix, document processing times are starting to resolve.

3. resolved Jan 29, 2026, 08:54 PM UTC

   As of 20:44 UTC document delivery times have returned to normal. Please reach out to support if you have any questions or concerns: [email protected]. We apologize for the inconvenience.

Read the full incident report →

Started Jan 23, 2026, 03:30 PM UTC· resolved Jan 23, 2026, 04:12 PM UTC

1. investigating Jan 23, 2026, 03:30 PM UTC

   We are currently investigating an issue with the Build a New Route feature inside of App Manager that prevents building routes using a pluggable router engine. We do not suspect at this time that this is affecting routes for drivers in the mobile app.

2. investigating Jan 23, 2026, 03:47 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 23, 2026, 03:55 PM UTC

   We have confirmed that Pluggable Routing on the mobile app remains unaffected by that this issue, and that Build A New Route for pluggable routing still remains the only affected issue.

4. resolved Jan 23, 2026, 04:12 PM UTC

   We have confirmed this issue has been fixed, you can now generate routes in Build a New Route using pluggable router engines. Please reach out to our support team if you have any questions or concerns: [email protected]

Read the full incident report →

Started Jan 10, 2026, 10:24 PM UTC· resolved Jan 10, 2026, 11:05 PM UTC

1. investigating Jan 10, 2026, 10:24 PM UTC

   We are currently investigating elevated error rates for the Eleos Platform as of 22:02 UTC. Error rates are currently between 8% and 15%. During this time period with the elevated error rates, the mobile apps may briefly fall back to offline mode and will retry any requests that were queued. Document upload, processing, and delivering messages to customers web services are unaffected.

2. resolved Jan 10, 2026, 11:05 PM UTC

   Error rates have returned to normal operating levels. Between 22:02 UTC and 22:33 UTC a server became unhealthy and stopped responding to requests which resulted in a brief 15% error rate spike which quickly dropped to an 8% error rate across the platform. A new server automatically provisioned and the error rate returned to normal operating levels. During this time, mobile apps would have experienced intermittent connectivity issues and would have retried requests. Some mobile apps may have briefly fallen back into offline mode and then returned to normal online functionality. App Manager requests may have intermittently failed but succeeded on subsequent attempts. Correction made to previous update: elevated error rate started at 22:02 UTC.

Read the full incident report →

Started Jan 06, 2026, 04:17 PM UTC· resolved Jan 06, 2026, 05:41 PM UTC

1. monitoring Jan 06, 2026, 04:17 PM UTC

   Platform Metrics in App Manager are failing to load for users during this time due to an issue with an upstream provider. We're monitoring and will post updates as we receive them from our provider.

2. monitoring Jan 06, 2026, 05:02 PM UTC

   We are continuing to monitor as we await for more updates from our upstream provider at this time.

3. monitoring Jan 06, 2026, 05:24 PM UTC

   Platform Metrics in App Manager seem to be loading now for some users as our upstream provider have indicated that they have deployed a fix and are monitoring the rollout. We'll continue to provide more updates as we receive them.

4. resolved Jan 06, 2026, 05:41 PM UTC

   Our upstream provider has indicated this issue has been resolved, and we're seeing Platform Metrics successfully load in App Manager.

Read the full incident report →

Started Dec 17, 2025, 05:00 PM UTC· resolved Dec 17, 2025, 05:40 PM UTC

1. investigating Dec 17, 2025, 05:00 PM UTC

   Beginning at 16:21 UTC creating an Action Request via the Action Request API resulted in an error and the requested Action Request was not created. We are currently investigating the errors, and will provide an update at 17:20 UTC.

2. monitoring Dec 17, 2025, 05:18 PM UTC

   We have identified the root cause of the issue, and have rolled back the changes that caused them. As of 17:15 UTC the error rate of the Action Request API has returned to normal. Correction to the previous update: the elevated errors of the Action Request API began at 16:21 UTC. We are continuing to monitor the error rates, and will provide an update at 17:40 UTC.

3. resolved Dec 17, 2025, 05:40 PM UTC

   The error rates for the Action Request API has remained normal since 17:15 UTC. This incident has been resolved. The period of interruption was between 16:21 UTC and 17:15 UTC for an outage time of 54 minutes. During this time PUT requests to create new Action Requests resulted in a HTTP 500 error response, and the requested Action Request was not created.

Read the full incident report →

Started Dec 12, 2025, 09:45 PM UTC· resolved Dec 12, 2025, 10:16 PM UTC

1. monitoring Dec 12, 2025, 09:45 PM UTC

   From 12/12/2025 21:21 UTC to 12/12/2025 21:32 UTC our monitoring indicated DNS resolution issues when trying to contact Eleos's servers. We've traced this to an issue with our upstream DNS provider. Mobile app users and back office users may have seen intermittent delays loading information and performing actions in the app or in the Hub during this time window. Some users may not have been impacted at all depending on the configuration of their local DNS cache. Our monitoring indicates this is resolved and we are continuing to monitor. We are waiting on final confirmation from our upstream vendor that the issue is resolved.

2. resolved Dec 12, 2025, 10:16 PM UTC

   Our monitoring has continued to indicate the issue has been resolved. Our upstream vendor has also since confirmed the issue has been resolved. Please reach out to our support team at [email protected] if you have any questions or issues.

Read the full incident report →

Started Nov 07, 2025, 12:31 AM UTC· resolved Nov 07, 2025, 01:03 AM UTC

1. investigating Nov 07, 2025, 12:31 AM UTC

   We are investigating potential issues affecting the document processing. Our on-call team is engaged and will provide an update shortly.

2. investigating Nov 07, 2025, 12:44 AM UTC

   Document processing performance should no longer be degraded. We are continuing to monitor and investigate this issue.

3. resolved Nov 07, 2025, 01:03 AM UTC

   This incident has been resolved. We are continuing to monitor document processing.

Read the full incident report →

Started Oct 20, 2025, 01:07 PM UTC· resolved Oct 20, 2025, 08:34 PM UTC

1. investigating Oct 20, 2025, 01:07 PM UTC

   We are investigating potential issues with retrieving POIs in the Eleos mobile app. Our on-call team is engaged and will provide an update shortly.

2. identified Oct 20, 2025, 01:41 PM UTC

   We've identified the issue affecting the mobile app. A portion of POI layers and pin move recommendations will not load in the mobile app. The rest of the app will continue to function as normal, including trip planning features such as adding non-POI stops, routing, and navigation. We're working to mitigate the issue and will update again by 10 AM EDT.

3. identified Oct 20, 2025, 02:13 PM UTC

   The issue affecting POI retrieval and pin move recommendations stems from issues with an upstream provider. Additionally, these issues are now affecting document delivery, which is currently delayed. Any delayed documents are stored and delivery will be retried when the service issue has been resolved. We're continuing to evaluate potential mitigations and will update again by 10:45 AM EDT.

4. identified Oct 20, 2025, 02:48 PM UTC

   We're continuing to investigate mitigations for document delivery and POI layer issues. We'll update again by 11:15 AM EDT.

5. identified Oct 20, 2025, 03:23 PM UTC

   Our upstream provider is still working to resolve the underlying issue. We're continuing to investigate mitigations for document delivery and POI layer loading. We have confirmed that while document delivery is delayed, documents are being delivered within 60 minutes. Additionally, we have observed a delay in message delivery. We're investigating this and will provide more details. We'll provide another update by 11:50 AM EDT.

6. identified Oct 20, 2025, 03:53 PM UTC

   After investigating a potential message delivery issue, we have determined that we are successfully delivering messages and that it is not affected by the other issues. Document delivery and POI layer loading are both still affected. Documents continue to be delivered within 60 minutes of sending. We're continuing to investigate mitigation options while the upstream provider works on the underlying issue. We'll post another update by 12:20 PM EDT. Please note that this status page appears to be affected by the ongoing issues and updates may be delayed as a result.

7. identified Oct 20, 2025, 04:36 PM UTC

   Our upstream provider is continuing to resolve the underlying issue, which is manifesting in our systems as reduced computing capacity. We continue to process documents at a reduced rate; at this time, we are delivering all documents within 90 minutes of sending, and most within an hour of sending. POI layer loading is still operating at a degraded level. We are still investigating and preparing mitigation options. We'll post another update by 1:15 PM EDT.

8. identified Oct 20, 2025, 05:19 PM UTC

   Our upstream provider is currently in the process of validating a fix for their capacity issues . We continue to process documents at a reduced rate; at this time, we are delivering all documents within 90 minutes of sending, and most within an hour of sending. POI layer loading is still operating at a degraded level. We'll post another update by 1:45 PM EDT.

9. identified Oct 20, 2025, 05:57 PM UTC

   Our upstream provider is applying a mitigation and reports seeing an early indication of improvements. These improvements have not yet had an effect on the Eleos Platform, but we're continuing to monitor and work on a fallback mitigation. Document delivery and POI layers are still affected with degraded performance. We'll provide another update by 2:30 PM EDT

10. identified Oct 20, 2025, 06:33 PM UTC

    We're continuing to prep our fallback mitigation while our service provider works on fixing the underlying issue. We're still seeing documents delivered with delays, as well as degraded POI layer loading. Other areas of the mobile apps continue to be unaffected. We'll share another update by 3:15 PM EDT.

11. monitoring Oct 20, 2025, 07:00 PM UTC

    Our upstream provider has applied their mitigation and we're now seeing significant improvements in document processing times. Our systems are currently working through the backlog of pending document deliveries. POI layer loading is not yet improved. We'll continue to monitor as we catch up with the document delivery backlog and provide another update by 3:30 PM EDT.

12. monitoring Oct 20, 2025, 07:35 PM UTC

    Our document delivery system is continuing to catch up with its backlog. POI layers is continuing to have issues loading in the mobile app. We're continuing to monitor and we'll provide another update by 4:05 PM EDT.

13. monitoring Oct 20, 2025, 08:05 PM UTC

    We're continuing to work through the document delivery backlog. POI layers are continuing to have issues loading in the mobile app. We're continuing to monitor and we'll provide another update by 4:35 PM EDT.

14. monitoring Oct 20, 2025, 08:20 PM UTC

    Our document delivery backlog has caught up and we're processing incoming documents at a normal rate. We're continuing to monitor delivery times to ensure they've returned to normal durations. POI layer loading and pin move recommendation issues have resolved. Drivers should not see errors when loading POI layers in the mobile app. We'll provide another update by 4:40 PM EDT for document delivery as that continues to return to normal operation.

15. resolved Oct 20, 2025, 08:34 PM UTC

    We've confirmed that documents are being delivered within normal durations. Other areas of the mobile app and App Manager are operating normally. We apologize for the disruption in service. If you have further concerns, please reach out at [email protected].

Read the full incident report →

Started Oct 20, 2025, 09:47 AM UTC· resolved Oct 20, 2025, 10:34 AM UTC

1. monitoring Oct 20, 2025, 09:47 AM UTC

   The Eleos Platform experienced degraded performance beginning at 7:42 UTC. App users who were logged in were unable to receive or send messages, or receive Action Requests. Messages produced on the app during this time were held on device until the error rates were reduced. Document processing during this time was also delayed. Documents captured on device will be uploaded and processed once the error rates have subsided. The Messaging and Action Request API were also unavailable. We are starting to see full restoration of functionality as of 9:22 UTC, and will continue to monitor the issue and will provide an update at 10:15 UTC.

2. monitoring Oct 20, 2025, 10:16 AM UTC

   As of 9:22 UTC we believe the Eleos Platform has stabilized and full functionality has been restored. The outage period was between 7:42 UTC and 9:22 UTC (for a total outage time of 1 hour and 40 minutes). Messages sent on device during this period will have been integrated once the system was restored. We are investigating document processing difficulties during the outage period, and will post an update by 10:45 UTC.

3. resolved Oct 20, 2025, 10:34 AM UTC

   Documents uploaded during the outage period (between 7:42 and 9:22) were processed, and made available via the Document API by 9:54 UTC. The system has stabilized and full functionality has been restored. Please reach out to [email protected] if you experience any abnormalities with the Eleos Platform.

Read the full incident report →

Started May 29, 2025, 01:51 PM UTC· resolved May 29, 2025, 11:42 PM UTC

1. resolved May 29, 2025, 01:51 PM UTC

   Between 11:54 AM EDT and 7:42 PM EDT yesterday, May 28th, emails sent to our primary support address, [email protected], were not received and did not create support tickets. If you sent an email to [email protected] during this time, please resend the email. You would have received an error email with the subject "Delivery Status Notification (failure)" in reply to your message. Any tickets opened via the support portal were not impacted. We're very sorry for the disruption this issue has caused for your business.

Read the full incident report →

Started May 05, 2025, 02:34 PM UTC· resolved May 05, 2025, 03:54 PM UTC

1. investigating May 05, 2025, 02:34 PM UTC

   We are currently investigating an issue with drivers not being able to receive routes at this time.

2. monitoring May 05, 2025, 02:51 PM UTC

   Routing functionality with an upstream provider has been restored and we're seeing routing success rate increase. We will be monitoring to make sure that drivers are able to receive new routes in the mobile apps, and the Build a Route functionality in Trip Planner Studio will continue to function.

3. monitoring May 05, 2025, 02:56 PM UTC

   Routing success rates appear to be stable and under normal operating conditions, but we are continuing to monitor.

4. monitoring May 05, 2025, 03:19 PM UTC

   Routing success rates still appear to be stable and under normal operating conditions, but we are continuing to monitor at this time.

5. resolved May 05, 2025, 03:54 PM UTC

   Routing success rates have remained stable and under normal operating conditions. The upstream provider has acknowledged the issue on their side and has indicated the issue has been resolved on their end.

6. postmortem May 22, 2025, 06:22 PM UTC

   On May 5, 2025, our engineering team was paged for elevated error rates that exceeded normal operational thresholds. These errors stemmed from our routing service provider unexpectedly rate-limiting our requests. This caused Trip Planner and route requests originating from our mobile applications to fail. This also affected Trip Planner Studio’s Build a New Route requests made via the App Manager. The vast majority of route requests failed from 14:16 UTC to 14:48 UTC. Upon investigation and communication with the external provider, it was determined that the rate-limiting was the result of the deployment of a malformed configuration by the provider and was not the result of our usage patterns or volume, which remained normal. Routing functionality was restored at 14:48 UTC. As a precautionary measure, we waited to resolve the status page incident until 15:54 UTC when we confirmed that the routing provider had identified the underlying cause of the outage and did not expect a reoccurrence.

Read the full incident report →

Started Apr 30, 2025, 07:20 PM UTC· resolved Apr 30, 2025, 08:08 PM UTC

1. identified Apr 30, 2025, 07:20 PM UTC

   We have identified an issue preventing the Eleos Platform Metric charts from rendering within App Manager. It appears, at this time, our vendor for rendering these charts is experiencing an outage.

2. identified Apr 30, 2025, 07:20 PM UTC

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

3. identified Apr 30, 2025, 07:42 PM UTC

   We have confirmed this issue is due to an outage from our vendor, and we are currently in direct communication with them. We will provide another update within 30 minutes or as soon as we receive more information from our vendor.

4. monitoring Apr 30, 2025, 07:48 PM UTC

   Our vendor has indicated that the issue has been resolved, and we have observed that the Eleos Platform Metrics are now rendering and functional. If you are still experiencing issues, please reach out to our support team at [email protected].

5. resolved Apr 30, 2025, 08:08 PM UTC

   The Eleos Platform Metrics seem to be fully functional at this point, again, if you continue to experience any issues rendering these charts please reach out to support at [email protected].

Read the full incident report →

Started Apr 28, 2025, 04:02 PM UTC· resolved Apr 28, 2025, 04:26 PM UTC

1. identified Apr 28, 2025, 04:02 PM UTC

   We are currently experiencing delays in messages being sent from the driver to customer backend services. No message information is being lost during this time. We are still successfully processing and delivering messages but are working to mitigate a growing backlog of message that are causing delays.

2. identified Apr 28, 2025, 04:15 PM UTC

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

3. resolved Apr 28, 2025, 04:26 PM UTC

   The issue is resolved and we are no longer seeing message delays. No message information was lost during this time. We are continuing to monitor our message backlog and ensure messages are no longer being delayed but it is currently stable.

Read the full incident report →

Started Apr 16, 2025, 02:28 PM UTC· resolved Apr 16, 2025, 08:03 PM UTC

1. investigating Apr 16, 2025, 02:28 PM UTC

   We are investigating a delay in the delivery time of transactions. Our on-call team is engaged and will provide an update shortly.

2. investigating Apr 16, 2025, 02:56 PM UTC

   We have identified the cause of the issue and are working on a mitigation.

3. investigating Apr 16, 2025, 03:29 PM UTC

   We are continuing to work on applying the mitigation and will notify once complete.

4. monitoring Apr 16, 2025, 04:07 PM UTC

   We are currently monitoring our backlog of messages. Messages are being processed and we are working through a large backlog that has been queued.

5. monitoring Apr 16, 2025, 04:41 PM UTC

   We are monitoring our sub-system for sending messages from the driver to customer backend services. We are successfully integrating messages at this time to customer backend web services but we are currently working through the backlog of messages that we do have. No message information has been lost during this time. We will continue to monitor until we have successfully integrated all messages in our queue.

6. monitoring Apr 16, 2025, 05:14 PM UTC

   We are continuing to monitor messages being sent from the driver to customer backend services. As we continue to work through the backlog of messages, we are also implementing mitigations to increase the system's ability to work through the backlog faster. Still no message information has been lost during this time.

7. monitoring Apr 16, 2025, 05:54 PM UTC

   We are continuing to monitor messages being sent from the driver to customer backend services. Still no message information has been lost during this time as we work through our backlog of messages. Workflow actions have not been impacted during this time. We are successfully processing and delivering messages and are seeing our backlog decrease steadily.

8. monitoring Apr 16, 2025, 06:28 PM UTC

   We are still monitoring messages being sent from the driver to customer backend services. No message information has been lost and workflow actions have not been impacted. We are continuing to see a decrease in the backlog and working on solutions to get through the backlog faster.

9. monitoring Apr 16, 2025, 06:56 PM UTC

   We have completed processing all messages in our backlog. We will continue to monitor the backlog to ensure the queue is stable and messages are no longer being delayed.

10. monitoring Apr 16, 2025, 07:31 PM UTC

    We remain caught up on our backlog of messages. We are assessing if all messages that were cleared from the backlog have been fully integrated. At this time it appears so, but we want to confirm using a separate source of data.

11. resolved Apr 16, 2025, 08:03 PM UTC

    Messages integrated successfully and the message backlog remains stable.

Read the full incident report →

Started Apr 15, 2025, 06:24 PM UTC· resolved Apr 15, 2025, 06:42 PM UTC

1. investigating Apr 15, 2025, 06:24 PM UTC

   Our monitoring indicates a significant drop in route requests beginning around 16:33 UTC. We’re investigating and will provide more information on impact as soon as possible. It is not yet clear if the problem is affecting end users or if the problem is with our monitoring, but we will clarify shortly.

2. monitoring Apr 15, 2025, 06:28 PM UTC

   We've identified this is a problem with our monitoring, and that routing is working normally across the Platform. Thank you for your understanding on the false alarm—we try to err on the side of notifying on the status page in cases where there's uncertainty as to whether there's an emerging issue, but in this case there turned out to be no user impact.

3. resolved Apr 15, 2025, 06:42 PM UTC

   We've confirmed that our normal service level monitoring and alerting is working correctly, that logs are being ingested and stored as normal, and that the issue is isolated to our logging provider's web console. We've raised the issue to them, and we have identified a workaround should logs be needed in the interim.

Read the full incident report →

Started Feb 12, 2025, 07:03 PM UTC· resolved Feb 12, 2025, 10:16 PM UTC

1. identified Feb 12, 2025, 07:03 PM UTC

   We have identified an issue where trying to use Build a New Route within Trip Planner Studio will fail when selecting a pluggable routing engine. We have identified the issue, and are working on putting a fix in place. We will provide updates here as available or in the next 20 minutes, whichever comes first.

2. identified Feb 12, 2025, 07:26 PM UTC

   We have determined the cause of the pluggable route engine rendering incorrectly within Build a New Route, and are working on reverting the change. We will provide updates here as available or in the next 20 minutes, whichever comes first.

3. identified Feb 12, 2025, 07:47 PM UTC

   We are continuing to work to revert the set of changes that broke pluggable route engines within Build a New Route. We will provide updates here as available or in the next 20 minutes, whichever comes first.

4. identified Feb 12, 2025, 08:08 PM UTC

   We are continuing to work to revert the set of changes that broke pluggable route engines within Build a New Route. We will provide updates here as available or in the next 20 minutes, whichever comes first.

5. identified Feb 12, 2025, 08:30 PM UTC

   We are continuing to work to revert the set of changes that broke pluggable route engines within Build a New Route. We will provide updates here as available or in the next 20 minutes, whichever comes first.

6. identified Feb 12, 2025, 08:42 PM UTC

   We are currently deploying a fix that should resolve the issue within Build A New Route when attempting to use pluggable routing engines. The estimate for the fix to be in place is 25 minutes. We will provide an update when the fix is in place, and Build A New Route is functioning normally.

7. identified Feb 12, 2025, 09:03 PM UTC

   The fix for pluggable engines within Build A New Route of the Platform Dashboard is in place, and has been confirmed to be working as expected again. We are sorry for the inconvenience this may have caused. Please reach out to [email protected] if you have any questions.

8. resolved Feb 12, 2025, 10:16 PM UTC

   This incident has been resolved.

Read the full incident report →