bgpreport

Network · data from 2026-11-12

AS17416 DWINS Digital Service Corp

Registry name: DWINS-TW - DWINS Digital Service Corp.,, TW · PeeringDB

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

Announced routes

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

112.213.48.0/20 Valid Other IRR onlyRADB 673 100% 68
211.78.80.0/21 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
211.78.88.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
211.78.92.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
211.78.94.0/24 Valid Other IRR onlyNTTCOM 673 100% 68
211.78.95.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
2405:4d00::/32 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS17416's PeeringDB record names no 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 60 are in fix.csv.

  • Route object: RIR7
  • Route object: not announced53
ChangePrefix or setDetailFull-table peers
Route object: RIR112.213.48.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.78.80.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.78.88.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.78.92.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.78.94.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR211.78.95.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2405:4d00::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

61.56.96.0/20NTTCOM, RADBNo ROA
112.213.48.0/21RADBValid
112.213.48.0/22RADBValid
112.213.48.0/23RADBValid
112.213.48.0/24RADBValid
112.213.49.0/24RADBValid
112.213.50.0/23RADBValid
112.213.50.0/24RADBValid
112.213.51.0/24RADBValid
112.213.52.0/22RADBValid
112.213.52.0/23RADBValid
112.213.52.0/24RADBValid
112.213.53.0/24RADBValid
112.213.54.0/23RADBValid
112.213.54.0/24RADBValid
112.213.55.0/24RADBValid
112.213.56.0/21RADBValid
112.213.56.0/22RADBValid
112.213.56.0/23RADBValid
112.213.56.0/24RADBValid
112.213.57.0/24RADBValid
112.213.58.0/23RADBValid
112.213.58.0/24RADBValid
112.213.59.0/24RADBValid
112.213.60.0/22RADBValid
112.213.60.0/23RADBValid
112.213.60.0/24RADBValid
112.213.61.0/24RADBValid
112.213.62.0/23RADBValid
112.213.62.0/24RADBValid
112.213.63.0/24RADBValid
192.170.73.0/24NTTCOM, RADBNo ROA
211.78.80.0/23RADBValid
211.78.80.0/24RADBValid
211.78.81.0/24RADBValid
211.78.82.0/23RADBValid
211.78.82.0/24RADBValid
211.78.83.0/24RADBValid
211.78.84.0/22RADBValid
211.78.84.0/23RADBValid
211.78.84.0/24RADBValid
211.78.85.0/24RADBValid
211.78.86.0/23RADBValid
211.78.86.0/24RADBValid
211.78.87.0/24RADBValid
211.78.88.0/23RADBValid
211.78.88.0/24RADBValid
211.78.89.0/24RADBValid
211.78.90.0/23RADBValid
211.78.90.0/24RADBValid
211.78.91.0/24RADBValid
211.78.92.0/24RADBValid
211.78.93.0/24RADBValid

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.