You have just announced a new prefix and a customer in another country says they cannot reach it. A monitoring alert says a route changed. A colleague asks whether your ROAs are correct before you switch on route origin validation. Or you are preparing a peering request and want to know where the other network is present.
All of these questions are about how the rest of the internet sees your routes — something you cannot answer from inside your own network. Today NetTools.tech adds three read-only tools for exactly that:
- the BGP Looking Glass for an IP address, a prefix or an AS number,
- the ASN Explorer, which now combines registry data with what an AS announces and who it is connected to,
- the IXP & Peering Explorer for PeeringDB networks, Internet Exchanges and facilities.
Together they answer one question: how is this prefix or AS visible on the internet, which AS paths are observed, who originates it, is the route RPKI-valid, and where does the network connect?
Where the data comes from
Routing observations come from the RIPE NCC's Routing Information Service (RIS), queried through the RIPEstat Data API. RIS operates route collectors at Internet Exchanges and data centres; each collector holds BGP sessions with many networks and records the routes they announce. When you look up a prefix, you see the routes those collectors currently have: which collector, which peer, the full AS path, the origin AS and when the route last changed.
Routing status and RPKI come from RIPEstat as well: when the prefix was first and last seen, how many of RIS's full-table peers see it, the route objects registered for it, and the RPKI validation result for every observed origin. NetTools does not run its own RPKI validator — it shows RIPEstat's result and the ROAs it was based on.
Network and peering metadata comes from PeeringDB: the Internet Exchanges and facilities a network lists, its peering policy and its public NOC contacts. This is information networks publish about themselves. The tools always show it separately and never use it as evidence of how traffic is routed.
Every section of a result says which source it came from, when NetTools fetched it, whether it was served from the NetTools cache, and the source's own data time. Nothing is labelled "real-time": route observations are cached for up to 5 minutes, routing status and RPKI for up to 30 minutes, PeeringDB records for up to 6 hours, and a Refresh from sources button fetches them again.
A real example: 193.0.0.0/21
To show what the tools return, here is a lookup of 193.0.0.0/21 — the address block of the RIPE NCC itself — made on 23 October 2026 at 11:15 UTC. Your results will differ: routes change all the time, and that is the point of looking.
The routing summary at the top shows four cards:
- Origin ASN: AS3333, RIPE NCC.
- BGP visibility: 100 % — seen by 163 of 163 RIS full-table IPv4 peers. The percentage is only shown because RIPEstat states both numbers; when it does not, the tool shows the raw collector count instead of inventing a ratio.
- RPKI: ✓ VALID. A ROA authorises AS3333 for 193.0.0.0/21 with a maximum length of /21.
- Prefix: 193.0.0.0/21, announced in BGP.
Below them: the prefix was first seen in RIS history on 31 October 2000 with the same origin, and AS3333 has a route object in the RIPE database. At the time of the lookup, 23 RIS route collectors held 349 routes for the prefix.
Observed routes
The Observed routes tab lists all 349 routes, 50 per page, filterable by collector, collector country, peer ASN, origin and RPKI state, and searchable by AS number or name. A few examples, showing the most common path at each collector:
RRC01 London AS8218 → AS3333
RRC11 New York AS9002 → AS3333
RRC06 Tokyo AS2497 → AS1273 → AS3333
RRC00 Amsterdam AS3333The last line is not a mistake: at RRC00, RIPE's own network is one of the collector's peers, so the path contains only the origin. A collector's location is where RIPE's collector sits; it says nothing about the path your traffic takes.
Long paths stay readable: repeated ASes are collapsed into a single chip with a ×N badge, and paths longer than seven hops fold their middle part behind an expand button. The longest path in this lookup had seven different ASes:
AS37989 → AS56300 → AS132132 → AS4657 → AS20562 → AS1103 ×2 → AS3333The AS path graph
The AS path graph tab draws the most common distinct paths (top 12 by default, up to 120) with the origin on the right and the collectors' peers on the left. You can drag to pan, zoom with the mouse wheel, click an AS to highlight every path through it, or click a path in the list to highlight it alone.
The graph only draws what was observed: an arrow means two ASes were adjacent in at least one route seen by RIS. It does not claim that one AS is a customer, provider or peer of another — BGP routes do not contain that information, and the tool does not guess it.
In this example, AS1103 (SURF) is the AS seen right before the origin most often — in 83 of the 349 routes — and selecting it highlights every path it is part of. In 65 routes it appears twice in a row: AS-path prepending, a common way to make a path less attractive. One route, received via AS14907, even contained AS3333 four times in a row.
Comparing routes
The Compare routes tab summarises the differences between all observed paths. Here: 275 distinct AS paths across 349 routes, one origin, 95 different ASes seen right before the origin (AS1103 in 83 routes, AS1273 in 54), paths of 1 to 7 ASes, and 69 routes with prepending. You can then pick collectors and see their most common paths next to each other, with the ASes that differ highlighted.
The tool calls these observed path differences and nothing more. Every network picks its own best route, so different paths from different vantage points are normal. A difference is not, by itself, an outage, a leak or a hijack. The same restraint applies when a prefix is announced by more than one origin AS: the tool tells you, lists both origins with their RPKI states, and notes that this can be intentional.
PeeringDB
The PeeringDB tab shows the origin network's own record: for AS3333, a non-profit network with a Selective peering policy and connections at AMS-IX and NL-ix. From there you can open each Internet Exchange in the Peering Explorer to see its members, route-server participation and facilities, or open a facility to see which networks and exchanges are present.
ASN Explorer
Searching for an AS number — on the BGP Looking Glass or in the ASN Explorer — shows the AS as a whole. For AS3333 at the same moment: 6 announced IPv4 prefixes and 2 IPv6 prefixes (each one a link to its routes), 907 BGP neighbours, and the PeeringDB record.
The neighbours are labelled the way RIPEstat derives them: left neighbours appear between the AS and the route collectors in observed paths, which typically means upstreams or peers; right neighbours appear between the AS and the origin, typically customers. The ASN Explorer shows this as a position in AS paths, not as a business relationship, because that is all the data can support. The registry information — holder, registry, allocation dates — still comes directly from the responsible regional internet registry via RDAP.
Built to be shared, and to stay read-only
Searches are kept in the address bar, so a link such as /bgp?q=193.0.0.0/21&tab=graph or /peering?ix=26 opens the same view for a colleague. Every result can be exported as CSV or JSON, copied or printed — the export contains the currently filtered routes together with the query, the sources and their timestamps.
The tools only read public databases. They cannot send BGP announcements, talk to route servers, change routing or send any traffic to the networks you look up. Private, documentation and reserved address space is refused with an explanation, and RIPEstat and PeeringDB are queried only from the NetTools server, where the API credentials stay.
What they do not do (yet)
- One routing source. Routes come from RIPE RIS only. Other collector projects such as RouteViews, and the looking glasses of individual carriers, are not queried yet; the routing data layer is designed so they can be added as further providers.
- Collectors are vantage points. RIS sees the routes its peers choose to send. A route that is missing from RIS is not necessarily missing everywhere, and a route seen by every collector can still be filtered by a network that is not a RIS peer.
- PeeringDB is self-published. An Internet Exchange connection means a network has a port there, not that it exchanges traffic with any particular member. Many networks have no PeeringDB record at all.
- No traffic measurement. These tools show the control plane — which routes exist. For the data plane, what packets actually do, use Traceroute or MTR.
Try it
Open the BGP Looking Glass and try one of the examples, or look up your own prefix. For a full reference of every field and option, see the guides for the BGP Looking Glass, the ASN Explorer and the IXP & Peering Explorer.