Data as of Nov 15, 2026

37.110.148.0/24

12 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
44
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalData
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.110.0.0 - 37.110.159.25540,960RU-RTK-20120208PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 9, 2012abuse@rt.ru
└ 37.110.144.0/204,096NCN-BBCUSTNCNET Broadband customersASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20120208

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

Who has announced 37.110.128.0/19

37.110.128.0/19

Routing history

Pattern
Stable
First seen
Feb 2012
Current origin since
Feb 2012 · 15 yr
Origin networks
1