BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2607:fda8::/32
Announced exactly
- 2607:fda8::/32AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8::
- Registry
- ARIN · United States · Oct 15, 2009
- Delegated block
- 2607:fda8:: – 2607:fda8:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2607:fda8:4::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:4::
- 2607:fda8:1001::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1001::
- 2607:fda8:1003::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1003::
- 2607:fda8:1005::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1005::
- 2607:fda8:1006::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1006::
- 2607:fda8:1007::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1007::
- 2607:fda8:1008::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1008::
- 2607:fda8:1010::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1010::
- 2607:fda8:1011::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1011::
- 2607:fda8:1012::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1012::
- 2607:fda8:1013::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1013::
- 2607:fda8:1014::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1014::
- 2607:fda8:1015::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1015::
- 2607:fda8:1020::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1020::
- 2607:fda8:1021::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1021::
- 2607:fda8:1022::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1022::
- 2607:fda8:1023::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1023::
- 2607:fda8:1026::/48AS36224HCL AMERICA INCRPKI Valid2607:fda8:1026::
- 2607:fda8:1028::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1028::
- 2607:fda8:1029::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:1029::
- 2607:fda8:8000::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8000::
- 2607:fda8:8003::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8003::
- 2607:fda8:8004::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8004::
- 2607:fda8:8007::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8007::
- 2607:fda8:8008::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8008::
- 2607:fda8:800a::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:800a::
- 2607:fda8:800b::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:800b::
- 2607:fda8:800c::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:800c::
- 2607:fda8:800d::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:800d::
- 2607:fda8:800e::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:800e::
- 2607:fda8:8010::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8010::
- 2607:fda8:8011::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8011::
- 2607:fda8:8012::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8012::
- 2607:fda8:8013::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8013::
- 2607:fda8:8014::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8014::
- 2607:fda8:8015::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8015::
- 2607:fda8:8017::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:8017::
- 2607:fda8:801b::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:801b::
- 2607:fda8:801c::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:801c::
- 2607:fda8:801f::/48AS54004Cablevision Lightpath LLCRPKI Valid2607:fda8:801f::
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.