BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a03:4b47::/32
Announced exactly
- 2a03:4b47::/32AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47::
- Registry
- RIPE NCC · United Arab Emirates · Nov 7, 2012
- Delegated block
- 2a03:4b40:: – 2a03:4b47:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a03:4b47:700::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:700::
- 2a03:4b47:710::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:710::
- 2a03:4b47:720::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:720::
- 2a03:4b47:730::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:730::
- 2a03:4b47:734::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:734::
- 2a03:4b47:738::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:738::
- 2a03:4b47:740::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:740::
- 2a03:4b47:748::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:748::
- 2a03:4b47:758::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:758::
- 2a03:4b47:760::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:760::
- 2a03:4b47:768::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:768::
- 2a03:4b47:770::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:770::
- 2a03:4b47:778::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:778::
- 2a03:4b47:780::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:780::
- 2a03:4b47:790::/46AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:790::
- 2a03:4b47:1000::/48AS199739Earthlink Telecommunications Equipment Trading & Services DMCCRPKI Valid2a03:4b47:1000::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. 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.