BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a13:a5c6::/32
Announced exactly
- 2a13:a5c6::/32AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6::
- Registry
- RIPE NCC · United Kingdom · Aug 8, 2023
- Delegated block
- 2a13:a5c0:: – 2a13:a5c7:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a13:a5c6:1000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:1000::
- 2a13:a5c6:101d::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:101d::
- 2a13:a5c6:101e::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:101e::
- 2a13:a5c6:101f::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:101f::
- 2a13:a5c6:1020::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:1020::
- 2a13:a5c6:1021::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:1021::
- 2a13:a5c6:1fff::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:1fff::
- 2a13:a5c6:2000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:2000::
- 2a13:a5c6:2f00::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:2f00::
- 2a13:a5c6:2f0f::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:2f0f::
- 2a13:a5c6:2f10::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:2f10::
- 2a13:a5c6:3000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3000::
- 2a13:a5c6:3100::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3100::
- 2a13:a5c6:3200::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3200::
- 2a13:a5c6:3a00::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3a00::
- 2a13:a5c6:3b01::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3b01::
- 2a13:a5c6:3b02::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3b02::
- 2a13:a5c6:3c00::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3c00::
- 2a13:a5c6:3c01::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:3c01::
- 2a13:a5c6:4000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4000::
- 2a13:a5c6:40b1::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:40b1::
- 2a13:a5c6:4100::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4100::
- 2a13:a5c6:4101::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4101::
- 2a13:a5c6:4102::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4102::
- 2a13:a5c6:4103::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4103::
- 2a13:a5c6:4a09::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4a09::
- 2a13:a5c6:4aa1::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4aa1::
- 2a13:a5c6:4aa2::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4aa2::
- 2a13:a5c6:4aa3::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4aa3::
- 2a13:a5c6:4aa4::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4aa4::
- 2a13:a5c6:4aa5::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:4aa5::
- 2a13:a5c6:5000::/36AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:5000::
- 2a13:a5c6:5f00::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:5f00::
- 2a13:a5c6:6100::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6100::
- 2a13:a5c6:6300::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6300::
- 2a13:a5c6:6600::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6600::
- 2a13:a5c6:6700::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6700::
- 2a13:a5c6:6800::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6800::
- 2a13:a5c6:6801::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:6801::
- 2a13:a5c6:7300::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:7300::
- 2a13:a5c6:7400::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:7400::
- 2a13:a5c6:7500::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:7500::
- 2a13:a5c6:7501::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:7501::
- 2a13:a5c6:7600::/40AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:7600::
- 2a13:a5c6:902c::/48AS201217RADISHCLOUD TECHNOLOGY LLCRPKI Valid2a13:a5c6:902c::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.