The new per-second rate limits for our Geocoding & Places API that we announced on June 3 are now officially in effect.
What’s Now Active
We’ve transitioned from per-minute to per-second rate limits across all endpoints. This allows for more consistent traffic handling and better protection against sudden spikes.
New Rate Limits:
| Endpoint | New Rate Limit |
|---|---|
/geocoding/v1/locations/by-position/.* |
500 requests per second |
/geocoding/v1/locations/by-address/.* |
100 requests per second |
/geocoding/v1/suggestions/by-address/.* |
100 requests per second |
/geocoding/v1/suggestions/by-text/.* |
100 requests per second |
/geocoding/v1/feedback/.* |
100 requests per second |
| All other endpoints | 50 requests per second |
Why This Matters
This update helps us:
- Support higher, sustained usage without compromising performance
- Reduce the impact of high traffic load that can degrade service for everyone
- Deliver a more stable and predictable experience for all developers
What You Should Do
If you haven’t already:
- Review your current API usage to ensure it aligns with the new per-second limits
- Implement client-side rate limiting to avoid disruptions
- Monitor your traffic and adjust as needed
Need Help?
If you have any questions or need assistance, contact our support.