BGP Looking Glass
AvailableLook up an IP address, IPv4/IPv6 prefix or AS number and see how the internet routes it: the origin AS, the AS paths observed by RIPE RIS route collectors around the world, BGP visibility, RPKI validation and the origin network’s PeeringDB record — with an interactive AS-path graph and route comparison.
Look up a prefix, address or AS number
Routing summary
How it works
The NetTools server queries the RIPEstat Data API: the looking-glass call returns the routes RIPE RIS route collectors currently hold for the prefix (collector, peer, AS path, origin, last change), routing-status adds first/last seen, visibility among RIS full-table peers and route objects, and rpki-validation gives the RPKI state of each observed origin. The origin network’s PeeringDB record is added as metadata. Results are normalised into the NetTools routing model and cached briefly (routes 5 minutes).
Where the data comes from
- Route observations come from the RIPE NCC’s Routing Information Service (RIS): route collectors at internet exchanges and data centres hold BGP sessions with hundreds of networks, and RIPEstat’s looking-glass data call returns the routes they currently have for a prefix — collector, peer, AS path, origin and when the route last changed.
- Visibility, first/last seen and route objects come from RIPEstat routing-status: how many of RIS’s full-table peers see the prefix, out of how many. The percentage is only shown when RIPEstat states both numbers.
- RPKI is RIPEstat’s rpki-validation result (validated with Routinator) for each observed origin. NetTools does not validate ROAs itself.
- PeeringDB adds what the origin network publishes about itself — IX connections, facilities, peering policy, contacts. It is metadata, not routing evidence.
- A collector’s location is where RIPE’s route collector sits. It does not tell you the path your own traffic takes.
- Results are cached on the NetTools server (route observations 5 minutes, routing status and RPKI 30 minutes, PeeringDB 6 hours); every section says when it was fetched and the source’s own data time.
Safeguards & responsible use
- Read-only: it queries public routing databases and never sends BGP announcements, talks to route servers or sends traffic to the network.
- Queries go only to RIPEstat and PeeringDB from the NetTools server; API credentials stay on the server.
- Private, documentation and reserved address space is refused without a lookup.
- Rate limited, time limited and cached; no query is stored.
Learn more
What is BGP Looking Glass?How it works, how to read the results, troubleshooting and FAQs. Complete guide →Frequently asked questions
Where do the AS paths come from?
From the RIPE NCC’s Routing Information Service (RIS). Its route collectors at internet exchanges peer with hundreds of networks; each route shows what one of those peers announced to the collector. It is a view from those vantage points, not the path your own traffic takes.
What does the visibility percentage mean?
It is RIPEstat’s count of RIS full-table peers that see the prefix, divided by the number of full-table peers for that address family. If RIPEstat does not state both numbers, NetTools shows the raw collector count instead of a percentage.
What do the RPKI states mean?
Valid means a ROA authorises the origin AS for this prefix length. Invalid means ROAs exist but none matches the origin or the length, so networks that enforce RPKI drop the route. Not found means no ROA covers the prefix.
Why do collectors show different AS paths?
Every network picks its own best route, so peers at different collectors often reach the origin through different transit providers. A path difference is normal and is not by itself an outage or a routing problem.
Is this real time?
Route observations reflect the RIS collectors’ state at the time shown with each result and are cached for up to 5 minutes; routing status and RPKI for up to 30 minutes. Every section shows when it was fetched and the source’s own data time.