Serving Regions
The edge regions that have served your active account's traffic: the distinct values of the region field of your traffic-log entries. Use them as the values of the region filter of GET /v1/traffic/logs — for example ?region=eu-north-1, or several comma-separated, with region_op set to equals, not_equals, in or not_in.
Only regions present in your stored traffic logs are listed (entries without a region are skipped), in alphabetical order, at most 100. This is not the list of all platform regions — for that, see List Regions.
Permissions: requires traffic_inspector:read on the active account.
Response (200 OK)
items array<string>
Region names, sorted alphabetically. Empty when no stored traffic has a region.
Errors
401 Unauthorized
Missing or invalid auth.
403 Forbidden
No active account, not a member, or
Insufficient permissions for this action (no traffic_inspector:read).500 Internal Server Error
Internal server error.Request
curl "https://api.ngris.com/v1/traffic/serving-regions" \
-H "X-API-KEY: <your_api_key>"
Response — 200 OK
{
"items": [
"eu-north-1",
"us-east-va"
]
}
Then — filter traffic logs by region
curl "https://api.ngris.com/v1/traffic/logs?region=eu-north-1" \
-H "X-API-KEY: <your_api_key>"