Home ASN LookupAS60139

AS60139 Sever-Telecom Sever Telecom JSC

🇷🇺

Org handle: ORG-ZL27-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

6total

6 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)3,584

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2014-05-01

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
90.156.146.0/24	Valid	RIPE	2026-10-11
178.57.112.0/21	No ROA	RIPE	2026-10-11
178.57.114.0/24	No ROA	RIPE	2026-10-11
178.57.116.0/24	No ROA	RIPE	2026-10-11
185.141.232.0/23	No ROA	RIPE	2026-10-11
185.141.235.0/24	No ROA	RIPE	2026-10-11

Allocated Prefixes

(RIR)3

Prefix	Country	RIR	Status
90.156.146.0/24	🇷🇺 RU	RIPE	assigned
185.141.232.0/23	🇷🇺 RU	RIPE	assigned
185.141.235.0/24	🇷🇺 RU	RIPE	assigned

All 6 announced prefixes of AS60139 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS214173Sever Telecom SPb Sever Telecom JSC5
AS31133MF MGSM PJSC MegaFon2

Transfer History

Registry transfers of AS60139 between organisations.

AS60139M&A · 2019-05-06
Z-Telecom Ltd
RIPE NCC
→
Sever Telecom JSC
RIPE NCC

Date	Resource	From	To	Type
2019-05-06	AS60139	Z-Telecom Ltd RIPE NCC	Sever Telecom JSC RIPE NCC	M&A

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 AS60139 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/60139

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

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