BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
63.240.0.0/15
Announced exactly
- 63.240.0.0/15AS7018AT&T Enterprises, LLCRPKI Not found63.240.0.0
- Registry
- ARIN · United States · Nov 3, 1999
- Delegated block
- 63.240.0.0 – 63.241.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 63.240.62.0/24AS399604EXL SERVICE.COM, LLCRPKI Not found63.240.62.0
- 63.240.102.0/24AS7105Dow Jones & Company, Inc.RPKI Not found63.240.102.0
- 63.240.119.0/24AS10257Tangoe US, Inc.RPKI Not found63.240.119.0
- 63.240.152.0/24AS2386AT&T Enterprises, LLCRPKI Valid63.240.152.0
- 63.240.165.0/24AS7018AT&T Enterprises, LLCRPKI Not found63.240.165.0
- 63.240.184.0/21AS3573Accenture LLPRPKI Not found63.240.184.0
- 63.241.40.0/24AS13788US CourtsRPKI Not found63.241.40.0
- 63.241.41.0/24AS13788US CourtsRPKI Not found63.241.41.0
- 63.241.42.0/24AS13788US CourtsRPKI Not found63.241.42.0
- 63.241.44.0/24AS2386AT&T Enterprises, LLCRPKI Valid63.241.44.0
- 63.241.90.0/24AS53825Alameda Health SystemRPKI Not found63.241.90.0
- 63.241.103.0/24AS394803American National Standards InstituteRPKI Not found63.241.103.0
- 63.241.148.0/24AS27271United Rentals North America, Inc.RPKI Not found63.241.148.0
- 63.241.163.0/24AS400858ARRIVIA, INC.RPKI Not found63.241.163.0
- 63.241.166.0/24AS27271United Rentals North America, Inc.RPKI Not found63.241.166.0
- 63.241.172.0/24AS400858ARRIVIA, INC.RPKI Not found63.241.172.0
- 63.241.197.0/24AS393360Tyler Technologies, Inc.RPKI Not found63.241.197.0
- 63.241.205.0/24AS393360Tyler Technologies, Inc.RPKI Not found63.241.205.0
- 63.241.223.0/24AS2386AT&T Enterprises, LLCRPKI Valid63.241.223.0
- 63.241.232.0/24AS393360Tyler Technologies, Inc.RPKI Not found63.241.232.0
- 63.241.244.0/24AS399014Essilor of America, Inc.RPKI Not found63.241.244.0
- 63.241.252.0/24AS14745Unitas GlobalRPKI Not found63.241.252.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.