BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
97.65.0.0/16
Announced exactly
- 97.65.0.0/16AS3549Level 3 Parent, LLCRPKI Not found97.65.0.0
- Registry
- ARIN · United States · May 14, 2008
- Delegated block
- 97.65.0.0 – 97.65.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 97.65.3.0/24AS62802Macy's Systems and Technology, Inc.RPKI Valid97.65.3.0
- 97.65.7.0/24AS395955Interline Brands, Inc.RPKI Not found97.65.7.0
- 97.65.10.0/24AS395572Clear Winds Technologies IncorporatedRPKI Not found97.65.10.0
- 97.65.14.0/24AS23509Inventory Locator Service, LLCRPKI Not found97.65.14.0
- 97.65.15.0/24AS53626Corus360RPKI Not found97.65.15.0
- 97.65.16.0/23AS14652COSTAR GROUP Inc.RPKI Not found97.65.16.0
- 97.65.22.0/24AS46672Cologix, IncRPKI Not found97.65.22.0
- 97.65.42.0/24AS27414Caris Diagnostics, Inc.RPKI Not found97.65.42.0
- 97.65.55.0/24AS26489Polunsky & BeitelRPKI Not found97.65.55.0
- 97.65.67.0/24AS32899Bresco BroadbandRPKI Not found97.65.67.0
- 97.65.68.0/24AS32899Bresco BroadbandRPKI Not found97.65.68.0
- 97.65.80.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.80.0
- 97.65.84.0/23AS401333CeraNet, Inc.RPKI Not found97.65.84.0
- 97.65.86.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.86.0
- 97.65.87.0/24AS62802Macy's Systems and Technology, Inc.RPKI Valid97.65.87.0
- 97.65.91.0/24AS10753Level 3 Parent, LLCRPKI Not found97.65.91.0
- 97.65.105.0/24AS21928T-Mobile USA, Inc.RPKI Valid97.65.105.0
- 97.65.113.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.113.0
- 97.65.139.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.139.0
- 97.65.144.0/24AS36736UT Medical GroupRPKI Not found97.65.144.0
- 97.65.157.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.157.0
- 97.65.159.0/24AS11273Fiserv Solutions, LLCRPKI Not found97.65.159.0
- 97.65.163.0/24AS10753Level 3 Parent, LLCRPKI Not found97.65.163.0
- 97.65.179.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.179.0
- 97.65.181.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.181.0
- 97.65.184.0/24AS3356Level 3 Parent, LLCRPKI Not found97.65.184.0
- 97.65.198.0/24AS13915Radiology Imaging Associates P.C.RPKI Not found97.65.198.0
- 97.65.200.0/21AS3549Level 3 Parent, LLCRPKI Not found97.65.200.0
- 97.65.200.0/24AS19233Dialogix TelecomRPKI Not found97.65.200.0
- 97.65.205.0/24AS19233Dialogix TelecomRPKI Not found97.65.205.0
- 97.65.208.0/24AS32411AssureRx Health, Inc.RPKI Not found97.65.208.0
- 97.65.210.0/24AS26219Deli ExpressRPKI Not found97.65.210.0
- 97.65.216.0/23AS30305Black Knight IP Holding Company, LLCRPKI Not found97.65.216.0
- 97.65.222.0/24AS395176Encore TechnologiesRPKI Not found97.65.222.0
- 97.65.224.0/24AS5777Ribbon Communications Operating Company, Inc.RPKI Not found97.65.224.0
- 97.65.234.0/24AS11962Empire Today LLCRPKI Not found97.65.234.0
- 97.65.241.0/24AS10753Level 3 Parent, LLCRPKI Not found97.65.241.0
- 97.65.249.0/24AS54321ENETSolutions L.L.CRPKI Not found97.65.249.0
- 97.65.254.0/24AS396155City of ArlingtonRPKI Not found97.65.254.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.