bgpreport

Network · data from 2026-11-12

AS63902 SHINETEL-AS-TW - SHINE TELECOM CO., LTD.

Registry name: SHINETEL-AS-TW - SHINE TELECOM CO., LTD., TW · not in PeeringDB

23IPv4 routes 91.3% RPKI valid · 78.3% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
1No ROA 5 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS63902, seen from no peer

Announced routes

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

65.181.180.0/22 Invalid: origin Other origin only 2 0%low visibility 2
141.11.142.0/23 No ROA None 2 0%low visibility 2
141.11.80.0/24 Valid Nonecovered by 141.11.80.0/23 673 100% 66
141.11.84.0/24 Valid Nonecovered by 141.11.84.0/23 673 100% 66
141.11.85.0/24 Valid Nonecovered by 141.11.84.0/23 673 100% 66
103.116.14.0/24 Valid Other IRR onlyRADB 673 100% 66
89.28.235.0/24 Valid Other IRR onlyRADB 672 100% 67
103.116.15.0/24 Valid Other IRR onlyRADB 672 100% 66
141.11.81.0/24 Valid Other IRR onlyRADB 672 100% 66
141.11.221.0/24 Valid Other IRR onlyRADB 671 100% 67
81.168.76.0/24 Valid Other IRR onlyRADB 670 100% 67
81.168.79.0/24 Valid Other IRR onlyRADB 670 100% 67
109.110.189.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
141.11.84.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
141.11.183.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
31.59.166.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
82.29.52.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
87.229.31.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
85.209.230.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
96.62.222.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
155.117.15.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
157.254.216.0/24 Valid RIR databaseARIN, RADB 671 100% 67
96.62.152.0/24 Valid RIR databaseRADB, RIPE 647 96% 67

AS-SET

AS63902 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 20 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none5
  • Route object: RIR7
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin65.181.180.0/22ROAs covering it name AS17404, not AS63902. If AS63902 should announce it, add a ROA for AS63902.2 of 673
Route object: none65.181.180.0/22Route objects for it name AS17404. Add a route object with origin AS63902 in the RIR database for the space.2 of 673
ROA: none141.11.142.0/23No ROA covers it. Add a ROA for AS63902, maxLength 23.2 of 673
Route object: none141.11.142.0/23No route object for it. Add a route object with origin AS63902 in the RIR database for the space.2 of 673
Route object: none141.11.80.0/24No route object for it. A route object for 141.11.80.0/23 with origin AS63902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63902 in the RIR database for the space.673 of 673
Route object: none141.11.84.0/24No route object for it. A route object for 141.11.84.0/23 with origin AS63902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63902 in the RIR database for the space.673 of 673
Route object: none141.11.85.0/24No route object for it. A route object for 141.11.84.0/23 with origin AS63902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63902 in the RIR database for the space.673 of 673
Route object: RIR103.116.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.28.235.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.116.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.11.81.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.11.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR81.168.76.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR81.168.79.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

68.166.206.0/24ARIN, RADBValid
103.205.87.0/24RADB, RIPEValid
141.11.80.0/23RADB, RIPEValid
141.11.220.0/23RADB, RIPEValid
149.127.234.0/24RADBNo ROA
149.127.235.0/24RADBNo ROA

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.