Network · data from 2026-11-12
AS4774 ABONE-AS - A-Bone by Internet Initiative Japan Inc.
Registry name: ABONE-AS - A-Bone by Internet Initiative Japan Inc., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4774, 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.
| 202.6.252.0/22 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.6.254.0/24 | Valid | RIR databaseAPNIC, JPIRR, RADB | 672 100% |
| 202.6.255.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.6.253.0/24 | Valid | RIR databaseAPNIC, JPIRR, RADB | 671 100% |
AS-SET
AS4774 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 8 are in fix.csv.
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.6.252.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4774 whose prefix no peer sees AS4774 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.2.58.0/24 | JPIRR, RADB | Valid |
| 202.6.252.0/23 | APNIC | Valid |
| 202.6.252.0/24 | APNIC | Valid |
| 202.6.254.0/23 | APNIC | Valid |
| 2001:300:fff5::/48 | JPIRR, RADB | Valid |
| 2001:300:fff6::/48 | JPIRR, RADB | Valid |
| 2001:300:fff7::/48 | 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.