BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.125.0.0/16
Announced exactly
- 64.125.0.0/16AS6461Zayo BandwidthRPKI Valid64.125.0.0
- Registry
- ARIN · United States · Jul 6, 2000
- Delegated block
- 64.125.0.0 – 64.125.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.125.44.0/24AS21691Toyota Motor Credit CorporationRPKI Valid64.125.44.0
- 64.125.66.0/24AS14056SEI InvestmentsRPKI Valid64.125.66.0
- 64.125.74.0/24AS6461Zayo BandwidthRPKI Valid64.125.74.0
- 64.125.77.0/24AS25755National Public Radio, Inc.RPKI Valid64.125.77.0
- 64.125.87.0/24AS7170Manhattan West, LLCRPKI Valid64.125.87.0
- 64.125.96.0/24AS30419PaeDae, Inc.RPKI Valid64.125.96.0
- 64.125.97.0/24AS63474Sirius Computer Solutions, Inc.RPKI Valid64.125.97.0
- 64.125.98.0/24AS14147Bank-Fund Staff Federal Credit UnionRPKI Valid64.125.98.0
- 64.125.105.0/24AS36376Cheniere Energy, Inc.RPKI Valid64.125.105.0
- 64.125.106.0/24AS398731Goodman Manufacturing Company, L.P.RPKI Valid64.125.106.0
- 64.125.111.0/24AS53802382 Communications CorporationRPKI Valid64.125.111.0
- 64.125.114.0/24AS53294Fox News ChannelRPKI Valid64.125.114.0
- 64.125.133.0/24AS393631UNASSIGNEDRPKI Valid64.125.133.0
- 64.125.134.0/24AS393631UNASSIGNEDRPKI Valid64.125.134.0
- 64.125.135.0/24AS13955Echostar Broadcasting CorporationRPKI Valid64.125.135.0
- 64.125.160.0/21AS33481BELWAVE COMMUNICATIONS, INC.RPKI Valid64.125.160.0
- 64.125.169.0/24AS17025Zayo BandwidthRPKI Valid64.125.169.0
- 64.125.227.0/24AS17025Zayo BandwidthRPKI Valid64.125.227.0
- 64.125.229.0/24AS17025Zayo BandwidthRPKI Valid64.125.229.0
- 64.125.236.0/24AS32187UNASSIGNEDRPKI Valid64.125.236.0
- 64.125.239.0/24AS20293THE WESTERN UNION COMPANYRPKI Valid64.125.239.0
- 64.125.250.0/24AS54999Tenaris Global Services (USA) Corp.RPKI Valid64.125.250.0
- 64.125.251.0/24AS13344NetEx Inc.RPKI Valid64.125.251.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.