Data as of Nov 17, 2026

81.20.205.0/24

5 residential-proxy exits · 30 days

OOO SET · space held by MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
3
60% of its exits
Providers
34
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

8.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.20.192.0/20
since Jul 2017
AS20866Unknown9
3 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.20.192.0/204,096RU-MTU-20020205MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 23, 2025abuse@mtu.ru
└ 81.20.205.0/24256NET-FOR-TOMSKunknownASSIGNED PAFeb 21, 2024abuse@mtu.ru
via RU-MTU-20020205

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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2024
Current origin since
Feb 2024 · 2.7 yr
Origin networks
1