Service response time

Service Response Time is the period of time from when the last byte of a request is received by HLS to when the first byte of the corresponding response is sent from HLS. Service Response Time is measured in milliseconds. HERE’s production service logs are used to provide the required information. The Service Response Time 98th percentile is computed as the 98th percentile of all valid calls sent during each consecutive 24-hour period starting at midnight Coordinated Universal Time (UTC).

HERE Map Rendering

API	Response time
Raster Tile API v3 - Base tiles	570 ms
Raster Tile API v3 - Satellite and hybrid tiles	780 ms
Vector Tile API v2	300 ms

HERE Positioning

API	Response time
Network Positioning API v1	300 ms
Network Positioning API v2	300 ms

HERE Real-Time Traffic

API	Response time
Traffic API v6 and v7	200 ms Traffic Incidents 0.25x0.25 degrees, radius 15 km, max. zoom level 10, max. response size 0.2

HERE Routing

API	Response time
Routing API v7 and v8	• Long Route (between 100 km and 1000 km actual distance): 3000 ms No traffic, no avoids, no alternatives, single routes only, Routingmodetype=fastest, and transportmode=car. • Short Route (less than 100 km actual distance): 350 ms No traffic, no avoids, no alternatives, single routes only, Routingmodetype=fastest, and transport mode=car. • Pedestrian (less than 100 km): 350 ms No alternatives.

API

Response time

Routing API v7 and v8

• Long Route (between 100 km and 1000 km actual distance): 3000 ms
No traffic, no avoids, no alternatives, single routes only, Routingmodetype=fastest, and transportmode=car.
• Short Route (less than 100 km actual distance): 350 ms
No traffic, no avoids, no alternatives, single routes only, Routingmodetype=fastest, and transport mode=car.
• Pedestrian (less than 100 km): 350 ms
No alternatives.

HERE Geocoding and Search

API	Response Time
Geocode	250 ms
Reverse Geocode	100ms