bgpreport

Network · data from 2026-11-12

AS9619 SSD - Sony Global Solutions Inc.

Registry name: SSD - Sony Global Solutions Inc., JP · not in PeeringDB

9IPv4 routes 44.4% RPKI valid · 66.7% with a route object
4IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS9619, seen from no peer

Announced routes

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

211.125.143.0/24 No ROA Nonecovered by 211.125.128.0/20 672 100% 66
2001:cf8:acc::/48 No ROA Nonecovered by 2001:cf8::/32 636 100% 68
133.138.0.0/16 No ROA Other IRR onlyRADB 672 100% 66
137.153.0.0/16 No ROA Other IRR onlyRADB 672 100% 66
146.215.0.0/16 No ROA Other IRR onlyRADB 672 100% 66
211.125.128.0/20 No ROA Other IRR onlyRADB 672 100% 66
2001:cf8::/32 No ROA Other IRR onlyRADB 635 100% 70
211.125.139.0/24 Valid Nonecovered by 211.125.128.0/20 673 100% 67
211.125.130.0/24 Valid Nonecovered by 211.125.128.0/20 672 100% 66
2001:cf8:acf::/48 Valid Nonecovered by 2001:cf8::/32 635 100% 67
211.125.140.0/24 Valid Other IRR onlyRADB 672 100% 66
211.125.142.0/24 Valid Other IRR onlyRADB 672 100% 66
2001:cf8:ace::/48 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS9619 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 29 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR8
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none211.125.143.0/24No ROA covers it. Add a ROA for AS9619, maxLength 24.672 of 673
Route object: none211.125.143.0/24No route object for it. A route object for 211.125.128.0/20 with origin AS9619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9619 in the RIR database for the space.672 of 673
ROA: none2001:cf8:acc::/48No ROA covers it. Add a ROA for AS9619, maxLength 48.636 of 636
Route object: none2001:cf8:acc::/48No route object for it. A route object for 2001:cf8::/32 with origin AS9619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9619 in the RIR database for the space.636 of 636
ROA: none133.138.0.0/16No ROA covers it. Add a ROA for AS9619, maxLength 16.672 of 673
Route object: RIR133.138.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none137.153.0.0/16No ROA covers it. Add a ROA for AS9619, maxLength 16.672 of 673
Route object: RIR137.153.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none146.215.0.0/16No ROA covers it. Add a ROA for AS9619, maxLength 16.672 of 673
Route object: RIR146.215.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.125.128.0/20No ROA covers it. Add a ROA for AS9619, maxLength 20.672 of 673
Route object: RIR211.125.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2001:cf8::/32No ROA covers it. Add a ROA for AS9619, maxLength 32.635 of 636
Route object: RIR2001:cf8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none211.125.139.0/24No route object for it. A route object for 211.125.128.0/20 with origin AS9619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9619 in the RIR database for the space.673 of 673
Route object: none211.125.130.0/24No route object for it. A route object for 211.125.128.0/20 with origin AS9619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9619 in the RIR database for the space.672 of 673
Route object: none2001:cf8:acf::/48No route object for it. A route object for 2001:cf8::/32 with origin AS9619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9619 in the RIR database for the space.635 of 636
Route object: RIR211.125.140.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.125.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:cf8:ace::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

146.215.8.0/22RADBNo ROA
146.215.48.0/20RADBNo ROA
157.68.0.0/16RADBNo ROA
211.125.141.0/24RADBValid
2001:cf8:0:f::1/128NTTCOMNo ROA
2001:cf8:0:f::2/128NTTCOMNo ROA
2001:cf8:0:f::3/128NTTCOMNo ROA
2001:cf8:0:f::4/128NTTCOMNo ROA
2001:cf8:5::/48RADBValid

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.