BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.53.64.0/18
Announced exactly
- 64.53.64.0/18AS2711Spirit CommunicationsRPKI Not found64.53.64.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.67.0/24AS10279West Carolina Communications, LLCRPKI Not found64.53.67.0
- 64.53.68.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.68.0
- 64.53.69.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.69.0
- 64.53.71.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.71.0
- 64.53.72.0/24AS19212Piedmont Rural Telephone Cooperative, IncorporatedRPKI Not found64.53.72.0
- 64.53.73.0/24AS19212Piedmont Rural Telephone Cooperative, IncorporatedRPKI Not found64.53.73.0
- 64.53.74.0/24AS19212Piedmont Rural Telephone Cooperative, IncorporatedRPKI Not found64.53.74.0
- 64.53.75.0/24AS19212Piedmont Rural Telephone Cooperative, IncorporatedRPKI Not found64.53.75.0
- 64.53.77.0/24AS14615Comporium, IncRPKI Not found64.53.77.0
- 64.53.79.0/24AS29897ATG Communications, LLCRPKI Not found64.53.79.0
- 64.53.81.0/24AS27563Spirit CommunicationsRPKI Not found64.53.81.0
- 64.53.85.0/24AS2711Spirit CommunicationsRPKI Not found64.53.85.0
- 64.53.86.0/24AS2711Spirit CommunicationsRPKI Not found64.53.86.0
- 64.53.88.0/24AS12208TruVista CommunicationsRPKI Not found64.53.88.0
- 64.53.89.0/24AS12208TruVista CommunicationsRPKI Not found64.53.89.0
- 64.53.91.0/24AS14615Comporium, IncRPKI Not found64.53.91.0
- 64.53.93.0/24AS14615Comporium, IncRPKI Not found64.53.93.0
- 64.53.98.0/24AS22646Hargray Communications Group, Inc.RPKI Not found64.53.98.0
- 64.53.99.0/24AS26903City of Salisbury, North CarolinaRPKI Not found64.53.99.0
- 64.53.100.0/24AS10279West Carolina Communications, LLCRPKI Not found64.53.100.0
- 64.53.102.0/24AS16863Home Telephone Company, Inc.RPKI Not found64.53.102.0
- 64.53.103.0/24AS27563Spirit CommunicationsRPKI Not found64.53.103.0
- 64.53.107.0/24AS19212Piedmont Rural Telephone Cooperative, IncorporatedRPKI Not found64.53.107.0
- 64.53.113.0/24AS397460Beaufort County GovernmentRPKI Not found64.53.113.0
- 64.53.114.0/24AS10279West Carolina Communications, LLCRPKI Not found64.53.114.0
- 64.53.116.0/24AS2711Spirit CommunicationsRPKI Not found64.53.116.0
- 64.53.125.0/24AS2711Spirit CommunicationsRPKI Not found64.53.125.0
- 64.53.126.0/24AS40641MGW Telephone Company, Inc.RPKI Not found64.53.126.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.