Data as of Nov 15, 2026

5.227.102.0/24

1 residential-proxy exit · 30 days

MTS PJSC

Announcement

this exact prefix

No RPKI

Announced by

AS44895

Type

Residential

Risk

0 / 100 · Low

Recent change

New origin Aug 2026

its first announcement on record

registry: sub-allocated pa to Mobile TeleSystems Ryazan branch by MTS PJSC, Aug 31, 2026

Residential-proxy exits

Proxy exits

0.39% of its addresses · 30 days

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

BirdProxies
BottingTools
ByteProxies
Byteful
CliProxy
Decodo
EnigmaProxy
Evomi
FloppyData
Geonode
Infatica
InfiniteProxies
MangoProxy
NovaProxy
Oxylabs
Proxiware
ProxyEmpire
Proxyma
Shifter
VitalExclusive

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
5.227.96.0/20 since Jul 2026	AS8359	Mobile	266 5 always on	MTS PJSC
5.227.0.0/17 since Jan 2024	AS8359	Mobile	6,706 879 always on	MTS PJSC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
5.227.0.0/16	65,536	RU-MTU-20120907	MTS PJSC (ORG-ZM1-RIPE) · RU	ALLOCATED PA	Sep 7, 2012	abuse@mtu.ru
└ 5.227.102.0/24	256	MTS-NET-FBN	Mobile TeleSystems Ryazan branch	SUB-ALLOCATED PA	Aug 31, 2026	abuse@mtu.ru via RU-MTU-20120907

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Announcement Routing history RPKI & IRR Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern: Stable
First seen: Aug 2026
Current origin since: Aug 2026 · 3 mo
Origin networks: 1