Network · data from 2026-11-12
AS24085 QTSC-AS-VN - Quang Trung Software City Development Company
Registry name: QTSC-AS-VN - Quang Trung Software City Development Company, VN · not in PeeringDB
105IPv4 routes
98.1% RPKI valid · 100.0% with a route object
5IPv6 routes
100.0% RPKI valid · 20.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
4 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
151Route objects not announced
registered with origin AS24085, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24085, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 103.45.229.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.45.230.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 2403:6000::/40 | Valid | Nonecovered by 2403:6000::/32 | 636 100% |
| 2403:6000:100::/40 | Valid | Nonecovered by 2403:6000::/32 | 636 100% |
| 2403:6000:800::/40 | Valid | Nonecovered by 2403:6000::/32 | 636 100% |
| 2403:6000:7000::/40 | Valid | Nonecovered by 2403:6000::/32 | 636 100% |
| 116.193.64.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 116.193.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.75.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.193.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.80.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.80.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.81.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.82.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.83.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.96.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.96.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.100.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.102.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.103.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.106.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.107.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.108.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.109.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.110.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.111.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.116.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.117.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.118.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.119.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 120.72.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 120.72.124.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.224.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.225.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.78.226.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.78.227.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.228.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.229.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.230.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.78.231.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 116.193.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.64.0/18 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.75.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.94.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.96.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 210.2.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.100.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.106.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.108.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.111.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.125.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 210.2.97.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 210.2.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 2403:6000::/32 | Valid | RIR databaseAPNIC, NTTCOM | 636 100% |
| 120.72.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 2 0%low visibility |
AS-SET
AS24085 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 159 are in fix.csv.
- ROA: none2
- Route object: none4
- Route object: RIR2
- Route object: not announced151
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.45.229.0/24 | No ROA covers it. Add a ROA for AS24085, maxLength 24. |
| Route object: RIR | 103.45.229.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.45.230.0/24 | No ROA covers it. Add a ROA for AS24085, maxLength 24. |
| Route object: RIR | 103.45.230.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: none | 2403:6000::/40 | No route object for it. A route object for 2403:6000::/32 with origin AS24085 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24085 in the RIR database for the space. |
| Route object: none | 2403:6000:100::/40 | No route object for it. A route object for 2403:6000::/32 with origin AS24085 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24085 in the RIR database for the space. |
| Route object: none | 2403:6000:800::/40 | No route object for it. A route object for 2403:6000::/32 with origin AS24085 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24085 in the RIR database for the space. |
| Route object: none | 2403:6000:7000::/40 | No route object for it. A route object for 2403:6000::/32 with origin AS24085 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24085 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24085 whose prefix no peer sees AS24085 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.45.228.0/22 | NTTCOM, RADB | No ROA |
| 103.45.228.0/24 | NTTCOM | No ROA |
| 103.45.231.0/24 | NTTCOM | No ROA |
| 116.193.64.0/21 | APNIC, NTTCOM, RADB | Valid |
| 116.193.64.0/22 | APNIC, NTTCOM, RADB | Valid |
| 116.193.64.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.66.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.68.0/22 | APNIC, NTTCOM, RADB | Valid |
| 116.193.68.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.70.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.72.0/21 | APNIC, NTTCOM, RADB | Valid |
| 116.193.72.0/22 | APNIC, NTTCOM, RADB | Valid |
| 116.193.72.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.74.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 116.193.76.0/23 | APNIC, NTTCOM, RADB | Valid |
| 116.193.78.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.80.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.80.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.82.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.84.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.84.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.86.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.96.0/20 | APNIC, NTTCOM, RADB | Valid |
| 120.72.96.0/21 | APNIC, NTTCOM, RADB | Valid |
| 120.72.96.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.96.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.97.0/24 | APNIC, NTTCOM, RADB | Valid |
| 120.72.98.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.100.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.100.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.101.0/24 | APNIC, NTTCOM, RADB | Valid |
| 120.72.102.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.104.0/21 | APNIC, NTTCOM, RADB | Valid |
| 120.72.104.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.104.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.104.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 120.72.105.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 120.72.106.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.108.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.108.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.110.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.112.0/20 | APNIC, NTTCOM, RADB | Valid |
| 120.72.112.0/21 | APNIC, NTTCOM, RADB | Valid |
| 120.72.112.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.112.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.114.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.115.0/24 | APNIC, NTTCOM, RADB | Valid |
| 120.72.116.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.116.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.118.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.120.0/21 | APNIC, NTTCOM, RADB | Valid |
| 120.72.120.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.120.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.121.0/24 | APNIC, NTTCOM, RADB, REACH | Valid |
| 120.72.122.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.124.0/22 | APNIC, NTTCOM, RADB | Valid |
| 120.72.124.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.125.0/24 | APNIC, NTTCOM, RADB | Valid |
| 120.72.126.0/23 | APNIC, NTTCOM, RADB | Valid |
| 120.72.126.0/24 | APNIC, NTTCOM, RADB | Valid |
| 120.72.127.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.78.224.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.78.224.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.78.226.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.78.228.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.78.228.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.78.230.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.64.0/19 | APNIC, NTTCOM, RADB | Valid |
| 210.2.64.0/20 | APNIC, NTTCOM, RADB | Valid |
| 210.2.64.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.64.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.64.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.65.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.66.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.68.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.68.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.70.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.72.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.72.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.72.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.74.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.76.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.78.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.80.0/20 | APNIC, NTTCOM, RADB | Valid |
| 210.2.80.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.80.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.80.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.80.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.81.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.82.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.82.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.83.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.84.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.84.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.86.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.88.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.88.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.88.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.90.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.92.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.92.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.94.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.96.0/19 | APNIC, NTTCOM, RADB | Valid |
| 210.2.96.0/20 | APNIC, NTTCOM, RADB | Valid |
| 210.2.96.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.96.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.96.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.98.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.100.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.100.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.101.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.102.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.102.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.103.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.104.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.104.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.104.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.104.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.105.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.106.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.107.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.108.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.108.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.109.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.110.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.110.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.112.0/20 | APNIC, NTTCOM, RADB | Valid |
| 210.2.112.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.112.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.112.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.114.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.116.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.116.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.116.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.117.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.118.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.118.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.119.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.120.0/21 | APNIC, NTTCOM, RADB | Valid |
| 210.2.120.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.120.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.122.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.123.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.124.0/22 | APNIC, NTTCOM, RADB | Valid |
| 210.2.124.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.124.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.126.0/23 | APNIC, NTTCOM, RADB | Valid |
| 210.2.126.0/24 | APNIC, NTTCOM, RADB | Valid |
| 210.2.127.0/24 | APNIC, NTTCOM, RADB | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.