bgpreport

Network · data from 2026-11-12

AS38258 SONY-APAC-AP - Sony - ASN for Asia Pacific

Registry name: SONY-APAC-AP - Sony - ASN for Asia Pacific, SG · not in PeeringDB

5IPv4 routes 0.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
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS38258, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38258, 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.240.128.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
121.100.32.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
121.100.40.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
146.215.8.0/22 No ROA Other IRR onlyNTTCOM 671 100% 67
2400:3c00::/32 No ROA Other IRR onlyNTTCOM 635 100% 68
2400:3c00::/48 No ROA Other IRR onlyNTTCOM 635 100% 68
103.240.131.0/24 No ROA RIR databaseAPNIC 671 100% 67
2400:3c00:1::/48 No ROA RIR databaseAPNIC 635 100% 68

AS-SET

AS38258 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 21 are in fix.csv.

  • ROA: none8
  • Route object: RIR6
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none103.240.128.0/22No ROA covers it. Add a ROA for AS38258, maxLength 22.673 of 673
Route object: RIR103.240.128.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.100.32.0/20No ROA covers it. Add a ROA for AS38258, maxLength 20.673 of 673
Route object: RIR121.100.32.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.100.40.0/21No ROA covers it. Add a ROA for AS38258, maxLength 21.673 of 673
Route object: RIR121.100.40.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none146.215.8.0/22No ROA covers it. Add a ROA for AS38258, maxLength 22.671 of 673
Route object: RIR146.215.8.0/22Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none2400:3c00::/32No ROA covers it. Add a ROA for AS38258, maxLength 32.635 of 636
Route object: RIR2400:3c00::/32Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636
ROA: none2400:3c00::/48No ROA covers it. Add a ROA for AS38258, maxLength 48.635 of 636
Route object: RIR2400:3c00::/48Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636
ROA: none103.240.131.0/24No ROA covers it. Add a ROA for AS38258, maxLength 24.671 of 673
ROA: none2400:3c00:1::/48No ROA covers it. Add a ROA for AS38258, maxLength 48.635 of 636

Route objects not announced

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

103.240.128.0/23NTTCOMNo ROA
121.100.32.0/21NTTCOMNo ROA
146.215.8.0/21RADBNo ROA
146.215.8.0/23NTTCOMNo ROA
146.215.10.0/23NTTCOMNo ROA
2400:3c00:1:a102::/64NTTCOMNo ROA
2400:3c00:2::/48APNICNo 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.