bgpreport

Network · data from 2026-11-12

AS23784 POLEXCHENGE - SQUARE ENIX CO., LTD.

Registry name: POLEXCHENGE - SQUARE ENIX CO., LTD., JP · not in PeeringDB

9IPv4 routes 100.0% RPKI valid · 44.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 5 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS23784, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23784, 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.
219.117.144.0/24 Valid Nonecovered by 219.117.144.0/20 672 100% 67
219.117.145.0/24 Valid Nonecovered by 219.117.144.0/20 672 100% 67
219.117.146.0/24 Valid Nonecovered by 219.117.144.0/20 672 100% 67
219.117.147.0/24 Valid Nonecovered by 219.117.144.0/20 672 100% 67
124.150.157.0/24 Valid Nonecovered by 124.150.152.0/21 2 0%low visibility 2
119.252.32.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
124.150.152.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
202.67.48.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
219.117.144.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67

AS-SET

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

  • Route object: none5
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none219.117.144.0/24No route object for it. A route object for 219.117.144.0/20 with origin AS23784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23784 in the RIR database for the space.672 of 673
Route object: none219.117.145.0/24No route object for it. A route object for 219.117.144.0/20 with origin AS23784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23784 in the RIR database for the space.672 of 673
Route object: none219.117.146.0/24No route object for it. A route object for 219.117.144.0/20 with origin AS23784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23784 in the RIR database for the space.672 of 673
Route object: none219.117.147.0/24No route object for it. A route object for 219.117.144.0/20 with origin AS23784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23784 in the RIR database for the space.672 of 673
Route object: none124.150.157.0/24No route object for it. A route object for 124.150.152.0/21 with origin AS23784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23784 in the RIR database for the space.2 of 673
Route object: RIR119.252.32.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.150.152.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.67.48.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.117.144.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS23784 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.