bgpreport

Network · data from 2026-11-12

AS35326 SUVAN-NET "SUVAN NET" LLC

Registry name: SUVAN-NET "SUVAN NET" LLC, UZ · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS35326, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35326, 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.
37.153.159.0/24 No ROA RIR databaseRIPE 673 100% 68
85.204.79.0/24 No ROA RIR databaseRIPE 673 100% 68
89.39.94.0/23 No ROA RIR databaseRIPE 673 100% 68
185.196.212.0/22 No ROA RIR databaseRIPE 673 100% 68
2a14:4a00::/29 No ROA RIR databaseRIPE 634 100% 70

AS-SET

AS35326 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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none37.153.159.0/24No ROA covers it. Add a ROA for AS35326, maxLength 24.673 of 673
ROA: none85.204.79.0/24No ROA covers it. Add a ROA for AS35326, maxLength 24.673 of 673
ROA: none89.39.94.0/23No ROA covers it. Add a ROA for AS35326, maxLength 23.673 of 673
ROA: none185.196.212.0/22No ROA covers it. Add a ROA for AS35326, maxLength 22.673 of 673
ROA: none2a14:4a00::/29No ROA covers it. Add a ROA for AS35326, maxLength 29.634 of 636

Route objects not announced

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