BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.53.0.0/18
Announced exactly
- 64.53.0.0/18AS2711Spirit CommunicationsRPKI Not found64.53.0.0
- Registry
- ARIN · United States · Mar 7, 2000
- Delegated block
- 64.53.0.0 – 64.53.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.53.2.0/23AS19331Twin Lakes Telephone Cooperative CorporationRPKI Not found64.53.2.0
- 64.53.6.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.6.0
- 64.53.7.0/24AS16863Home Telephone Company, Inc.RPKI Not found64.53.7.0
- 64.53.11.0/24AS14615Comporium, IncRPKI Not found64.53.11.0
- 64.53.18.0/24AS396213USC UpstateRPKI Not found64.53.18.0
- 64.53.20.0/24AS19635Sandhill Telephone Cooperative, Inc.RPKI Not found64.53.20.0
- 64.53.22.0/24AS14615Comporium, IncRPKI Not found64.53.22.0
- 64.53.23.0/24AS16863Home Telephone Company, Inc.RPKI Not found64.53.23.0
- 64.53.25.0/24AS40641MGW Telephone Company, Inc.RPKI Not found64.53.25.0
- 64.53.27.0/24AS14615Comporium, IncRPKI Not found64.53.27.0
- 64.53.31.0/24AS16863Home Telephone Company, Inc.RPKI Not found64.53.31.0
- 64.53.35.0/24AS12208TruVista CommunicationsRPKI Not found64.53.35.0
- 64.53.36.0/24AS10279West Carolina Communications, LLCRPKI Not found64.53.36.0
- 64.53.52.0/24AS2711Spirit CommunicationsRPKI Not found64.53.52.0
- 64.53.58.0/24AS12208TruVista CommunicationsRPKI Not found64.53.58.0
- 64.53.59.0/24AS18671PRTCRPKI Not found64.53.59.0
- 64.53.61.0/24AS14615Comporium, IncRPKI Not found64.53.61.0
- 64.53.62.0/24AS14615Comporium, IncRPKI Not found64.53.62.0
- 64.53.63.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.63.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.