BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
60.64.0.0/10
Announced exactly
- 60.64.0.0/10AS17676SoftBank Corp.RPKI Not found60.64.0.0
- Registry
- APNIC · Japan · May 20, 2004
- Delegated block
- 60.64.0.0 – 60.79.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 60.100.0.0/16AS17676SoftBank Corp.RPKI Valid60.100.0.0
- 60.101.0.0/16AS17676SoftBank Corp.RPKI Valid60.101.0.0
- 60.102.0.0/16AS17676SoftBank Corp.RPKI Valid60.102.0.0
- 60.103.0.0/16AS17676SoftBank Corp.RPKI Valid60.103.0.0
- 60.104.0.0/16AS17676SoftBank Corp.RPKI Valid60.104.0.0
- 60.105.0.0/16AS17676SoftBank Corp.RPKI Valid60.105.0.0
- 60.106.0.0/16AS17676SoftBank Corp.RPKI Valid60.106.0.0
- 60.107.0.0/16AS17676SoftBank Corp.RPKI Valid60.107.0.0
- 60.108.0.0/16AS17676SoftBank Corp.RPKI Valid60.108.0.0
- 60.109.0.0/16AS17676SoftBank Corp.RPKI Valid60.109.0.0
- 60.110.0.0/16AS17676SoftBank Corp.RPKI Valid60.110.0.0
- 60.111.0.0/16AS17676SoftBank Corp.RPKI Valid60.111.0.0
- 60.112.0.0/16AS17676SoftBank Corp.RPKI Valid60.112.0.0
- 60.113.0.0/16AS17676SoftBank Corp.RPKI Valid60.113.0.0
- 60.114.0.0/16AS17676SoftBank Corp.RPKI Valid60.114.0.0
- 60.115.0.0/16AS17676SoftBank Corp.RPKI Valid60.115.0.0
- 60.116.0.0/16AS17676SoftBank Corp.RPKI Valid60.116.0.0
- 60.117.0.0/16AS17676SoftBank Corp.RPKI Valid60.117.0.0
- 60.118.0.0/16AS17676SoftBank Corp.RPKI Valid60.118.0.0
- 60.119.0.0/16AS17676SoftBank Corp.RPKI Valid60.119.0.0
- 60.120.0.0/16AS17676SoftBank Corp.RPKI Valid60.120.0.0
- 60.121.0.0/16AS17676SoftBank Corp.RPKI Valid60.121.0.0
- 60.122.0.0/16AS17676SoftBank Corp.RPKI Valid60.122.0.0
- 60.124.0.0/16AS17676SoftBank Corp.RPKI Valid60.124.0.0
- 60.125.0.0/16AS17676SoftBank Corp.RPKI Valid60.125.0.0
- 60.126.0.0/16AS17676SoftBank Corp.RPKI Valid60.126.0.0
- 60.127.0.0/16AS17676SoftBank Corp.RPKI Valid60.127.0.0
- 60.64.0.0/16AS17676SoftBank Corp.RPKI Valid60.64.0.0
- 60.65.0.0/16AS17676SoftBank Corp.RPKI Valid60.65.0.0
- 60.66.0.0/16AS17676SoftBank Corp.RPKI Valid60.66.0.0
- 60.67.0.0/16AS17676SoftBank Corp.RPKI Valid60.67.0.0
- 60.68.0.0/16AS17676SoftBank Corp.RPKI Valid60.68.0.0
- 60.69.0.0/16AS17676SoftBank Corp.RPKI Valid60.69.0.0
- 60.70.0.0/16AS17676SoftBank Corp.RPKI Valid60.70.0.0
- 60.71.0.0/16AS17676SoftBank Corp.RPKI Valid60.71.0.0
- 60.72.0.0/16AS17676SoftBank Corp.RPKI Valid60.72.0.0
- 60.73.0.0/16AS17676SoftBank Corp.RPKI Valid60.73.0.0
- 60.74.0.0/16AS17676SoftBank Corp.RPKI Valid60.74.0.0
- 60.75.0.0/16AS17676SoftBank Corp.RPKI Valid60.75.0.0
- 60.76.0.0/16AS17676SoftBank Corp.RPKI Valid60.76.0.0
- 60.77.0.0/16AS17676SoftBank Corp.RPKI Valid60.77.0.0
- 60.78.0.0/16AS17676SoftBank Corp.RPKI Valid60.78.0.0
- 60.79.0.0/16AS17676SoftBank Corp.RPKI Valid60.79.0.0
- 60.80.0.0/16AS17676SoftBank Corp.RPKI Valid60.80.0.0
- 60.81.0.0/16AS17676SoftBank Corp.RPKI Valid60.81.0.0
- 60.82.0.0/16AS17676SoftBank Corp.RPKI Valid60.82.0.0
- 60.83.0.0/16AS17676SoftBank Corp.RPKI Valid60.83.0.0
- 60.84.0.0/16AS17676SoftBank Corp.RPKI Valid60.84.0.0
- 60.85.0.0/16AS17676SoftBank Corp.RPKI Valid60.85.0.0
- 60.86.0.0/16AS17676SoftBank Corp.RPKI Valid60.86.0.0
- 60.87.0.0/16AS17676SoftBank Corp.RPKI Not found60.87.0.0
- 60.88.0.0/16AS17676SoftBank Corp.RPKI Valid60.88.0.0
- 60.89.0.0/16AS17676SoftBank Corp.RPKI Valid60.89.0.0
- 60.90.0.0/16AS17676SoftBank Corp.RPKI Valid60.90.0.0
- 60.91.0.0/16AS17676SoftBank Corp.RPKI Valid60.91.0.0
- 60.92.0.0/16AS17676SoftBank Corp.RPKI Valid60.92.0.0
- 60.93.0.0/16AS17676SoftBank Corp.RPKI Valid60.93.0.0
- 60.94.0.0/16AS17676SoftBank Corp.RPKI Valid60.94.0.0
- 60.95.0.0/16AS17676SoftBank Corp.RPKI Valid60.95.0.0
- 60.96.0.0/16AS17676SoftBank Corp.RPKI Valid60.96.0.0
- 60.97.0.0/16AS17676SoftBank Corp.RPKI Valid60.97.0.0
- 60.98.0.0/16AS17676SoftBank Corp.RPKI Valid60.98.0.0
- 60.99.0.0/16AS17676SoftBank Corp.RPKI Valid60.99.0.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.