BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:480::/32
Announced exactly
- 2001:480::/32AS668United States Department of Defense (DoD)RPKI Not found2001:480::
- Registry
- ARIN · United States · Jun 14, 2001
- Delegated block
- 2001:480:: – 2001:480:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:480:10::/48AS22Navy Network Information Center (NNIC)RPKI Not found2001:480:10::
- 2001:480:20::/48AS48Navy Network Information Center (NNIC)RPKI Not found2001:480:20::
- 2001:480:23::/48AS5058Navy Network Information Center (NNIC)RPKI Not found2001:480:23::
- 2001:480:30::/48AS13Headquarters, USAISCRPKI Not found2001:480:30::
- 2001:480:31::/48AS5887United States Department of Defense (DoD)RPKI Not found2001:480:31::
- 2001:480:34::/48AS252Headquarters, USAISCRPKI Not found2001:480:34::
- 2001:480:50::/48AS6043United States Department of Defense (DoD)RPKI Not found2001:480:50::
- 2001:480:51::/48AS6009United States Department of Defense (DoD)RPKI Not found2001:480:51::
- 2001:480:52::/48AS4221United States Department of Defense (DoD)RPKI Not found2001:480:52::
- 2001:480:60::/48AS5957United States Department of Defense (DoD)RPKI Not found2001:480:60::
- 2001:480:90::/48AS5980United States Department of Defense (DoD)RPKI Not found2001:480:90::
- 2001:480:95::/48AS4221United States Department of Defense (DoD)RPKI Not found2001:480:95::
- 2001:480:a0::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:a0::
- 2001:480:a1::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:a1::
- 2001:480:aa::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:aa::
- 2001:480:ab::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:ab::
- 2001:480:b0::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:b0::
- 2001:480:120::/48AS3381Maui High Performance Computing CenterRPKI Not found2001:480:120::
- 2001:480:240::/48AS687United States Department of Defense (DoD)RPKI Not found2001:480:240::
- 2001:480:280::/48AS366United States Department of Defense (DoD)RPKI Not found2001:480:280::
- 2001:480:421::/48AS518United States Department of Defense (DoD)RPKI Not found2001:480:421::
- 2001:480:501::/48AS37Navy Network Information Center (NNIC)RPKI Not found2001:480:501::
- 2001:480:540::/48AS89Navy Network Information Center (NNIC)RPKI Not found2001:480:540::
- 2001:480:560::/48AS22Navy Network Information Center (NNIC)RPKI Not found2001:480:560::
- 2001:480:630::/48AS84Navy Network Information Center (NNIC)RPKI Not found2001:480:630::
- 2001:480:740::/48AS289Headquarters, USAISCRPKI Not found2001:480:740::
- 2001:480:1610::/48AS518United States Department of Defense (DoD)RPKI Not found2001:480:1610::
- 2001:480:1670::/48AS213Headquarters, USAISCRPKI Not found2001:480:1670::
- 2001:480:1801::/48AS5132United States Department of Defense (DoD)RPKI Not found2001:480:1801::
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.