AS43594 SVYAZ-AS Svyaz LLC

🇷🇺

Org handle: ORG-SL630-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

11total

10 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)4,096

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2017-01-09

Announced Prefixes

(BGP)11

Prefix	RPKI	IRR	Last Seen
95.215.124.0/22	Valid	RIPE	2026-10-10
95.215.124.0/24	Valid	RIPE	2026-10-10
95.215.125.0/24	Valid	RIPE	2026-10-10
95.215.126.0/24	Valid	RIPE	2026-10-10
95.215.127.0/24	Valid	RIPE	2026-10-10
185.184.232.0/22	Valid	RIPE	2026-10-10
185.184.232.0/24	Valid	RIPE	2026-10-10
185.184.233.0/24	Valid	RIPE	2026-10-10
185.184.234.0/24	Valid	RIPE	2026-10-10
185.184.235.0/24	Valid	RIPE	2026-10-10

1-10 of 11

1 / 2

(RIR)3

Prefix	Country	RIR	Status
95.215.124.0/22	🇷🇺 RU	RIPENCC	allocated
185.184.232.0/22	🇷🇺 RU	RIPENCC	allocated
2a0b:4380::/29	🇷🇺 RU	RIPENCC	allocated

(seen in AS paths)

Networks AS43594 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 AS43594 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/43594" | jq