bgpreport

Network · data from 2026-11-12

AS59123 Kakaku.com

Registry name: KAKAKUCOM - Kakaku.com, Inc., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59123, 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.

103.70.240.0/22 No ROA Other IRR onlyJPIRR 673 100% 67
103.70.240.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
103.70.242.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
103.70.243.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
219.100.44.0/22 No ROA Other IRR onlyJPIRR 673 100% 67
219.100.47.0/24 No ROA Other IRR onlyJPIRR 673 100% 67
133.247.72.0/22 No ROA Other IRR onlyJPIRR 669 99% 67
133.247.72.0/24 No ROA Other IRR onlyJPIRR 669 99% 67
133.247.75.0/24 No ROA Other IRR onlyJPIRR 669 99% 67
2406:4580::/32 No ROA Other IRR onlyJPIRR 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS59123: AS-KAKAKUCOM. 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 (AS59123 isn't in the set, or no route object for AS59123 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.

NameDatabaseASNsSets Route objectsAS59123 in itNot covered
AS-KAKAKUCOM JPIRR 1119 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 29 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none103.70.240.0/22No ROA covers it. Add a ROA for AS59123, maxLength 22.673 of 673
Route object: RIR103.70.240.0/22Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none103.70.240.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.673 of 673
Route object: RIR103.70.240.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none103.70.242.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.673 of 673
Route object: RIR103.70.242.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none103.70.243.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.673 of 673
Route object: RIR103.70.243.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none219.100.44.0/22No ROA covers it. Add a ROA for AS59123, maxLength 22.673 of 673
Route object: RIR219.100.44.0/22Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none219.100.47.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.673 of 673
Route object: RIR219.100.47.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none133.247.72.0/22No ROA covers it. Add a ROA for AS59123, maxLength 22.669 of 673
Route object: RIR133.247.72.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none133.247.72.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.669 of 673
Route object: RIR133.247.72.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none133.247.75.0/24No ROA covers it. Add a ROA for AS59123, maxLength 24.669 of 673
Route object: RIR133.247.75.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none2406:4580::/32No ROA covers it. Add a ROA for AS59123, maxLength 32.635 of 636
Route object: RIR2406:4580::/32Route object only in JPIRR. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS59123 whose prefix no peer sees AS59123 announce. Many are kept on purpose (backup routes, space announced only in some places).

61.245.108.0/23JPIRRNo ROA
61.245.108.0/24JPIRRNo ROA
61.245.109.0/24JPIRRNo ROA
103.70.241.0/24JPIRRNo ROA
133.247.73.0/24JPIRRNo ROA
133.247.74.0/24JPIRRNo ROA
219.100.44.0/24JPIRRNo ROA
219.100.45.0/24JPIRRNo ROA
219.100.46.0/24JPIRRNo ROA

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.