Skip to content

docs: add the 402 row and correct the 403 and 429 explanations #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MudassarTariq merged 1 commit into from
Nov 12, 2026
Merged

docs: add the 402 row and correct the 403 and 429 explanations #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ spec:

## Rate Limiting, Retries and Timeouts

The plugin holds a token bucket limiter set to `rate_limit` requests per second with a burst of the same size. Keep it under the ceiling for your plan and you will not see 429s during a large sync.
The plugin holds a token bucket limiter set to `rate_limit` requests per second with a burst of the same size. The API has no per-second rate limits, so `rate_limit` only paces the sync. A 429 means your credits are used up.

Retries cover 429, 500, 502, 503 and 504 responses along with network level failures. Backoff doubles each time, so the waits are 1 second, then 2, then 4. Other 4xx responses are returned immediately, because retrying a 400 or a 401 will never succeed.

Expand Down
3 changes: 2 additions & 1 deletion docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ If `${IPGEOLOCATION_API_KEY}` reaches the plugin unexpanded, the shell running `
|---|---|---|
| 400 | Malformed request, usually an invalid IP or AS number | Check the entry the log names |
| 401 | Invalid key, or an endpoint your plan does not include | Confirm the key, then check whether the table needs a paid plan |
| 403 | Key is disabled or the request came from a blocked origin | Check the key's status in the dashboard |
| 402 | Your paid subscription has expired | Renew the plan in the dashboard |
| 403 | The key has an IP allow-list and this machine's IP is not on it | Add the IP to the key's allow-list, or remove the list |
| 404 | No data for the queried resource | Expected for some IPv6 prefixes and unallocated AS numbers |
| 423 | Bogon address: private, loopback, reserved or multicast | Remove it from `ips`. These ranges have no public location |
| 429 | No credits left: the free plan's daily credits, or a paid plan's credits with overage off or at its cap (the API has no per-second rate limits) | Check remaining credits in the dashboard. Overage is on by default on all paid plans and is switched with Allow Surcharge Usage |
Expand Down
Loading