Get email notifications whenever Eleos Technologies creates, updates or resolves an incident.
Get text message notifications whenever Eleos Technologies creates or resolves an incident.
Get webhook notifications whenever Eleos Technologies creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 27, 2025
No incidents reported today.
Apr 26, 2025
No incidents reported.
Apr 25, 2025
No incidents reported.
Apr 24, 2025
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 24, 18:13 UTC
Apr 24, 18:13 UTC
Apr 23, 2025
No incidents reported.
Apr 22, 2025
No incidents reported.
Apr 21, 2025
No incidents reported.
Apr 20, 2025
No incidents reported.
Apr 19, 2025
No incidents reported.
Apr 18, 2025
No incidents reported.
Apr 17, 2025
No incidents reported.
Apr 16, 2025
Resolved -
Messages integrated successfully and the message backlog remains stable.
Apr 16, 20:03 UTC
Apr 16, 20:03 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 16, 19:31 UTC
Apr 16, 19:31 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 16, 18:56 UTC
Apr 16, 18:56 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 16, 18:28 UTC
Apr 16, 18:28 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 16, 17:54 UTC
Apr 16, 17:54 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 16, 17:14 UTC
Apr 16, 17:14 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 16, 16:41 UTC
Apr 16, 16:41 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 16, 16:07 UTC
Apr 16, 16:07 UTC
Update -
We are continuing to work on applying the mitigation and will notify once complete.
Apr 16, 15:29 UTC
Apr 16, 15:29 UTC
Update -
We have identified the cause of the issue and are working on a mitigation.
Apr 16, 14:56 UTC
Apr 16, 14:56 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.
Apr 16, 14:28 UTC
Apr 16, 14:28 UTC
Apr 15, 2025
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 15, 18:42 UTC
Apr 15, 18:42 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 15, 18:28 UTC
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 15, 18:28 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.
Apr 15, 18:24 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.
Apr 15, 18:24 UTC
Apr 14, 2025
No incidents reported.
Apr 13, 2025
No incidents reported.