The new per-second rate limits for our Routing API that we announced on July 29 are now officially in effect.
What’s now active?
We switched from per-minute to per-second rate limits. This allows for more precise traffic control and better system stability.
The new limits are as follows:
| Method | Current rate limits | New rate limits |
startAndCreateReachableAreas (async) |
50 requests per minute | 1 request per second |
startAndCreateReachableLocations (async) |
50 requests per minute | 1 request per second |
All other methods |
500 requests per minute | 10 requests per second |
That means that there is even an increase of the rate limits. For example, the method calculateRoute will allow 600 requests per minute (10 requests per second * 60 seconds), of course using a per-second rate limit.
Why are we doing this?
Our goal is simple: support more usage while keeping our services stable and fast.
We’re happy when our APIs are used heavily — steady, high usage is a good thing! The real challenge comes from sudden traffic spikes, like sending thousands of requests all at once and then going quiet. These bursts can strain our systems and affect everyone’s experience.
By switching to per-second limits, we can better handle consistent, high-volume use while protecting against those sudden peaks.
What do I need to do (if I haven’t already)?
- Review your current usage to ensure it complies with the new per-second limits.
- Implement client-side rate limiting if not already in place.
- Monitor your API traffic to avoid disruptions.
Who can I contact if I have questions?
If you have any questions or need support, please reach out to us via our support.