BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.51.0.0/16
Announced exactly
- 64.51.0.0/16AS3257GTT-BACKBONE GTTRPKI Not found64.51.0.0
- Registry
- ARIN · United States · Mar 3, 2000
- Delegated block
- 64.51.0.0 – 64.51.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.51.4.0/22AS7459Grande Communications Networks, LLCRPKI Valid64.51.4.0
- 64.51.12.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.12.0
- 64.51.13.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.13.0
- 64.51.14.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.14.0
- 64.51.15.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.15.0
- 64.51.16.0/22AS7459Grande Communications Networks, LLCRPKI Valid64.51.16.0
- 64.51.20.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.51.20.0
- 64.51.24.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.51.24.0
- 64.51.27.0/24AS63099MADEALA TELECOM TECHNOLOGY INCRPKI Valid64.51.27.0
- 64.51.28.0/22AS7459Grande Communications Networks, LLCRPKI Valid64.51.28.0
- 64.51.36.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.51.36.0
- 64.51.44.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.51.44.0
- 64.51.224.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.224.0
- 64.51.226.0/24AS199527BITE-LT-AS Bite Lietuva multihomed end-usersRPKI Not found64.51.226.0
- 64.51.232.0/23AS30058FDCservers.netRPKI Valid64.51.232.0
- 64.51.234.0/23AS212238CDNEXTRPKI Valid64.51.234.0
- 64.51.236.0/22AS11611Arctic Fox Networks IncRPKI Valid64.51.236.0
- 64.51.240.0/20AS11611Arctic Fox Networks IncRPKI Valid64.51.240.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.