RIPEstat · Network · 1 endpoint
Network Info
Routing truth for an IP address or ASN — which announced prefix it lives in, and which networks originate that prefix, from the RIPE NCC's open data platform.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 120 / 60s
- Cache
- 5m
- Requests
- 1
Endpoint
How to call it
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/network-info/%7Bresource%7D \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"network-info","params":{"max_age":"60"}}Parameters
- resourcepath segment · required
- An IP address or an ASN.
- max_ageinteger (seconds) · optional
- Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300
Example response
200 OK
JSON
{
"data": {
"resource": "8.8.8.8",
"ip": "8.8.8.8",
"prefix": "8.8.8.0/24",
"asns": ["AS15169"],
"bgp_prefix": "8.8.8.0/24",
"url": "https://stat.ripe.net/8.8.8.8"
},
"meta": {
"request_id": "req_7Q2fK4mZ",
"as_of": "2026-08-20T16:30:00.000Z",
"age_seconds": 60,
"next_update_at": "2026-08-20T16:35:00.000Z"
}
}- resource / ip
- The resource as asked about, and the IP it resolved to.
- prefix / bgp_prefix
- The announced prefix the resource lives in.
- asns[]
- The ASNs that originate that prefix — routing-level truth, not registration data.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Data freshness
Every response is timestamped
as_of is when the data was published, age_seconds how old it is now, and next_update_at when newer data is expected.
Up to date
200
Inside its published window. Almost every request.
Delayed
delayed: true
Newer data is late; you get the latest there is, flagged.
Unavailable
503
Nothing recent enough. Carries Retry-After, never billed.
Health
Is it up?
- Network Info
1/1 passing