Network · data from 2026-11-12

AS10132 EASTAR-TECHNOLOGY-AP - Towngas Telecommunications Fixed Network Limited

Registry name: EASTAR-TECHNOLOGY-AP - Towngas Telecommunications Fixed Network Limited, HK · not in PeeringDB

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

0IPv6 routes

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

6Route objects not announced registered with origin AS10132, seen from no peer

Announced routes

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


61.4.0.0/18	Valid	Other IRR onlyNTTCOM, RADB	671 100%	67
113.212.192.0/18	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	67
113.212.216.0/21	Valid	RIR databaseAPNIC, RADB	671 100%	67
113.212.232.0/21	Valid	RIR databaseAPNIC, RADB	671 100%	67
61.4.10.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.11.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.12.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.13.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.14.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.15.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.16.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.23.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.26.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.27.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.28.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.29.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.30.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.31.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.32.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.36.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.37.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.42.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.44.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.48.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.52.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
61.4.56.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
113.212.196.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.198.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.200.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.202.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.208.0/22	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.212.0/22	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.216.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.217.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.219.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.220.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.222.0/23	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.224.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.225.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.229.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.230.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.231.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.232.0/22	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.232.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.233.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.234.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.235.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	199 30%	56
113.212.236.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.237.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56
113.212.240.0/24	Valid	RIR databaseAPNIC, RADB	199 30%	56

AS-SET

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

Route object: RIR1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	61.4.0.0/18	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

61.4.0.0/18

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

671 of 673

Route objects not announced

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


61.4.9.0/24	APNIC, NTTCOM, RADB	Valid
61.4.24.0/24	APNIC, NTTCOM, RADB	Valid
61.4.25.0/24	APNIC, NTTCOM, RADB	Valid
61.4.39.0/24	APNIC, NTTCOM, RADB	Valid
61.4.40.0/24	APNIC, NTTCOM, RADB	Valid
61.4.58.0/23	APNIC, NTTCOM, RADB	Valid

61.4.9.0/24

APNIC, NTTCOM, RADB

Valid

61.4.24.0/24

APNIC, NTTCOM, RADB

Valid

61.4.25.0/24

APNIC, NTTCOM, RADB

Valid

61.4.39.0/24

APNIC, NTTCOM, RADB

Valid

61.4.40.0/24

APNIC, NTTCOM, RADB

Valid

61.4.58.0/23

APNIC, NTTCOM, RADB

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.