About, Data Sources and API
How the GIBIRNet BGP Toolkit collects its data, how often it is updated and how to use the JSON API.
Data sources
- BGP table
- Full IPv4 and IPv6 table (all paths) from the GIBIRNet AS208972 route reflector, refreshed every hour.
- RPKI
- Validated ROA payloads (rpki-client format), refreshed every hour; origin validation per RFC 6811.
- GeoLite2
- MaxMind GeoLite2 ASN, City and Country databases, applied as soon as a new release is published.
- PeeringDB
- Organization names, websites, looking glass and route server addresses, refreshed daily.
- CAIDA
- Provider, customer and peering relationships between AS numbers from the CAIDA AS Relationships Dataset (monthly).
- Registry
- RIPE / APNIC whois for network descriptions.
- Updated
- 21.10.2026 13:16 UTC
Terms
- Upstream
- A transit provider of the AS (CAIDA relationship).
- Downstream
- A customer of the AS (CAIDA relationship).
- Peering
- Settlement-free peer of the AS (CAIDA relationship).
- Neighbors
- Every AS adjacent to the AS in the paths seen by AS208972; neighbors CAIDA does not know have no label.
- Routes
- Number of BGP paths that use the adjacency.
- Not announced
- Prefix left the routing table; kept for 30 days, then removed.
JSON API
60 / minuteFree, read-only, no key needed. Responses are JSON with an updated_at timestamp.
AS details, neighbors and announced prefixes
Most specific prefix covering an IP address, with GeoLite2 data
Prefix details, AS path, RPKI status and covering ROAs
Search AS numbers and prefixes by name
GET /api/v1/status
Data freshness for monitoring (HTTP 503 when stale)