Home ASN LookupAS16094

AS16094 MagTelecom-AS Magistralny Telecom LLC

🇷🇺

Org handle: ORG-MTL50-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

4 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)1,024

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2000-12-18

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
185.26.204.0/24	No ROA	RIPE	2026-10-11
185.26.205.0/24	No ROA	RIPE	2026-10-11
217.22.174.0/24	No ROA	RIPE	2026-10-11
217.22.175.0/24	No ROA	RIPE	2026-10-11

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
185.26.204.0/24	🇷🇺 RU	RIPE	assigned
185.26.205.0/24	🇷🇺 RU	RIPE	assigned
217.22.174.0/24	🇷🇺 RU	RIPE	assigned
217.22.175.0/24	🇷🇺 RU	RIPE	assigned

All 4 announced prefixes of AS16094 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS12389ROSTELECOM PJSC Rostelecom4

Downstreams (1)

Networks whose own prefixes AS16094 passes on: usually its customers.

AS201578MAG TELECOM Magistralny Telecom1

Transfer History

Registry transfers of AS16094 between organisations.

AS16094Transfer · 2018-01-30
ROILCOM LTD
RIPE NCC
→
Magistralny Telecom LLC
RIPE NCC

Date	Resource	From	To	Type
2018-01-30	AS16094	ROILCOM LTD RIPE NCC	Magistralny Telecom LLC RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

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 AS16094 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

Open

GEThttps://api.ipctl.io/v1/asn/16094

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

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