Network · data from 2026-11-12

AS63897 vocom-tw

Registry name: vocom-tw - vocom international telecom, TW · PeeringDB

12IPv4 routes 75.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS63897, seen from no peer

Announced routes

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


38.70.74.0/24	No ROA	Other IRR onlyRADB	672 100%	67
38.150.70.0/24	No ROA	Other IRR onlyRADB	672 100%	67
103.127.236.0/24	No ROA	Other IRR onlyRADB	671 100%	67
2400:4460::/32	Valid	None	636 100%	67
45.87.55.0/24	Valid	Other IRR onlyRADB	671 100%	67
103.127.239.0/24	Valid	Other IRR onlyRADB	671 100%	67
103.175.254.0/24	Valid	Other IRR onlyRADB	671 100%	67
157.20.199.0/24	Valid	Other IRR onlyRADB	671 100%	67
161.248.160.0/24	Valid	Other IRR onlyRADB	671 100%	67
161.248.161.0/24	Valid	Other IRR onlyRADB	671 100%	67
103.127.237.0/24	Valid	Other IRR onlyRADB	670 100%	67
103.178.36.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	67
103.178.37.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	67

AS-SET

AS63897'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 15 are in fix.csv.

ROA: none3
Route object: none1
Route object: RIR10
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.70.74.0/24	No ROA covers it. Add a ROA for AS63897, maxLength 24.	672 of 673
Route object: RIR	38.70.74.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	38.150.70.0/24	No ROA covers it. Add a ROA for AS63897, maxLength 24.	672 of 673
Route object: RIR	38.150.70.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	103.127.236.0/24	No ROA covers it. Add a ROA for AS63897, maxLength 24.	671 of 673
Route object: RIR	103.127.236.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: none	2400:4460::/32	No route object for it. Add a route object with origin AS63897 in the RIR database for the space.	636 of 636
Route object: RIR	45.87.55.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	103.127.239.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	103.175.254.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	157.20.199.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	161.248.160.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	161.248.161.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	103.127.237.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.70.74.0/24

No ROA covers it. Add a ROA for AS63897, maxLength 24.

672 of 673

Route object: RIR

38.70.74.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

38.150.70.0/24

No ROA covers it. Add a ROA for AS63897, maxLength 24.

672 of 673

Route object: RIR

38.150.70.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

103.127.236.0/24

No ROA covers it. Add a ROA for AS63897, maxLength 24.

671 of 673

Route object: RIR

103.127.236.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: none

2400:4460::/32

No route object for it. Add a route object with origin AS63897 in the RIR database for the space.

636 of 636

Route object: RIR

45.87.55.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

103.127.239.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

103.175.254.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

157.20.199.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

161.248.160.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

161.248.161.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

103.127.237.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route objects not announced

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


103.178.36.0/23	APNIC	Valid

103.178.36.0/23

APNIC

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.