Data as of Nov 12, 2026

94.136.207.0/24

9 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
20
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

272 observations

Proxy providers listing exits

  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • FlashProxy
  • FlexyProxies
  • IPFly
  • NovaProxy
  • Oxylabs
  • Proxio
  • ProxyRack
  • PuraRoute
  • RapidProxy
  • StrikeProxy
  • ThunderProxy
  • VibeProxies
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.136.192.0/19
since Aug 2008
AS30881Residential1,026
2 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
94.136.192.0/198,192RU-MTU-20080723MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 23, 2008abuse@mtu.ru
└ 94.136.200.0/212,048TENSORTELECOM-VPDN-NETVPDN ClientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20080723

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

94.136.200.0/21

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1