Network · data from 2026-11-12
AS45679 TOMOCHA.NET
Registry name: TOMOCHA-NET - Tatsumi, Tomo, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45679, 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.
| 2401:af80:9015::/48 | No ROA | Other IRR onlyJPIRR, RADB | 631 99% |
| 103.167.46.0/24 | Valid | Other IRR onlyJPIRR, RADB | 668 99% |
| 2001:df6:a680::/48 | Valid | Other IRR onlyJPIRR, RADB | 633 100% |
| 202.10.110.0/23 | Valid | RIR databaseAPNIC, JPIRR | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS45679: JPIRR::AS-TOMOCHA. 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 (AS45679 isn't in the set, or no route object for AS45679 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 | AS45679 in it | Not covered |
|---|---|---|---|---|---|
| JPIRR::AS-TOMOCHA | JPIRR | 1 | 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 12 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2401:af80:9015::/48 | No ROA covers it. Add a ROA for AS45679, maxLength 48. |
| Route object: RIR | 2401:af80:9015::/48 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.167.46.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df6:a680::/48 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45679 whose prefix no peer sees AS45679 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.96.59.232/29 | JPIRR | No ROA |
| 103.167.46.0/25 | JPIRR | Valid |
| 103.167.46.0/26 | JPIRR | Valid |
| 103.167.46.64/26 | JPIRR | Valid |
| 103.167.46.128/25 | JPIRR | Valid |
| 103.167.46.192/26 | JPIRR | Valid |
| 202.10.110.0/24 | APNIC, JPIRR | Valid |
| 202.10.111.0/24 | APNIC, JPIRR | 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.