Apr <var data-var='date'> 3</var>, <var data-var='time'>19:06</var> UTC Resolved - 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.Apr <var data-var='date'> 3</var>, <var data-var='time'>18:46</var> UTC Monitoring - 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.Apr <var data-var='date'> 3</var>, <var data-var='time'>18:28</var> UTC Investigating - 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.

Delays in message delivery and notifications

Mar <var data-var='date'>12</var>, <var data-var='time'>00:33</var> UTC Resolved - 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 support@eleostech.com if you have any questions or concerns about this incident.Mar <var data-var='date'>12</var>, <var data-var='time'>00:12</var> UTC Monitoring - 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.

Elevated Error Rates

Mar <var data-var='date'> 5</var>, <var data-var='time'>20:13</var> UTC Resolved - Response times have returned to normal levels and the APIs and apps are reporting normal telemetry.Mar <var data-var='date'> 5</var>, <var data-var='time'>20:07</var> UTC Monitoring - We've rolled back the offending change and error rates have returned to normal, beginning recovery at 19:50 UTC and returning to normal levels at 20:02 UTC. 95th percentile response time latency is still higher than expected and we are monitoring.Mar <var data-var='date'> 5</var>, <var data-var='time'>19:57</var> UTC Investigating - We are currently experiencing elevated error rate across the Eleos Mobile Platform beginning at 14:50 EDT. We are currently engaged in investigation, and will post an update with more information in 20 minutes.

Jan <var data-var='date'>29</var>, <var data-var='time'>20:54</var> UTC Resolved - As of 20:44 UTC document delivery times have returned to normal. Please reach out to support if you have any questions or concerns: support@eleostech.com. We apologize for the inconvenience.Jan <var data-var='date'>29</var>, <var data-var='time'>20:41</var> UTC Identified - We have identified the issue and applied a fix, document processing times are starting to resolve.Jan <var data-var='date'>29</var>, <var data-var='time'>20:23</var> UTC Investigating - We are currently investigating delays with document delivery.

Delayed Document Delivery

Jan <var data-var='date'>23</var>, <var data-var='time'>16:12</var> UTC Resolved - 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: support@eleostech.comJan <var data-var='date'>23</var>, <var data-var='time'>15:55</var> UTC Update - 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.Jan <var data-var='date'>23</var>, <var data-var='time'>15:47</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>23</var>, <var data-var='time'>15:30</var> UTC Investigating - 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.

Issue With Build A New Route Using Pluggable Router in App Manager

Jan <var data-var='date'>10</var>, <var data-var='time'>23:05</var> UTC Resolved - 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.Jan <var data-var='date'>10</var>, <var data-var='time'>22:24</var> UTC Investigating - 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.

Elevated Error Rates for the Eleos Platform

Jan <var data-var='date'> 9</var>, <var data-var='time'>02:04</var> UTC Resolved - Error rates have returned to normal operating levels. Between 00:48 UTC and 01:09 UTC a set of servers became unhealthy and stopped responding to requests which resulted in an 8% error rate across the platform. New servers were then 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.Jan <var data-var='date'> 9</var>, <var data-var='time'>01:21</var> UTC Monitoring - Error rates have come back down from around 8% and have returned to normal. We're continuing to monitor to make sure the error rate does not spike again. During this time period with the elevated error rates, the mobile apps may have briefly fallen back to offline mode and will have retried any requests that were queued. Document upload, processing, and delivering messages to customers web services were unaffected during this time.Jan <var data-var='date'> 9</var>, <var data-var='time'>01:01</var> UTC Investigating - We are currently investigating elevated error rates for the Eleos Platform.

Jan <var data-var='date'> 6</var>, <var data-var='time'>17:41</var> UTC Resolved - Our upstream provider has indicated this issue has been resolved, and we're seeing Platform Metrics successfully load in App Manager.Jan <var data-var='date'> 6</var>, <var data-var='time'>17:24</var> UTC Update - 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.Jan <var data-var='date'> 6</var>, <var data-var='time'>17:02</var> UTC Update - We are continuing to monitor as we await for more updates from our upstream provider at this time.Jan <var data-var='date'> 6</var>, <var data-var='time'>16:17</var> UTC Monitoring - 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.

App Manager Eleos Platform Metrics Are Not Loading

Dec <var data-var='date'>17</var>, <var data-var='time'>17:40</var> UTC Resolved - 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.Dec <var data-var='date'>17</var>, <var data-var='time'>17:18</var> UTC Monitoring - 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.Dec <var data-var='date'>17</var>, <var data-var='time'>17:00</var> UTC Investigating - 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.

Action Request API Interruption

Dec <var data-var='date'>12</var>, <var data-var='time'>22:16</var> UTC Resolved - 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 support@eleostech.com if you have any questions or issues.Dec <var data-var='date'>12</var>, <var data-var='time'>21:45</var> UTC Monitoring - 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.

