AS5572 BOTIK Botik Technologies LTD

🇷🇺

Org handle: ORG-BTL9-RIPE

Public network of Pereslavl-Zalessky

RIPE NCCallocated

Announced Prefixes (BGP)

6total

5 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)3,600

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2009-08-27

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
45.81.164.0/22	No ROA	RIPE	2026-10-11
95.129.136.0/22	No ROA	RIPE	2026-10-11
95.129.140.0/24	No ROA	RIPE	2026-10-11
95.129.141.0/24	No ROA	RIPE	2026-10-11
95.129.142.0/23	No ROA	RIPE	2026-10-11
2a01:67e0::/32	No ROA	RIPE	2026-10-11

(RIR)6

Prefix	Country	RIR	Status
45.81.164.0/22	🇷🇺 RU	RIPENCC	allocated
95.129.136.0/21	🇷🇺 RU	RIPENCC	allocated
95.129.138.176/28	🇷🇺 RU	RIPE	assigned
95.129.140.0/24	🇷🇺 RU	RIPE	assigned
95.129.141.0/24	🇷🇺 RU	RIPE	assigned
2a01:67e0::/32	🇷🇺 RU	RIPENCC	allocated

(seen in AS paths)

Networks AS5572 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 AS5572 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/5572" | jq