BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.184.0.0/17
Announced exactly
- 64.184.0.0/17AS32703Zayo BandwidthRPKI Valid64.184.0.0
- Registry
- ARIN · United States · Jul 28, 2004
- Delegated block
- 64.184.0.0 – 64.184.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.184.1.0/24AS32703Zayo BandwidthRPKI Valid64.184.1.0
- 64.184.2.0/23AS32703Zayo BandwidthRPKI Valid64.184.2.0
- 64.184.4.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.4.0
- 64.184.5.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.5.0
- 64.184.6.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.6.0
- 64.184.7.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.7.0
- 64.184.8.0/21AS11525Hancock Rural Telephone Corp.RPKI Valid64.184.8.0
- 64.184.16.0/22AS54209Monon Telephone Company, Inc.RPKI Valid64.184.16.0
- 64.184.22.0/24AS54209Monon Telephone Company, Inc.RPKI Valid64.184.22.0
- 64.184.32.0/20AS22110Ligtel Communications, Inc.RPKI Valid64.184.32.0
- 64.184.48.0/20AS11118ComTeckRPKI Valid64.184.48.0
- 64.184.74.0/24AS400017Ruoff MortgageRPKI Valid64.184.74.0
- 64.184.80.0/21AS3131Tele-Media SolutionsRPKI Valid64.184.80.0
- 64.184.80.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.80.0
- 64.184.81.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.81.0
- 64.184.82.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.82.0
- 64.184.83.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.83.0
- 64.184.84.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.84.0
- 64.184.85.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.85.0
- 64.184.86.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.86.0
- 64.184.87.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.87.0
- 64.184.94.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.94.0
- 64.184.95.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.95.0
- 64.184.96.0/24AS19112New Lisbon Telephone Co., INCRPKI Valid64.184.96.0
- 64.184.97.0/24AS19112New Lisbon Telephone Co., INCRPKI Valid64.184.97.0
- 64.184.98.0/24AS19112New Lisbon Telephone Co., INCRPKI Valid64.184.98.0
- 64.184.100.0/22AS22110Ligtel Communications, Inc.RPKI Valid64.184.100.0
- 64.184.105.0/24AS32703Zayo BandwidthRPKI Valid64.184.105.0
- 64.184.107.0/24AS19112New Lisbon Telephone Co., INCRPKI Valid64.184.107.0
- 64.184.111.0/24AS400385Citizens Telephone CorporationRPKI Valid64.184.111.0
- 64.184.112.0/22AS3131Tele-Media SolutionsRPKI Valid64.184.112.0
- 64.184.112.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.112.0
- 64.184.113.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.113.0
- 64.184.114.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.114.0
- 64.184.115.0/24AS3131Tele-Media SolutionsRPKI Valid64.184.115.0
- 64.184.116.0/22AS22110Ligtel Communications, Inc.RPKI Valid64.184.116.0
- 64.184.120.0/21AS55230Pulaski White Rural Telephone Cooperative Inc.RPKI Valid64.184.120.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.