Eleos Technologies Status

Resolved: Messages integrated successfully and the message backlog remains stable.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

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.

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

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

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

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.

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.

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.