Issue Summary

Currently, only cost-based rate-limiting provides the X-RateLimit-NearLimit = true header with a 429 response.

We have a number of partners questioning this as they facing 429 error that are not coming with the X-RateLimit-NearLimit as it’s stated in the documentation Rate limiting 

This suggestion is to add X-RateLimit-NearLimit header to the other rate limiting mechanisms responses:

• Counter-based rate limiting
• DB Connections Rate Limiting

Expected Results

Receive 429 response with X-RateLimit-NearLimit header ** when reaching rate limits, independently of rate limiting mechanism

Actual Results

Currently, the X-RateLimit-NearLimit header does not come with 429 responses for some rate limiting mechanisms.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available