bgpreport

Network · data from 2026-11-12

AS30120 SGNE-AS - Sempra Global

Registry name: SGNE-AS - Sempra Global, US · not in PeeringDB

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

Announced routes

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

206.130.144.0/24 No ROA Nonecovered by 206.130.144.0/23 673 100% 70
206.130.145.0/24 No ROA Nonecovered by 206.130.144.0/23 673 100% 70
206.130.146.0/24 No ROA Nonecovered by 206.130.146.0/23 673 100% 70
206.130.144.0/23 No ROA Other IRR onlyRADB 673 100% 67
206.130.146.0/23 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS30120 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 18 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none206.130.144.0/24No ROA covers it. Add a ROA for AS30120, maxLength 24.673 of 673
Route object: none206.130.144.0/24No route object for it. A route object for 206.130.144.0/23 with origin AS30120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30120 in the RIR database for the space.673 of 673
ROA: none206.130.145.0/24No ROA covers it. Add a ROA for AS30120, maxLength 24.673 of 673
Route object: none206.130.145.0/24No route object for it. A route object for 206.130.144.0/23 with origin AS30120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30120 in the RIR database for the space.673 of 673
ROA: none206.130.146.0/24No ROA covers it. Add a ROA for AS30120, maxLength 24.673 of 673
Route object: none206.130.146.0/24No route object for it. A route object for 206.130.146.0/23 with origin AS30120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30120 in the RIR database for the space.673 of 673
ROA: none206.130.144.0/23No ROA covers it. Add a ROA for AS30120, maxLength 23.673 of 673
Route object: RIR206.130.144.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.130.146.0/23No ROA covers it. Add a ROA for AS30120, maxLength 23.673 of 673
Route object: RIR206.130.146.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

63.160.85.0/24RADBNo ROA
63.167.43.0/24RADBNo ROA
67.130.146.0/24RADBNo ROA
204.153.172.0/22RADBNo ROA
204.153.172.0/23RADBNo ROA
206.130.144.0/22RADBNo ROA
216.103.246.0/24RADBNo ROA
2620:a9::/48RADBNo 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.