Network · data from 2026-11-12
AS17685 SQUARE ENIX CO., LTD.
Registry name: PLAYONLINE - SQUARE ENIX CO., LTD., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17685, 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.195.53.0/24 | Valid | Nonecovered by 61.195.48.0/20 | 672 100% |
| 61.195.55.0/24 | Valid | Nonecovered by 61.195.48.0/20 | 672 100% |
| 61.195.56.0/24 | Valid | Nonecovered by 61.195.48.0/20 | 672 100% |
| 61.195.48.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB, REACH | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS17685: AS-PLAYONLINE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS17685 isn't in the set, or no route object for AS17685 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS17685 in it | Not covered |
|---|---|---|---|---|---|
| AS-PLAYONLINE | RADB | 28 | 2 | Yes | 0 |
| JPIRR (also) | 2 | 1 | Yes | 0 | |
| NTTCOM (also) | 2 | 1 | Yes | 0 |
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 5 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 61.195.53.0/24 | No route object for it. A route object for 61.195.48.0/20 with origin AS17685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17685 in the RIR database for the space. |
| Route object: none | 61.195.55.0/24 | No route object for it. A route object for 61.195.48.0/20 with origin AS17685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17685 in the RIR database for the space. |
| Route object: none | 61.195.56.0/24 | No route object for it. A route object for 61.195.48.0/20 with origin AS17685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17685 in the RIR database for the space. |
| Route object: RIR | 61.195.48.0/20 | Route object only in JPIRR, NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17685 whose prefix no peer sees AS17685 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 219.117.144.0/20 | REACH | 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.