BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.8.192.0/18
Announced exactly
- 64.8.192.0/18AS3257GTT Communications Inc.RPKI Not found64.8.192.0
- Registry
- ARIN · United States · Feb 6, 2001
- Delegated block
- 64.8.192.0 – 64.8.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.8.192.0/24AS11404Wave BroadbandRPKI Valid64.8.192.0
- 64.8.193.0/24AS11404Wave BroadbandRPKI Valid64.8.193.0
- 64.8.194.0/24AS11404Wave BroadbandRPKI Valid64.8.194.0
- 64.8.195.0/24AS11404Wave BroadbandRPKI Valid64.8.195.0
- 64.8.196.0/24AS11404Wave BroadbandRPKI Valid64.8.196.0
- 64.8.197.0/24AS11404Wave BroadbandRPKI Valid64.8.197.0
- 64.8.198.0/24AS11404Wave BroadbandRPKI Valid64.8.198.0
- 64.8.199.0/24AS11404Wave BroadbandRPKI Valid64.8.199.0
- 64.8.200.0/24AS11404Wave BroadbandRPKI Valid64.8.200.0
- 64.8.201.0/24AS11404Wave BroadbandRPKI Valid64.8.201.0
- 64.8.202.0/24AS11404Wave BroadbandRPKI Valid64.8.202.0
- 64.8.203.0/24AS11404Wave BroadbandRPKI Valid64.8.203.0
- 64.8.204.0/24AS11404Wave BroadbandRPKI Valid64.8.204.0
- 64.8.205.0/24AS11404Wave BroadbandRPKI Valid64.8.205.0
- 64.8.206.0/24AS11404Wave BroadbandRPKI Valid64.8.206.0
- 64.8.207.0/24AS11404Wave BroadbandRPKI Valid64.8.207.0
- 64.8.208.0/24AS11404Wave BroadbandRPKI Valid64.8.208.0
- 64.8.209.0/24AS11404Wave BroadbandRPKI Valid64.8.209.0
- 64.8.210.0/24AS11404Wave BroadbandRPKI Valid64.8.210.0
- 64.8.211.0/24AS11404Wave BroadbandRPKI Valid64.8.211.0
- 64.8.212.0/24AS11404Wave BroadbandRPKI Valid64.8.212.0
- 64.8.213.0/24AS11404Wave BroadbandRPKI Valid64.8.213.0
- 64.8.214.0/24AS11404Wave BroadbandRPKI Valid64.8.214.0
- 64.8.215.0/24AS11404Wave BroadbandRPKI Valid64.8.215.0
- 64.8.216.0/24AS11404Wave BroadbandRPKI Valid64.8.216.0
- 64.8.217.0/24AS11404Wave BroadbandRPKI Valid64.8.217.0
- 64.8.218.0/24AS11404Wave BroadbandRPKI Valid64.8.218.0
- 64.8.219.0/24AS11404Wave BroadbandRPKI Valid64.8.219.0
- 64.8.220.0/24AS11404Wave BroadbandRPKI Valid64.8.220.0
- 64.8.221.0/24AS11404Wave BroadbandRPKI Valid64.8.221.0
- 64.8.222.0/24AS11404Wave BroadbandRPKI Valid64.8.222.0
- 64.8.223.0/24AS11404Wave BroadbandRPKI Valid64.8.223.0
- 64.8.224.0/23AS212238Datacamp LimitedRPKI Valid64.8.224.0
- 64.8.226.0/23AS30058FDCservers.netRPKI Valid64.8.226.0
- 64.8.228.0/23AS212238Datacamp LimitedRPKI Valid64.8.228.0
- 64.8.230.0/23AS212238Datacamp LimitedRPKI Valid64.8.230.0
- 64.8.232.0/23AS3320Deutsche Telekom AGRPKI Valid64.8.232.0
- 64.8.234.0/23AS212238Datacamp LimitedRPKI Valid64.8.234.0
- 64.8.236.0/23AS55470Cyfuture India Pvt. Ltd.RPKI Valid64.8.236.0
- 64.8.238.0/23AS212238Datacamp LimitedRPKI Valid64.8.238.0
- 64.8.240.0/24AS6079RCNRPKI Valid64.8.240.0
- 64.8.241.0/24AS6079RCNRPKI Valid64.8.241.0
- 64.8.242.0/24AS6079RCNRPKI Valid64.8.242.0
- 64.8.243.0/24AS6079RCNRPKI Valid64.8.243.0
- 64.8.244.0/24AS6079RCNRPKI Valid64.8.244.0
- 64.8.245.0/24AS6079RCNRPKI Valid64.8.245.0
- 64.8.246.0/24AS6079RCNRPKI Valid64.8.246.0
- 64.8.247.0/24AS6079RCNRPKI Valid64.8.247.0
- 64.8.248.0/24AS2914NTT America, Inc.RPKI Valid64.8.248.0
- 64.8.249.0/24AS2914NTT America, Inc.RPKI Valid64.8.249.0
- 64.8.250.0/24AS2914NTT America, Inc.RPKI Valid64.8.250.0
- 64.8.251.0/24AS2914NTT America, Inc.RPKI Valid64.8.251.0
- 64.8.252.0/24AS2914NTT America, Inc.RPKI Valid64.8.252.0
- 64.8.253.0/24AS2914NTT America, Inc.RPKI Valid64.8.253.0
- 64.8.255.0/24AS13335Cloudflare, Inc.RPKI Valid64.8.255.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.