BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.203.192.0/18
Announced exactly
- 64.203.192.0/18AS22646Hargray Communications Group, Inc.RPKI Not found64.203.192.0
- Registry
- ARIN · United States · Oct 30, 2002
- Delegated block
- 64.203.192.0 – 64.203.223.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.203.192.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.192.0
- 64.203.193.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.193.0
- 64.203.194.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.194.0
- 64.203.195.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.195.0
- 64.203.196.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.196.0
- 64.203.197.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.197.0
- 64.203.198.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.198.0
- 64.203.199.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.199.0
- 64.203.200.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.200.0
- 64.203.201.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.201.0
- 64.203.202.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.202.0
- 64.203.203.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.203.0
- 64.203.204.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.204.0
- 64.203.205.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.205.0
- 64.203.208.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.208.0
- 64.203.209.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.209.0
- 64.203.210.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.210.0
- 64.203.211.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.211.0
- 64.203.212.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.212.0
- 64.203.213.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.213.0
- 64.203.214.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.214.0
- 64.203.215.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.215.0
- 64.203.216.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.216.0
- 64.203.217.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.217.0
- 64.203.218.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.218.0
- 64.203.220.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.220.0
- 64.203.222.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.222.0
- 64.203.223.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.223.0
- 64.203.224.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.224.0
- 64.203.224.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.224.0
- 64.203.227.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.227.0
- 64.203.228.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.228.0
- 64.203.229.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.229.0
- 64.203.230.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.230.0
- 64.203.231.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.231.0
- 64.203.232.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.232.0
- 64.203.233.0/24AS40702Clearwave CommunicationsRPKI Valid64.203.233.0
- 64.203.234.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.234.0
- 64.203.235.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.235.0
- 64.203.236.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.236.0
- 64.203.238.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.238.0
- 64.203.240.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.240.0
- 64.203.241.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.241.0
- 64.203.242.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.242.0
- 64.203.243.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.243.0
- 64.203.244.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.244.0
- 64.203.246.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.246.0
- 64.203.247.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.247.0
- 64.203.248.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.248.0
- 64.203.249.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.249.0
- 64.203.250.0/24AS400511Clearwave CommunicationsRPKI Not found64.203.250.0
- 64.203.251.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.251.0
- 64.203.252.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.252.0
- 64.203.253.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.203.253.0
- 64.203.254.0/23AS22646Hargray Communications Group, Inc.RPKI Not found64.203.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, 62.103.0.0/16. 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.