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

77.239.210.0/24

6 residential-proxy exits · 30 days

MTS PJSC

Announcement
77.239.208.0/20
No RPKI
Announced by
AS8359
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
2
33% of its exits
Providers
31
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

685 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • GloryCloud
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxio
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • ResiProxies
  • VantageProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.239.192.0/19
since Nov 2024
AS8359Mobile246
13 always on
MTS PJSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.239.192.0/198,192RU-MTU-20070312MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 12, 2007abuse@mtu.ru
└ 77.239.208.0/204,096MTS-TUMEN-NETPJSC MTS Tyumen Region branchASSIGNED PAJun 7, 2023abuse@mtu.ru
via RU-MTU-20070312

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 historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

77.239.208.0/20

Routing history

Pattern
Reactivated
First seen
Jan 2010
Current origin since
Jun 2023 · 3.4 yr
Origin networks
2
Last change of origin
Jun 2023
Recorded history

History

Handoffs
1