AS35326 SUVAN-NET "SUVAN NET" LLC

🇺🇿

Org handle: ORG-NL314-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

5total

4 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)2,048

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)6.3×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2019-03-13

Announced Prefixes

(BGP)5

Prefix	RPKI	IRR	Last Seen
37.153.159.0/24	No ROA	RIPE	2026-10-10
85.204.79.0/24	No ROA	RIPE	2026-10-10
89.39.94.0/23	No ROA	RIPE	2026-10-10
185.196.212.0/22	No ROA	RIPE	2026-10-10
2a14:4a00::/29	No ROA	RIPE	2026-10-10

(RIR)5

Prefix	Country	RIR	Status
37.153.159.0/24	🇺🇿 UZ	RIPENCC	allocated
85.204.79.0/24	🇺🇿 UZ	RIPENCC	allocated
89.39.94.0/23	🇺🇿 UZ	RIPENCC	allocated
185.196.212.0/22	🇺🇿 UZ	RIPENCC	allocated
2a14:4a00::/29	🇺🇿 UZ	RIPENCC	allocated

(seen in AS paths)

Networks AS35326 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS35326 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/35326" | jq