AS38951 TKT-AS PJSC Rostelecom

🇷🇺

Org handle: ORG-JR8-RIPE

OJSC "TKT"

RIPE NCCallocated

Announced Prefixes (BGP)

5total

5 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)16,384

Announced (BGP)16,384

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2005-11-17

Announced Prefixes

(BGP)5

Prefix	RPKI	IRR	Last Seen
46.252.160.0/20	Valid	RIPE	2026-10-11
77.241.32.0/20	Valid	RIPE	2026-10-11
87.237.112.0/21	Valid	RIPE	2026-10-11
93.185.176.0/20	Valid	RIPE	2026-10-11
109.205.248.0/21	Valid	RIPE	2026-10-11

(RIR)5

Prefix	Country	RIR	Status
46.252.160.0/20	🇷🇺 RU	RIPENCC	allocated
77.241.32.0/20	🇷🇺 RU	RIPENCC	allocated
87.237.112.0/21	🇷🇺 RU	RIPENCC	allocated
93.185.176.0/20	🇷🇺 RU	RIPENCC	allocated
109.205.248.0/21	🇷🇺 RU	RIPENCC	allocated

(seen in AS paths)

Networks AS38951 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 AS38951 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/38951" | jq