bgpreport

Network · data from 2026-11-12

AS142438 Toyama Kasumi

Registry name: KSMNW-AS-AP - Kasumi Networks Inc, CN · PeeringDB

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

Announced routes

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

2a05:1087::/32 No ROA RIR databaseRADB, RIPE 634 100% 68
2406:840:8100::/40 Valid Nonecovered by 2406:840:8000::/36 2 0%low visibility 2
2406:840:fef8::/48 Valid RIR databaseAPNIC 634 100% 69
2a0e:b107:da0::/44 Valid RIR databaseRIPE 634 100% 68
2a0e:b107:14a0::/44 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS142438's PeeringDB record names no 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a05:1087::/32No ROA covers it. Add a ROA for AS142438, maxLength 32.634 of 636
Route object: none2406:840:8100::/40No route object for it. A route object for 2406:840:8000::/36 with origin AS142438 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142438 in the RIR database for the space.2 of 636

Route objects not announced

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

2406:840:8000::/36APNIC, RADBValid
2406:840:8200::/40APNICValid
2a0c:b641:130::/44RIPEValid

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.