Network · data from 2026-11-12

AS29746 S3PL-ASN - S3 Partners LLC

Registry name: S3PL-ASN - S3 Partners LLC, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


38.97.111.0/24	No ROA	Other IRR onlyRADB	671 100%	67
72.21.173.0/24	Valid	Other IRR onlyALTDB, RADB	670 100%	67

AS-SET

AS29746 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 3 are in fix.csv.

ROA: none1
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.97.111.0/24	No ROA covers it. Add a ROA for AS29746, maxLength 24.	671 of 673
Route object: RIR	38.97.111.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	72.21.173.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.97.111.0/24

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

671 of 673

Route object: RIR

38.97.111.0/24

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

671 of 673

Route object: RIR

72.21.173.0/24

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

670 of 673

Route objects not announced

Every route object with origin AS29746 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.