N-WaysService status
Is it working? The live status of each API, incidents and planned maintenance.
Is it working?
Each API’s state right now, and the incidents of the last 90 days with their updates. It updates by itself as things change. The status of everything N-Ways runs, the apps and website included, with each part’s last 90 days and response times, is on status.nways.ng.
Checking… (this needs JavaScript; or see the status as JSON)
Partners also hear about incidents and planned work by email. To follow them in a feed reader, Slack or Teams: Atom feed, RSS feed.
What it covers
| Service | Includes |
|---|---|
| Maps | Hosted styles, vector tiles, fonts, static maps |
| Geocoding and places | Geocoding, reverse geocoding, postcodes, autocomplete, address validation, places |
| Routes | Routes, the route matrix, route optimisation, fares, traffic |
| Fleet | Vehicles, deliveries, tracking links and webhooks |
| Console | Sign-in, keys, usage and billing |
Planned maintenance
We announce planned work at least 48 hours ahead on the status page and by email, and do it at night in West Africa when traffic is lowest. Planned maintenance doesn’t count against uptime commitments.
Check it from your code
Your monitoring can watch the same thing we do: GET https://nways.ng/healthz answers 200 while the service is up. It needs no key and isn’t charged; please don’t call it more than once a minute.
curl -fsS https://nways.ng/healthzFor your own calls, log the X-Request-Id header and the error’s reason, and retry 503 and 429 answers after the Retry-After seconds. Retrying well