BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a00:fb8::/29
Announced exactly
- 2a00:fb8::/29AS88811&1 Versatel GmbHRPKI Valid2a00:fb8::
- Registry
- RIPE NCC · Germany · Dec 10, 2008
- Delegated block
- 2a00:fb8:: – 2a00:fbf:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a00:fb8::/35AS88811&1 Versatel GmbHRPKI Valid2a00:fb8::
- 2a00:fb8:2000::/35AS88811&1 Versatel GmbHRPKI Valid2a00:fb8:2000::
- 2a00:fb8:4000::/35AS88811&1 Versatel GmbHRPKI Valid2a00:fb8:4000::
- 2a00:fb8:6000::/35AS88811&1 Versatel GmbHRPKI Valid2a00:fb8:6000::
- 2a00:fbc:1000::/36AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:1000::
- 2a00:fbc:2000::/36AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:2000::
- 2a00:fbc:3000::/36AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:3000::
- 2a00:fbc:4000::/36AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:4000::
- 2a00:fbc:5000::/36AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:5000::
- 2a00:fbc:d000::/38AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:d000::
- 2a00:fbc:d400::/38AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:d400::
- 2a00:fbc:d800::/38AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:d800::
- 2a00:fbc:dc00::/38AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:dc00::
- 2a00:fbc:e800::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:e800::
- 2a00:fbc:e900::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:e900::
- 2a00:fbc:ea00::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:ea00::
- 2a00:fbc:eb00::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:eb00::
- 2a00:fbc:ec00::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:ec00::
- 2a00:fbc:ee00::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:ee00::
- 2a00:fbc:ef00::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:ef00::
- 2a00:fbc:f000::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:f000::
- 2a00:fbc:f100::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:f100::
- 2a00:fbc:f200::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:f200::
- 2a00:fbc:f300::/40AS88811&1 Versatel GmbHRPKI Valid2a00:fbc:f300::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.