Network · data from 2026-11-12
AS37922 Diversity Media Co.,Ltd.
Registry name: CATVY - Diversitymedia Co.,Ltd., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37922, 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.
| 118.91.196.0/22 | Valid | Nonecovered by 118.91.192.0/21 | 183 27% |
| 118.91.192.0/19 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 103.239.108.0/22 | Valid | Other IRR onlyJPIRR, RADB | 669 99% |
| 2406:a3c0::/32 | Valid | Other IRR onlyJPIRR | 337 53% |
| 118.91.200.0/21 | Valid | Other IRR onlyJPIRR, RADB | 185 27% |
| 118.91.208.0/21 | Valid | Other IRR onlyJPIRR, RADB | 185 27% |
| 118.91.216.0/21 | Valid | Other IRR onlyJPIRR, RADB | 185 27% |
AS-SET
PeeringDB's irr_as_set for AS37922: AS37922. 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 (AS37922 isn't in the set, or no route object for AS37922 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 | AS37922 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS37922 | A single AS number, not a set: AS37922 (this network), 7 route objects. | |||||
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 8 are in fix.csv.
- Route object: none1
- Route object: RIR6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 118.91.196.0/22 | No route object for it. A route object for 118.91.192.0/21 with origin AS37922 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37922 in the RIR database for the space. |
| Route object: RIR | 118.91.192.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.239.108.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:a3c0::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 118.91.200.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.91.208.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.91.216.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37922 whose prefix no peer sees AS37922 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 118.91.192.0/21 | JPIRR, 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.