BGP lookup: any network’s prefixes, neighbours and visibility, live from RIPE
consults, drawn.
Under every website is a table: which network announces which addresses, and who carries whom. Operators read it in terminals; almost nobody else has ever seen it. This page reads the RIPE NCC’s public measurement wire — the live answers of the route-collector network — and draws it: any network’s holder, its announced prefixes, its upstreams and downstreams, its visibility among the collectors, and the history of its announcements. Any ASN, prefix or address is free to look up.
It opens with you: your address, the prefix it sits in, and the network that announces it to the world. One wire, keyless, browser-direct; your lookups go to the measurement service and nowhere else, and what it does not say, this page does not invent.
Where you sit
Your seat in the table.
This connection
Asking the wire…
The desk
Any network. Any prefix. Any address.
An ASN (AS13335 or just 13335), a prefix
(1.1.1.0/24) or a bare address — the desk reads
whichever you hand it.
The network
The neighbours
Announcement history, drawn
The announced prefixes
The giants
The networks everyone stands on.
Ten large networks to start from. Press one and the desk above reads its prefixes, its neighbours and how widely its routes are seen.
Overview
The routing table, in plain words.
Every network on the internet has a number, its autonomous system number or ASN, and announces the blocks of addresses it can deliver — its prefixes — to its neighbours over the Border Gateway Protocol, BGP. Routing asks the RIPE NCC’s public RIPEstat service, which hears those announcements through the route collectors of its Routing Information Service, and draws the answer for any ASN, prefix or single address you type.
For a network it calls as-overview for the holder’s name, routing-status for its visibility, announced-prefixes for its address blocks, asn-neighbours for the networks on either side and routing-history for how its announcements grew; a prefix or an address goes to prefix-overview, routing-status and rir, and the opening panel uses whats-my-ip and network-info to find your own connection’s place. Upstream neighbours, drawn on the left, carry a network towards the rest of the internet; downstream ones, on the right, are carried by it. Visibility is shown as how many of the collectors’ peers see a route, out of all of them.
It reports what the collectors see now, and does not test whether a route works from where you are; your lookups go to RIPEstat and nowhere else. The same name’s DNS answers are on Resolver, a probe from your own browser on Network, the cables under the sea on Undersea, and how all of it came to be on History of the Internet.
Method
One measurement wire.
The source is the collectors
Everything comes from RIPEstat — the RIPE NCC’s public data service over RIS, a worldwide network of route collectors peering with real routers. Keyless, CORS-open, fetched browser-direct with no relay. The figures are the wire’s own answers at the moment you ask.
Left and right, said plainly
BGP’s jargon is kept but translated: a left neighbour sits between a network and the wider internet (its upstream); a right neighbour is carried by it. Visibility counts how many collectors currently see a route — the closest thing the internet has to “does this exist”.
The drawn history is an envelope
The history chart accumulates the opening of announcement timeline segments as RIS recorded them — the shape of a network’s growth, not a per-day audit. Very large networks sometimes exceed the history call’s patience; the page says so rather than drawing a fragment as the whole.
Your address stays yours
The opening panel asks the wire what address this connection came from and where it sits; that answer is drawn on your screen and kept nowhere. Lookups you type go to the measurement service and to no one else.