Network · data from 2026-11-12

AS138627 Cato Networks AS138627

Registry name: CATONETWORKSINC-AS-AP - Cato Networks, Inc., HK · PeeringDB

5IPv4 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

0Route objects not announced registered with origin AS138627, seen from no peer

Announced routes

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


113.30.129.0/24	Valid	RIR databaseAPNIC	672 100%	67
140.82.197.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
150.195.215.0/24	Valid	RIR databaseAPNIC	672 100%	67
150.195.216.0/24	Valid	RIR databaseAPNIC	672 100%	67
202.75.245.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67

AS-SET

AS138627's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS138627 is announced.

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.