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

37.204.166.0/24

14 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
2
14% of its exits
Providers
44
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • Proxying
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.204.0.0/1665,536RU-RTK-20120327PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 27, 2012abuse@rt.ru
└ 37.204.128.0/1816,384NCN-BBCUSTNCNET Broadband customersASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20120327

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

Who has announced 37.204.0.0/16

37.204.0.0/16

Routing history

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