Issues With DNS Resolution

Nov <var data-var='date'> 7</var>, <var data-var='time'>01:03</var> UTC Resolved - This incident has been resolved. We are continuing to monitor document processing.Nov <var data-var='date'> 7</var>, <var data-var='time'>00:44</var> UTC Update - Document processing performance should no longer be degraded. We are continuing to monitor and investigate this issue.Nov <var data-var='date'> 7</var>, <var data-var='time'>00:31</var> UTC Investigating - We are investigating potential issues affecting the document processing. Our on-call team is engaged and will provide an update shortly.

Investigating slowdowns in document processing

Oct <var data-var='date'>20</var>, <var data-var='time'>20:34</var> UTC Resolved - 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 support@eleostech.com.Oct <var data-var='date'>20</var>, <var data-var='time'>20:20</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>20:05</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>19:35</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>19:00</var> UTC Monitoring - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>18:33</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>17:57</var> UTC Update - 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 EDTOct <var data-var='date'>20</var>, <var data-var='time'>17:19</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>16:36</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>15:53</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>15:23</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>14:48</var> UTC Update - We're continuing to investigate mitigations for document delivery and POI layer issues. We'll update again by 11:15 AM EDT.Oct <var data-var='date'>20</var>, <var data-var='time'>14:13</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>13:41</var> UTC Identified - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>13:07</var> UTC Investigating - 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.

Investigating a problem with retrieving POIs and document delivery

Oct <var data-var='date'>20</var>, <var data-var='time'>10:34</var> UTC Resolved - 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 support@eleostech.com if you experience any abnormalities with the Eleos Platform.Oct <var data-var='date'>20</var>, <var data-var='time'>10:16</var> UTC Update - 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.Oct <var data-var='date'>20</var>, <var data-var='time'>09:47</var> UTC Monitoring - 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.

Error Rates Elevated

May <var data-var='date'>29</var>, <var data-var='time'>13:51</var> UTC Resolved - Between 11:54 AM EDT and 7:42 PM EDT yesterday, May 28th, emails sent to our primary support address, support@eleostech.com, were not received and did not create support tickets. If you sent an email to support@eleostech.com 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.

support@eleostech.com address not creating support tickets

May <var data-var='date'>28</var>, <var data-var='time'>23:52</var> UTC Resolved - We've resolved the issue with the support@eleostech.com address and support tickets are being created again. We determined that emails sent to this address between 11:54 AM EDT and 7:42 PM EDT were not received. If you sent an email to support@eleostech.com 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.May <var data-var='date'>28</var>, <var data-var='time'>23:28</var> UTC Investigating - Emails sent to our primary support address, support@eleostech.com, are not currently being received or creating support tickets. Support requests opened via the portal at https://eleostech.zendesk.com are creating tickets successfully. We're investigating the issue with support@eleostech.com. In the meantime, if you need to reach support, please email us at support@eleostech.zendesk.com or login to the portal at https://eleostech.zendesk.com to create a ticket.

May <var data-var='date'> 5</var>, <var data-var='time'>15:54</var> UTC Resolved - 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.May <var data-var='date'> 5</var>, <var data-var='time'>15:19</var> UTC Update - Routing success rates still appear to be stable and under normal operating conditions, but we are continuing to monitor at this time.May <var data-var='date'> 5</var>, <var data-var='time'>14:56</var> UTC Update - Routing success rates appear to be stable and under normal operating conditions, but we are continuing to monitor.May <var data-var='date'> 5</var>, <var data-var='time'>14:51</var> UTC Monitoring - 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.May <var data-var='date'> 5</var>, <var data-var='time'>14:34</var> UTC Investigating - We are currently investigating an issue with drivers not being able to receive routes at this time.

Drivers not receiving routes

Apr <var data-var='date'>30</var>, <var data-var='time'>20:08</var> UTC Resolved - 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 support@eleostech.com.Apr <var data-var='date'>30</var>, <var data-var='time'>19:48</var> UTC Monitoring - 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 support@eleostech.com.Apr <var data-var='date'>30</var>, <var data-var='time'>19:42</var> UTC Update - 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.Apr <var data-var='date'>30</var>, <var data-var='time'>19:20</var> UTC Update - We are continuing to work on a fix for this issue.Apr <var data-var='date'>30</var>, <var data-var='time'>19:20</var> UTC Identified - 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.

Eleos Platform Metrics Not Rendering Graphs

Apr <var data-var='date'>28</var>, <var data-var='time'>16:26</var> UTC Resolved - 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.Apr <var data-var='date'>28</var>, <var data-var='time'>16:15</var> UTC Update - We are continuing to work on a fix for this issue.Apr <var data-var='date'>28</var>, <var data-var='time'>16:02</var> UTC Identified - 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.

