BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:13b0::/31
Announced exactly
- 2001:13b0::/31AS3549Level 3 Parent, LLCRPKI Not found2001:13b0::
- Registry
- LACNIC · Argentina · Aug 4, 2005
- Delegated block
- 2001:13b0:: – 2001:13b7:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:13b0::/34AS3549Level 3 Parent, LLCRPKI Not found2001:13b0::
- 2001:13b0::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0::
- 2001:13b0:8000::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8000::
- 2001:13b0:8013::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:8013::
- 2001:13b0:8015::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:8015::
- 2001:13b0:8016::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8016::
- 2001:13b0:801a::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:801a::
- 2001:13b0:801e::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:801e::
- 2001:13b0:8020::/48AS272896COMSSET COMUNICACIONES SASRPKI Not found2001:13b0:8020::
- 2001:13b0:8021::/48AS3356Level 3 Parent, LLCRPKI Valid2001:13b0:8021::
- 2001:13b0:8025::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8025::
- 2001:13b0:8026::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8026::
- 2001:13b0:8027::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8027::
- 2001:13b0:8029::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:8029::
- 2001:13b0:8030::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:8030::
- 2001:13b0:a031::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:a031::
- 2001:13b0:a301::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:a301::
- 2001:13b0:b800::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:b800::
- 2001:13b0:b900::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:b900::
- 2001:13b0:bc00::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:bc00::
- 2001:13b0:bf04::/48AS3549Level 3 Parent, LLCRPKI Not found2001:13b0:bf04::
- 2001:13b0:c000::/48AS3356Level 3 Parent, LLCRPKI Not found2001:13b0:c000::
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.