bgpreport

Network · data from 2026-11-12

AS38636 DENA-NET - DeNA, Co. Ltd.

Registry name: DENA-NET - DeNA, Co. Ltd., JP · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS38636, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38636, 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:bd00:dc03::/48 No ROA Other IRR onlyJPIRR 636 100% 68
2401:bd00:b001::/48 No ROA Other IRR onlyJPIRR 635 100% 70
2401:bd00:b002::/48 No ROA Other IRR onlyJPIRR 635 100% 70
27.131.11.0/24 Valid Other IRR onlyJPIRR 673 100% 67
103.23.7.0/24 Valid Other IRR onlyJPIRR 672 100% 67

AS-SET

AS38636 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 17 are in fix.csv.

  • ROA: none3
  • Route object: RIR5
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none2401:bd00:dc03::/48No ROA covers it. Add a ROA for AS38636, maxLength 48.636 of 636
Route object: RIR2401:bd00:dc03::/48Route object only in JPIRR. Add it in the RIR database for the space.636 of 636
ROA: none2401:bd00:b001::/48No ROA covers it. Add a ROA for AS38636, maxLength 48.635 of 636
Route object: RIR2401:bd00:b001::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
ROA: none2401:bd00:b002::/48No ROA covers it. Add a ROA for AS38636, maxLength 48.635 of 636
Route object: RIR2401:bd00:b002::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR27.131.11.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR103.23.7.0/24Route object only in JPIRR. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

27.131.8.0/22JPIRRNo ROA
27.131.8.0/24JPIRR, RADBValid
103.23.4.0/22JPIRRNo ROA
202.166.185.0/24JPIRRNo ROA
2401:bd00::/32JPIRRNo ROA
2401:bd00:b003::/48JPIRRNo ROA
2401:bd00:dc01::/48JPIRRNo ROA
2401:bd00:dc02::/48JPIRRNo ROA
2401:bd00:dc04::/48JPIRRNo 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.