Home ASN LookupAS57181

AS57181 ASRTK OOO RTK

🇷🇺

Org handle: ORG-RTK1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

14total

14 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)6,144

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2011-08-12

Announced Prefixes

(BGP)14

Prefix	RPKI	IRR	Last Seen
31.133.200.0/21	No ROA	RIPE	2026-10-11
31.133.200.0/24	No ROA	-	2026-10-11
31.133.201.0/24	No ROA	-	2026-10-11
31.133.202.0/24	No ROA	-	2026-10-11
31.133.203.0/24	No ROA	-	2026-10-11
31.133.204.0/24	No ROA	-	2026-10-11
31.133.205.0/24	No ROA	-	2026-10-11
31.133.206.0/24	No ROA	-	2026-10-11
31.133.207.0/24	No ROA	-	2026-10-11
91.228.96.0/22	No ROA	RIPE	2026-10-11

1-10 of 14

1 / 2

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
31.133.200.0/21	🇷🇺 RU	RIPENCC	assigned
91.228.96.0/22	🇷🇺 RU	RIPENCC	assigned

All 14 announced prefixes of AS57181 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS3216SOVAM PJSC "Vimpelcom"14

Downstreams (2)

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

AS57803TELESERVIS20
AS13016TELELINE NET Teleline3

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 AS57181 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/57181

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

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