Service availability

HERE operates the following services on a continuous basis, 365 days per calendar year. HERE uses commercially reasonable efforts to maintain a target service availability per calendar month, as shown here.

Location services

HERE EV Charge Points

The following services have a 99.9% monthly uptime:

HERE EV Charge Points API v2
HERE EV Charge Points API v3

HERE Fuel Prices

Fuel Prices API v2 has a 99.9% monthly uptime.

HERE Geocoding and Search

The following services have a 99.9% monthly uptime:

Batch Geocoding API v6
Geocoder API v6
Geocoder Autocomplete API v6
Geocoding & Search API v7
Places (Search) API v2

HERE Map Rendering

The following services have a 99.9% monthly uptime:

Map Image API v3
Raster Tile API v3
Vector Tile API v2

HERE Positioning

The following services have a 99.9% monthly uptime:

HD GNSS Positioning & A GNSS Positioning v1
Network Positioning API v1
Network Positioning API v2

HERE Real-Time Traffic

The following services have a 99.9% monthly uptime:

Traffic API v6
Traffic API v7
Traffic Raster Tile API v3
Traffic TPEG API v1
Traffic Vector Tile API v2

HERE Routing

The following services have a 99.9% monthly uptime:

Geofencing v8
Isoline Routing API v8
Map Attributes API v8
Matrix Routing API v8
Route Matching API v8
Routing API v7
Routing API v8
Waypoints Sequence v8

HERE SDK (server components)

HERE SDK v4 for Android, iOS, and Flutter have a 99.9% monthly uptime.

HERE Tour Planning

Tour Planning API v3 has a 99.9% monthly uptime.

HERE Transit

The following services have a 99.9% monthly uptime:

Intermodal Routing v8
Public Transit API v8

Platform data services

Customers can create solutions with up to 99.9% uptime using high-service-availability APIs. Highly available solutions built on the HERE platform require both the Service Level Objective (SLO) supported APIs described below, and active use case workflow monitoring and responsiveness by the Customer.

HERE will use commercially reasonable efforts to provide SLOs as set out in the following table:

API	Description	Single Region Monthly Service availability	Multi-Region Monthly Service availability*
Authentication & Authorization	Used for obtaining access tokens and keys.	99.5%	99.9%
Blob	Used for write requests to various layer types.	99.5%	99.0%**
Config	Used for read (catalog details) and list (catalog) requests.	99.5%	99.9%
Index	Used for read and write requests to index layers.	98.5%	Not offered
Ingest	Used for write requests to stream layers.	99.5%	99.9%
Interactive Map	Used for read and write requests to interactive map layers.	99.5%	Not offered
Metadata & Query	Used for query and read requests to versioned and volatile layers.	99.5%	99.9%
Monitoring and Alerting (not an API)	Ability to access monitoring dashboards and logs from a browser.	99.5%	99.9%
Pipeline (v2)	Used for create (pipeline and pipeline version), activate, deactivate, and cancel requests.	99.5%	99.9%
Publish	Used for write requests to versioned layers.	99.5%	99.0%**
Stream	Used for read requests to stream layers.	99.5%	99.9%
Volatile Blob	Used for read and write requests to volatile layers.	99.5%	99.9%

The Monthly Service Availability of each API is measured independently, and Service Credits are provided based on whether Monthly Service Availability is met per API

* Multi-region Monthly Service Availability SLOs require multi-region Catalog and/or Pipeline configurations. For example, SLOs of 99.9% for any Data Write/Read Requests as depicted in the tables above require data be stored in multi-region configured catalogs. SLOs of 99.9% for Pipeline Requests as depicted in the tables above require data processing using multi-region configured pipelines. For Marketplace Consumers, this means that in order for the Multi-region Monthly Service Availability to apply, the Marketplace Provider must have configured the catalogs and/or pipelines you are reading from accordingly.

** For versioned layers, the HERE platform adheres to read-after-write consistency and uses synchronous data replication process. The synchronous replication process means that writes to either Publish or Blob APIs for versioned layers are possible only when both primary and secondary regions are available. Therefore, if the customer chooses the multi-region option for a catalog with versioned layers, the SLO for write Requests on versioned layers is reduced to 99.0% (two regions at 99.5% Service Availability equates to a combined Service Availability of 99.0% due to read-after-write consistency replication strategy).

Basic operational guidelines

The Customer shall, within their service or application logic, cache HERE Account tokens, API Lookup provided endpoints and Catalog/Pipeline configurations to ensure that information is available in the event any downtime is experienced. This caching is resolved automatically when using the HERE Data SDK for Java and Scala.
The Customer shall copy custom monitoring dashboards and alerts from the primary region to the secondary region so that those dashboards and alerts are available as necessary in the second region should the primary region become unavailable. Note: Each region contains only those metrics specific to that region.
The Customer shall bookmark all URLs to access monitoring dashboards, alerts and logs for each region as provided on the HERE Portal in order to reach them directly in the event the HERE Portal is unavailable.