bgpreport

Network · data from 2026-11-12

AS7482 APOL-AS - Asia Pacific On-line Service Inc.

Registry name: APOL-AS - Asia Pacific On-line Service Inc., TW · not in PeeringDB

76IPv4 routes 93.4% RPKI valid · 94.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
100Route objects not announced registered with origin AS7482, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7482, 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.

60.244.0.0/16 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.65.224.0/22 No ROA Other IRR onlyRADB 673 100% 67
203.65.228.0/24 No ROA Other IRR onlyRADB 671 100% 67
203.65.229.0/24 No ROA Other IRR onlyRADB 671 100% 67
203.65.230.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.178.180.0/24 Valid Other origin onlycovered by 202.178.160.0/19 673 100% 67
202.178.182.0/24 Valid Other origin onlycovered by 202.178.160.0/19 673 100% 67
210.200.67.0/24 Valid Other origin onlycovered by 210.200.64.0/19 672 100% 67
60.244.129.0/24 Valid Other origin onlycovered by 60.244.128.0/18 637 95% 67
60.244.0.0/18 Valid Other IRR onlyRADB 673 100% 67
60.244.64.0/18 Valid Other IRR onlyRADB 673 100% 67
60.244.128.0/18 Valid Other IRR onlyRADB 673 100% 67
60.244.192.0/18 Valid Other IRR onlyRADB 673 100% 67
124.218.0.0/16 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
124.218.0.0/18 Valid Other IRR onlyRADB 673 100% 67
124.218.64.0/18 Valid Other IRR onlyRADB 673 100% 67
124.218.128.0/18 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
124.218.192.0/18 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
124.219.0.0/17 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
124.219.0.0/18 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
203.79.128.0/17 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
203.79.128.0/18 Valid Other IRR onlyRADB 673 100% 67
203.79.192.0/18 Valid Other IRR onlyRADB 673 100% 67
219.91.0.0/17 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
219.91.0.0/18 Valid Other IRR onlyNTTCOM 673 100% 67
219.91.64.0/18 Valid Other IRR onlyNTTCOM 673 100% 67
222.156.0.0/16 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
222.156.0.0/18 Valid Other IRR onlyRADB 673 100% 67
222.156.28.0/24 Valid Other IRR onlyRADB 673 100% 67
222.156.64.0/18 Valid Other IRR onlyRADB 673 100% 67
222.156.128.0/18 Valid Other IRR onlyRADB 673 100% 67
222.156.192.0/18 Valid Other IRR onlyRADB 673 100% 67
202.178.245.0/24 Valid Other IRR onlyRADB 672 100% 67
210.58.0.0/16 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.58.0.0/18 Valid Other IRR onlyRADB 672 100% 67
210.58.64.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.58.128.0/18 Valid Other IRR onlyRADB 672 100% 67
210.58.192.0/18 Valid Other IRR onlyRADB 672 100% 67
210.200.0.0/16 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.200.64.0/19 Valid Other IRR onlyRADB 672 100% 67
210.200.96.0/19 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.200.105.0/24 Valid Other IRR onlyRADB 672 100% 67
210.200.128.0/18 Valid Other IRR onlyRADB 672 100% 67
210.200.192.0/18 Valid Other IRR onlyRADB 672 100% 67
210.201.0.0/16 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.201.0.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.201.30.0/24 Valid Other IRR onlyRADB 672 100% 67
210.201.64.0/18 Valid Other IRR onlyRADB 672 100% 67
210.201.128.0/18 Valid Other IRR onlyRADB 672 100% 67
210.201.192.0/18 Valid Other IRR onlyRADB 672 100% 67
210.202.64.0/18 Valid Other IRR onlyRADB 672 100% 67
210.202.128.0/18 Valid Other IRR onlyRADB 672 100% 67
210.202.192.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.203.0.0/17 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.203.0.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
210.203.64.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
218.35.0.0/18 Valid Other IRR onlyRADB 672 100% 67
218.35.64.0/18 Valid Other IRR onlyRADB 672 100% 67
218.35.128.0/18 Valid Other IRR onlyRADB 672 100% 67
218.35.192.0/18 Valid Other IRR onlyRADB 672 100% 67
218.187.0.0/16 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
218.187.0.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
218.187.64.0/18 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
218.187.128.0/18 Valid Other IRR onlyNTTCOM 672 100% 67
218.187.192.0/18 Valid Other IRR onlyNTTCOM 672 100% 67
222.156.220.0/24 Valid Other IRR onlyRADB 672 100% 67
223.22.0.0/18 Valid Other IRR onlyRADB 672 100% 67
210.200.86.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.96.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.98.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.100.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.111.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.135.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.189.0/24 Valid Other IRR onlyRADB 671 100% 67
210.200.212.0/24 Valid Other IRR onlyRADB 671 100% 67
223.22.66.0/24 Valid Other IRR onlyRADB 670 100% 67
2404:0:2000::/36 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS7482 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 182 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR73
  • Route object: not announced100
