bgpreport

Network · data from 2026-11-12

AS152324 M3XNETCOLTD-AS-AP - 3XNET Co., Ltd.

Registry name: M3XNETCOLTD-AS-AP - 3XNET Co., Ltd., JP · not in PeeringDB

9IPv4 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
2Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS152324, seen from no peer

Announced routes

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

165.49.248.0/24 Valid Other IRR onlyRADB 673 100% 67
14.137.248.0/24 Valid Other IRR onlyRADB 669 99% 67
14.137.249.0/24 Valid Other IRR onlyRADB 669 99% 67
163.223.216.0/23 Valid RIR databaseAPNIC 673 100% 67
95.169.170.0/24 Valid RIR databaseRIPE 672 100% 66
169.40.138.0/23 Valid RIR databaseRIPE 672 100% 66
95.169.172.0/24 Valid RIR databaseRIPE 671 100% 66
163.223.216.0/24 Valid RIR databaseAPNIC 9 1%low visibility 5
163.223.217.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

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

  • Route object: RIR3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: RIR165.49.248.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR14.137.248.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR14.137.249.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

82.47.24.0/23RADB, RIPEValid
82.153.47.0/24RADB, RIPEValid
82.153.48.0/24RADB, RIPEValid
147.90.30.0/24RADB, RIPEValid
162.4.52.0/23APNICValid
162.4.52.0/24APNICValid
162.4.53.0/24APNICValid
212.134.168.0/23RADBValid
217.216.254.0/24RADB, RIPEValid
217.216.255.0/24RADB, RIPEValid

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.