OptimoRoute Outage History

Between 00:35 and 05:56 UTC, our API service experienced increased error rates and latency. During this period, the API was degraded and, at times, unavailable, which may have prompted some users to contact support. The issue was fully resolved by 05:55 UTC, and all services are now operating normally. The incident was caused by problems with Amazon Elastic Compute Cloud infrastructure in the AWS N. Virginia region. Despite the API disruption, core functionality in the web application remained operational throughout the incident. The mobile application for drivers also remained operational, allowing drivers to continue accessing and completing their assigned routes.

Incident has been resolved and all services should operate normally.

This incident has been resolved.

Between 11:05 and 11:35 UTC, viewing a map with newly created routes in our web application displayed an error message prompting users to contact support. The issue was fully resolved within 15 minutes of the first report, and all services are now operating normally. Despite the error message, core functionalities such as adding orders, planning, sending routes, and moving orders on and off routes continued to function correctly. Additionally, all other services—such as live tracking, importing, API integrations, customer notifications, and real-time order tracking—remained fully operational throughout.

We experienced an issue with the OptimoRoute mobile service where new mobile apps could not be activated. This was caused by an expired HTTPS certificate. The issue has now been resolved, and all services are operating normally. No data from driver apps was lost.