BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2604:6600::/32
Announced exactly
- 2604:6600::/32AS40676Psychz NetworksRPKI Valid2604:6600::
- Registry
- ARIN · United States · Nov 4, 2010
- Delegated block
- 2604:6600:: – 2604:6600:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2604:6600:5::/48AS40676Psychz NetworksRPKI Valid2604:6600:5::
- 2604:6600:7::/48AS40676Psychz NetworksRPKI Valid2604:6600:7::
- 2604:6600:a::/48AS40676Psychz NetworksRPKI Valid2604:6600:a::
- 2604:6600:e::/48AS40676Psychz NetworksRPKI Valid2604:6600:e::
- 2604:6600:25::/48AS40676Psychz NetworksRPKI Valid2604:6600:25::
- 2604:6600:4b::/48AS40676Psychz NetworksRPKI Valid2604:6600:4b::
- 2604:6600:77::/48AS40676Psychz NetworksRPKI Valid2604:6600:77::
- 2604:6600:99::/48AS40676Psychz NetworksRPKI Valid2604:6600:99::
- 2604:6600:9a::/48AS40676Psychz NetworksRPKI Valid2604:6600:9a::
- 2604:6600:9b::/48AS40676Psychz NetworksRPKI Valid2604:6600:9b::
- 2604:6600:a3::/48AS40676Psychz NetworksRPKI Valid2604:6600:a3::
- 2604:6600:2000::/48AS40676Psychz NetworksRPKI Valid2604:6600:2000::
- 2604:6600:2001::/48AS40676Psychz NetworksRPKI Valid2604:6600:2001::
- 2604:6600:2002::/48AS40676Psychz NetworksRPKI Valid2604:6600:2002::
- 2604:6600:2003::/48AS40676Psychz NetworksRPKI Valid2604:6600:2003::
- 2604:6600:2005::/48AS40676Psychz NetworksRPKI Valid2604:6600:2005::
- 2604:6600:2006::/48AS40676Psychz NetworksRPKI Valid2604:6600:2006::
- 2604:6600:2007::/48AS40676Psychz NetworksRPKI Valid2604:6600:2007::
- 2604:6600:2008::/48AS40676Psychz NetworksRPKI Valid2604:6600:2008::
- 2604:6600:2009::/48AS40676Psychz NetworksRPKI Valid2604:6600:2009::
- 2604:6600:2010::/48AS40676Psychz NetworksRPKI Valid2604:6600:2010::
- 2604:6600:2600::/40AS40676Psychz NetworksRPKI Valid2604:6600:2600::
- 2604:6600:2601::/48AS40676Psychz NetworksRPKI Valid2604:6600:2601::
- 2604:6600:2605::/48AS40676Psychz NetworksRPKI Valid2604:6600:2605::
- 2604:6600:2607::/48AS40676Psychz NetworksRPKI Valid2604:6600:2607::
- 2604:6600:2608::/48AS40676Psychz NetworksRPKI Valid2604:6600:2608::
- 2604:6600:2700::/40AS40676Psychz NetworksRPKI Valid2604:6600:2700::
- 2604:6600:fd00::/48AS40676Psychz NetworksRPKI Valid2604:6600:fd00::
- 2604:6600:fdb6::/48AS40676Psychz NetworksRPKI Valid2604:6600:fdb6::
- 2604:6600:fdc0::/48AS40676Psychz NetworksRPKI Valid2604:6600:fdc0::
- 2604:6600:fe7c::/48AS40676Psychz NetworksRPKI Valid2604:6600:fe7c::
- 2604:6600:fffb::/48AS40676Psychz NetworksRPKI Valid2604:6600:fffb::
- 2604:6600:fffc::/48AS40676Psychz NetworksRPKI Valid2604:6600:fffc::
- 2604:6600:fffd::/48AS40676Psychz NetworksRPKI Valid2604:6600:fffd::
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.