ChangePrefix or setDetailFull-table peers
ROA: none60.244.0.0/16No ROA covers it. Add a ROA for AS7482, maxLength 16.673 of 673
Route object: RIR60.244.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.65.224.0/22No ROA covers it. Add a ROA for AS7482, maxLength 22.673 of 673
Route object: RIR203.65.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.65.228.0/24No ROA covers it. Add a ROA for AS7482, maxLength 24.671 of 673
Route object: RIR203.65.228.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.65.229.0/24No ROA covers it. Add a ROA for AS7482, maxLength 24.671 of 673
Route object: RIR203.65.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.65.230.0/24No ROA covers it. Add a ROA for AS7482, maxLength 24.671 of 673
Route object: RIR203.65.230.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none202.178.180.0/24Route objects for it name AS17709. A route object for 202.178.160.0/19 with origin AS7482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7482 in the RIR database for the space.673 of 673
Route object: none202.178.182.0/24Route objects for it name AS17709. A route object for 202.178.160.0/19 with origin AS7482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7482 in the RIR database for the space.673 of 673
Route object: none210.200.67.0/24Route objects for it name AS17709. A route object for 210.200.64.0/19 with origin AS7482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7482 in the RIR database for the space.672 of 673
Route object: none60.244.129.0/24Route objects for it name AS17709, AS18049. A route object for 60.244.128.0/18 with origin AS7482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7482 in the RIR database for the space.637 of 673
Route object: RIR60.244.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR60.244.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR60.244.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR60.244.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.218.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.218.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.218.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.218.128.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.218.192.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.219.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.219.0.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.79.128.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.79.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.79.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.91.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.91.0.0/18Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR219.91.64.0/18Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR222.156.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.178.245.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.58.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.58.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.58.64.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.58.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.58.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.96.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.105.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.0.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.30.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.201.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.202.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.202.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.202.192.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.203.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.203.0.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.203.64.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.35.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.35.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.35.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.35.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.187.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.187.0.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.187.64.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.187.128.0/18Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR218.187.192.0/18Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR222.156.220.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.22.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.200.86.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.96.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.98.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.111.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.135.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.189.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.200.212.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR223.22.66.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2404:0:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS7482 whose prefix no peer sees AS7482 announce. Many are kept on purpose (backup routes, space announced only in some places).

60.244.0.0/17RADBValid
60.244.0.0/19RADBValid
60.244.0.0/24RADBValid
60.244.96.0/19RADBValid
60.244.128.0/17RADBValid
61.58.64.0/19RADBNo ROA
103.25.232.0/22RADBNo ROA
103.25.232.0/24RADBNo ROA
103.25.233.0/24RADBNo ROA
103.25.234.0/24RADBNo ROA
103.25.235.0/24RADBNo ROA
124.218.134.0/24RADBValid
124.218.136.0/24RADBValid
124.218.172.0/24RADBValid
124.218.173.0/24RADBValid
124.218.174.0/24RADBValid
124.218.175.0/24RADBValid
124.218.176.0/24RADBValid
124.218.177.0/24RADBValid
124.218.178.0/24RADBValid
124.218.179.0/24RADBValid
202.178.128.0/17RADBValid
202.178.128.0/18RADBValid
202.178.160.0/19RADBValid
202.178.192.0/18RADBValid
203.65.228.0/22RADBNo ROA
203.65.228.0/23RADBNo ROA
210.58.0.0/17RADBValid
210.58.128.0/17RADBValid
210.63.192.0/18RADBNo ROA
210.85.0.0/16NTTCOM, RADBValid
210.85.0.0/18RADBValid
210.85.64.0/18RADBValid
210.85.128.0/18RADBValid
210.85.192.0/18RADBValid
210.200.0.0/17RADBValid
210.200.0.0/18RADBValid
210.200.0.0/19RADBValid
210.200.32.0/19RADBValid
210.200.64.0/18RADBValid
210.200.128.0/17RADBValid
210.200.128.0/19RADBValid
210.200.133.0/24RADBValid
210.200.160.0/19RADBValid
210.200.181.0/24RADBValid
210.200.192.0/19RADBValid
210.200.224.0/19RADBValid
210.201.0.0/17RADBValid
210.201.31.0/24RADBValid
210.201.88.0/24RADBValid
210.201.128.0/17RADBValid
210.202.0.0/16NTTCOM, RADBNo ROA
210.202.0.0/17RADBNo ROA
210.202.0.0/18RADBNo ROA
210.202.224.0/20RADBValid
218.34.0.0/16NTTCOM, RADBValid
218.34.0.0/18RADBValid
218.34.64.0/18RADBValid
218.34.128.0/18RADBValid
218.34.192.0/18RADBValid
218.35.0.0/16RADBValid
218.35.16.0/21RADBValid
218.35.16.0/22RADBValid
218.35.16.0/23RADBValid
218.35.16.0/24RADBValid
218.35.17.0/24RADBValid
218.35.18.0/23RADBValid
218.35.18.0/24RADBValid
218.35.19.0/24RADBValid
218.35.20.0/22RADBValid
218.35.20.0/23RADBValid
218.35.20.0/24RADBValid
218.35.21.0/24RADBValid
218.35.22.0/23RADBValid
218.35.22.0/24RADBValid
218.35.23.0/24RADBValid
218.35.24.0/23RADBValid
218.35.24.0/24RADBValid
218.35.25.0/24RADBValid
218.35.162.0/24RADBValid
218.35.213.0/24RADBValid
218.184.0.0/16NTTCOM, RADBValid
218.184.0.0/18RADBValid
218.184.64.0/18RADBValid
218.184.128.0/18RADBValid
218.184.192.0/18RADBValid
218.187.0.0/17RADBValid
218.187.103.0/24RADBValid
218.187.114.0/24RADBValid
218.187.128.0/17RADBValid
218.187.224.0/19RADBValid
219.91.0.0/19RADBValid
219.91.32.0/19RADBValid
219.91.64.0/19RADBValid
219.91.96.0/19RADBValid
222.157.0.0/16NTTCOM, RADBValid
222.157.0.0/18NTTCOM, RADBValid
222.157.64.0/18NTTCOM, RADBValid
222.157.128.0/18NTTCOM, RADBValid
222.157.192.0/18NTTCOM, RADBValid

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.