AS16301 DATACOM-AS PJSC Rostelecom

🇷🇺

Org handle: ORG-JR8-RIPE

Novgorod Datacom LLC

RIPE NCCallocated

Announced Prefixes (BGP)

5total

5 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)57,344

Announced (BGP)90,112

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2001-02-21

Announced Prefixes

(BGP)5

Prefix	RPKI	IRR	Last Seen
78.81.0.0/17	Valid	RIPE	2026-10-11
78.81.192.0/18	Valid	RIPE	2026-10-11
84.242.192.0/18	Valid	RIPE	2026-10-11
89.252.64.0/18	Valid	RIPE	2026-10-11
213.148.160.0/19	Valid	RIPE	2026-10-11

(RIR)4

Prefix	Country	RIR	Status
78.81.192.0/18	🇷🇺 RU	RIPE	assigned
84.242.192.0/18	🇷🇺 RU	RIPENCC	allocated
89.252.64.0/18	🇷🇺 RU	RIPENCC	allocated
213.148.160.0/19	🇷🇺 RU	RIPENCC	allocated

(seen in AS paths)

Networks AS16301 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 AS16301 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/16301" | jq