Delayed Message Processing

Apr <var data-var='date'>24</var>, <var data-var='time'>18:13</var> UTC Resolved - We investigated an incident with delayed integration of messages starting at 17:02UTC, which was resolved at 17:20UTC. The 99th percentile of message delay was just under 10 minutes, and most messages were delivered well under that time frame. No message information was lost and workflow actions were not impacted.

Apr <var data-var='date'>16</var>, <var data-var='time'>20:03</var> UTC Resolved - Messages integrated successfully and the message backlog remains stable.Apr <var data-var='date'>16</var>, <var data-var='time'>19:31</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>18:56</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>18:28</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>17:54</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>17:14</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>16:41</var> UTC Update - 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.Apr <var data-var='date'>16</var>, <var data-var='time'>16:07</var> UTC Monitoring - We are currently monitoring our backlog of messages. Messages are being processed and we are working through a large backlog that has been queued.Apr <var data-var='date'>16</var>, <var data-var='time'>15:29</var> UTC Update - We are continuing to work on applying the mitigation and will notify once complete.Apr <var data-var='date'>16</var>, <var data-var='time'>14:56</var> UTC Update - We have identified the cause of the issue and are working on a mitigation.Apr <var data-var='date'>16</var>, <var data-var='time'>14:28</var> UTC Investigating - We are investigating a delay in the delivery time of transactions. Our on-call team is engaged and will provide an update shortly.

Monitoring delayed message processing

Apr <var data-var='date'>15</var>, <var data-var='time'>18:42</var> UTC Resolved - 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.Apr <var data-var='date'>15</var>, <var data-var='time'>18:28</var> UTC Monitoring - 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.Apr <var data-var='date'>15</var>, <var data-var='time'>18:24</var> UTC Investigating - 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.

Investigating reduced route request volume

Feb <var data-var='date'>12</var>, <var data-var='time'>22:16</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>12</var>, <var data-var='time'>21:03</var> UTC Update - 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 support@eleostech.com if you have any questions.Feb <var data-var='date'>12</var>, <var data-var='time'>20:42</var> UTC Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>20:30</var> UTC Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>20:08</var> UTC Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>19:47</var> UTC Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>19:26</var> UTC Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>19:03</var> UTC Identified - 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.

Pluggable Build a New Route

Jan <var data-var='date'>29</var>, <var data-var='time'>08:12</var> UTC Completed - The maintenance is complete and the affected systems are back online.Jan <var data-var='date'>29</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>21</var>, <var data-var='time'>22:35</var> UTC Scheduled - In our ongoing and continuous efforts to improve the performance, reliability, and capacity of the services we offer you, and to reduce the likelihood of slower-than-normal response times as occurred January 14, we will be performing scheduled maintenance on the Eleos Platform next week. On Wednesday, January 29, beginning at 3:00 AM EST and ending at 3:30 AM EST (for a total of 30 minutes), 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. 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 3:00 AM EST, 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 3:00 AM EST, 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 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.

Planned maintenance January 29, 2025

Jan <var data-var='date'>14</var>, <var data-var='time'>17:31</var> UTC Resolved - Response times for the APIs and mobile apps are back to normal.Jan <var data-var='date'>14</var>, <var data-var='time'>17:16</var> UTC Investigating - We are investigating slow response times for API requests made to the Eleos Mobile Platform, which also affects mobile apps. Our on-call team is engaged and will provide an update shortly.

Degraded Performance

Dec <var data-var='date'> 5</var>, <var data-var='time'>20:30</var> UTC Resolved - Due to a configuration error, between 2024-12-05 at 20:27 UTC and 2024-12-06 at 16:37 UTC, Eleos Platform Metric charts in App Manager failed to display data. We have corrected the issue and confirmed that the charts are now displaying correctly.

Is Eleos Technologies down?

Eleos Technologies status is UP

Lastest published events

Delays in message delivery and notifications

Elevated Error Rates

Elevated Error Rates

Eleos Technologies Services, Components and Regions

Recent Eleos Technologies events

Delays in message delivery and notifications

Elevated Error Rates

Elevated Error Rates

Delayed Document Delivery

Issue With Build A New Route Using Pluggable Router in App Manager

Elevated Error Rates for the Eleos Platform

Get your FREE account now,
5 monitors included!

Is Eleos Technologies down?

Eleos Technologies status is UP

Lastest published events

Delays in message delivery and notifications

Elevated Error Rates

Elevated Error Rates

Eleos Technologies Services, Components and Regions

Recent Eleos Technologies events

Delays in message delivery and notifications

Elevated Error Rates

Elevated Error Rates

Delayed Document Delivery

Issue With Build A New Route Using Pluggable Router in App Manager

Elevated Error Rates for the Eleos Platform

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!