All Systems Operational
Route Optimization API Operational
90 days ago
99.98 % uptime
Today
Routing API Operational
90 days ago
99.96 % uptime
Today
Matrix API Operational
90 days ago
99.96 % uptime
Today
Isochrone API Operational
90 days ago
100.0 % uptime
Today
Geocoding API Operational
90 days ago
99.99 % uptime
Today
Cluster API Operational
90 days ago
100.0 % uptime
Today
Email / Support Operational
Recurring Payment Operational
Dashboard Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Routing API - Response Time (route between 2 locations)
Fetching
Matrix API - Response Time (115x115 locations)
Fetching
Route Optimization API - Response Time VRP (5 vehicles, 115 services) ?
Fetching
Route Optimization API - Response Time TSP (1 vehicle, 115 locations) ?
Fetching
Geocoding API - Response Time (1 address)
Fetching
Past Incidents
Jan 25, 2022

No incidents reported today.

Jan 24, 2022

No incidents reported.

Jan 23, 2022
Resolved - We have many internal clusters that do certain tasks. One of those clusters is responsible for some of the new profiles we introduced a few weeks ago. All these clusters get automated and frequent but usually safe data updates at certain times.

The popularity of those new profiles caused degraded performance at this cluster which stacked up in the route optimization cluster. This made it complicated to identify the root cause. Additionally the automated data update happening at the time of our investigation caused further confusion and costs us time to identify and fix the issue.

As soon as we understood the problem in the cluster with the new profiles the route optimization cluster usually stabilizes itself, which wasn't the case this time and costed us further time as we didn't get the cluster stable.

We now need to fix those two underlying problems that caused this unacceptable long downtime.

We very sorry for the inconveniences we caused. Please let us know if you need further clarification and support from us.
Jan 23, 16:42 CET
Identified - The issue has been identified and a fix is being implemented.
Jan 23, 15:00 CET
Jan 22, 2022

No incidents reported.

Jan 21, 2022

No incidents reported.

Jan 20, 2022

No incidents reported.

Jan 19, 2022

No incidents reported.

Jan 18, 2022

No incidents reported.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.

Jan 12, 2022

No incidents reported.

Jan 11, 2022

No incidents reported.