Network · data from 2026-11-12

AS394347 SG-ASN - Supreme Group LP

Registry name: SG-ASN - Supreme Group LP, CA · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

2No ROA 2 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS394347, seen from no peer

Announced routes

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


209.89.121.0/24	Invalid: origin	None	46 7%low visibility	29
207.189.143.0/24	No ROA	Other origin only	591 88%	67
66.85.91.0/24	No ROA	Other IRR onlyRADB	587 87%	67

209.89.121.0/24

Invalid: origin

None

46 7%low visibility

207.189.143.0/24

No ROA

Other origin only

591 88%

66.85.91.0/24

No ROA

Other IRR onlyRADB

587 87%

AS-SET

AS394347 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 6 are in fix.csv.

ROA: origin1
ROA: none2
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	209.89.121.0/24	ROAs covering it name AS852, not AS394347. If AS394347 should announce it, add a ROA for AS394347.	46 of 673
Route object: none	209.89.121.0/24	No route object for it. Add a route object with origin AS394347 in the RIR database for the space.	46 of 673
ROA: none	207.189.143.0/24	No ROA covers it. Add a ROA for AS394347, maxLength 24.	591 of 673
Route object: none	207.189.143.0/24	Route objects for it name AS6327, AS14107, AS399778. Add a route object with origin AS394347 in the RIR database for the space.	591 of 673
ROA: none	66.85.91.0/24	No ROA covers it. Add a ROA for AS394347, maxLength 24.	587 of 673
Route object: RIR	66.85.91.0/24	Route object only in RADB. Add it in the RIR database for the space.	587 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

209.89.121.0/24

ROAs covering it name AS852, not AS394347. If AS394347 should announce it, add a ROA for AS394347.

46 of 673

Route object: none

209.89.121.0/24

No route object for it. Add a route object with origin AS394347 in the RIR database for the space.

46 of 673

ROA: none

207.189.143.0/24

No ROA covers it. Add a ROA for AS394347, maxLength 24.

591 of 673

Route object: none

207.189.143.0/24

Route objects for it name AS6327, AS14107, AS399778. Add a route object with origin AS394347 in the RIR database for the space.

591 of 673

ROA: none

66.85.91.0/24

No ROA covers it. Add a ROA for AS394347, maxLength 24.

587 of 673

Route object: RIR

66.85.91.0/24

Route object only in RADB. Add it in the RIR database for the space.

587 of 673

Route objects not announced

Every route object with origin AS394347 is announced.

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.