BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
67.96.0.0/14
Announced exactly
- 67.96.0.0/14AS3356Level 3 Parent, LLCRPKI Not found67.96.0.0
- Registry
- ARIN · United States · Aug 7, 2001
- Delegated block
- 67.96.0.0 – 67.99.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 67.96.16.0/22AS62CyrusOne LLCRPKI Not found67.96.16.0
- 67.96.20.0/24AS62CyrusOne LLCRPKI Not found67.96.20.0
- 67.96.24.0/21AS62CyrusOne LLCRPKI Not found67.96.24.0
- 67.96.104.0/24AS3356Level 3 Parent, LLCRPKI Not found67.96.104.0
- 67.96.122.0/24AS15065Slic Network Solutions, IncRPKI Not found67.96.122.0
- 67.97.8.0/24AS3356Level 3 Parent, LLCRPKI Not found67.97.8.0
- 67.97.112.0/24AS8119DTN, LLCRPKI Not found67.97.112.0
- 67.97.132.0/24AS32342Genex Services IncRPKI Not found67.97.132.0
- 67.97.201.0/24AS15065Slic Network Solutions, IncRPKI Not found67.97.201.0
- 67.97.216.0/21AS13433Cox Enterprises IncRPKI Not found67.97.216.0
- 67.97.218.0/23AS393340Cox Enterprises IncRPKI Not found67.97.218.0
- 67.97.222.0/23AS393340Cox Enterprises IncRPKI Not found67.97.222.0
- 67.97.245.0/24AS16493Abercrombie & FitchRPKI Valid67.97.245.0
- 67.97.247.0/24AS46887Crown Castle Fiber LLCRPKI Not found67.97.247.0
- 67.98.88.0/24AS23384Reed Technology and Information Services, Inc.RPKI Not found67.98.88.0
- 67.98.95.0/24AS13652HORIZON BLUE CROSS BLUE SHIELD OF NJRPKI Not found67.98.95.0
- 67.98.107.0/24AS3356Level 3 Parent, LLCRPKI Not found67.98.107.0
- 67.98.160.0/21AS9246Teleguam Holdings, LLCRPKI Not found67.98.160.0
- 67.98.173.0/24AS797AT&T Services, Inc.RPKI Not found67.98.173.0
- 67.98.187.0/24AS54174BlueCross BlueShield of TennesseeRPKI Not found67.98.187.0
- 67.98.192.0/24AS16618Finastra USA CorporationRPKI Not found67.98.192.0
- 67.98.241.0/24AS23081CONVERGEONE HOLDINGS, INC.RPKI Not found67.98.241.0
- 67.99.160.0/20AS3685State University of New York at BuffaloRPKI Not found67.99.160.0
- 67.99.196.0/23AS22362Global Tel*link CorporationRPKI Not found67.99.196.0
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.