Network · data from 2026-11-12

AS135951 WEBICO-AS-VN - Webico Company Limited

Registry name: WEBICO-AS-VN - Webico Company Limited, VN · not in PeeringDB

27IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 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

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

25Route objects not announced registered with origin AS135951, seen from no peer

Announced routes

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


101.101.96.0/23	Valid	RIR databaseAPNIC	672 100%	67
101.101.96.0/24	Valid	RIR databaseAPNIC	672 100%	67
101.101.97.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.130.216.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.130.218.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.24.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.24.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.25.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.26.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.26.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.142.27.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.155.162.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.161.178.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.162.14.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.162.21.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.162.22.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.177.110.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.179.184.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
116.118.44.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
116.118.45.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
116.118.46.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
116.118.47.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
180.93.136.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
180.93.136.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
180.93.137.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
180.93.138.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
180.93.139.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
2401:45e0::/48	Valid	RIR databaseAPNIC	636 100%	69
2405:2840::/48	Valid	RIR databaseAPNIC, NTTCOM	634 100%	69

AS-SET

AS135951 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 25 are in fix.csv.

Route object: not announced25

Route objects not announced

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


103.130.216.0/22	APNIC, NTTCOM	Valid
103.155.162.0/24	APNIC, NTTCOM, RADB	Valid
103.155.163.0/24	APNIC, NTTCOM, RADB	Valid
103.161.172.0/23	NTTCOM, RADB	No ROA
103.162.14.0/24	APNIC, NTTCOM, RADB	Valid
103.162.15.0/24	APNIC, NTTCOM, RADB	Valid
103.162.20.0/23	APNIC, NTTCOM, RADB	Valid
103.162.20.0/24	APNIC, NTTCOM, RADB	Valid
103.164.154.0/23	NTTCOM, RADB	No ROA
103.164.154.0/24	NTTCOM, RADB	No ROA
103.164.155.0/24	NTTCOM, RADB	No ROA
103.166.176.0/23	APNIC	Invalid: origin
103.167.86.0/23	APNIC	Invalid: origin
103.177.110.0/24	APNIC, NTTCOM, RADB	Valid
103.177.111.0/24	APNIC, NTTCOM, RADB	Valid
103.179.184.0/24	APNIC, NTTCOM, RADB	Valid
103.179.185.0/24	APNIC, NTTCOM, RADB	Valid
116.118.44.0/22	APNIC, NTTCOM, RADB	Valid
116.118.44.0/23	APNIC, RADB	Valid
116.118.46.0/23	APNIC, RADB	Valid
180.93.136.0/23	APNIC, NTTCOM, RADB	Valid
180.93.138.0/23	APNIC, NTTCOM, RADB	Valid
2400:4de0::/48	APNIC, NTTCOM	Valid
2403:bfc0::/48	APNIC	No ROA
2405:28c0::/48	APNIC	Invalid: origin

103.130.216.0/22

APNIC, NTTCOM

Valid

103.155.162.0/24

APNIC, NTTCOM, RADB

Valid

103.155.163.0/24

APNIC, NTTCOM, RADB

Valid

103.161.172.0/23

NTTCOM, RADB

No ROA

103.162.14.0/24

APNIC, NTTCOM, RADB

Valid

103.162.15.0/24

APNIC, NTTCOM, RADB

Valid

103.162.20.0/23

APNIC, NTTCOM, RADB

Valid

103.162.20.0/24

APNIC, NTTCOM, RADB

Valid

103.164.154.0/23

NTTCOM, RADB

No ROA

103.164.154.0/24

NTTCOM, RADB

No ROA

103.164.155.0/24

NTTCOM, RADB

No ROA

103.166.176.0/23

APNIC

Invalid: origin

103.167.86.0/23

APNIC

Invalid: origin

103.177.110.0/24

APNIC, NTTCOM, RADB

Valid

103.177.111.0/24

APNIC, NTTCOM, RADB

Valid

103.179.184.0/24

APNIC, NTTCOM, RADB

Valid

103.179.185.0/24

APNIC, NTTCOM, RADB

Valid

116.118.44.0/22

APNIC, NTTCOM, RADB

Valid

116.118.44.0/23

APNIC, RADB

Valid

116.118.46.0/23

APNIC, RADB

Valid

180.93.136.0/23

APNIC, NTTCOM, RADB

Valid

180.93.138.0/23

APNIC, NTTCOM, RADB

Valid

2400:4de0::/48

APNIC, NTTCOM

Valid

2403:bfc0::/48

APNIC

No ROA

2405:28c0::/48

APNIC

Invalid: origin

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.