AS50126 TELESERVISE-AS OOO "Teleservis"

🇷🇺

Org handle: ORG-TO22-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

9total

9 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2009-11-20

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
77.232.144.0/24	Valid	RIPE	2026-10-10
77.232.145.0/24	Valid	RIPE	2026-10-10
77.232.146.0/24	Valid	RIPE	2026-10-10
77.232.147.0/24	Valid	RIPE	2026-10-10
77.232.148.0/22	Valid	RIPE	2026-10-10
77.232.152.0/24	Valid	RIPE	2026-10-10
77.232.153.0/24	Valid	RIPE	2026-10-10
77.232.154.0/24	Valid	RIPE	2026-10-10
77.232.155.0/24	Valid	RIPE	2026-10-10

(RIR)1

Prefix	Country	RIR	Status
77.232.148.0/22	🇷🇺 RU	RIPE	assigned

(seen in AS paths)

Networks AS50126 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 AS50126 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/50126" | jq