LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

94.136.216.0/21

1 residential-proxy exit · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
5
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

18 observations

Proxy providers listing exits

  • EnigmaProxy
  • NovaProxy
  • ProxyEmpire
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.136.192.0/19
since Aug 2008
AS30881Residential1,028
2 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
94.136.192.0/198,192RU-MTU-20080723MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 23, 2008abuse@mtu.ru
└ 94.136.216.0/221,024TENSORTELECOM-VPDN-NETVPDN ClientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20080723
└ 94.136.220.0/23512TENSORTELECOM-VPDN-NETVPDN ClientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20080723
└ 94.136.222.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20080723
└ 94.136.223.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP 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

AnnouncementRouting historyWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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