Data as of Nov 10, 2026

78.37.2.0/24

16 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
16
6.3% of its addresses · 30 days
Always-on exits
1
6.3% of its exits
Providers
32
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

661 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
78.36.0.0/15
since Dec 2018
AS12389Residential11,773
655 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
78.36.0.0/15131,072RU-RTK-20070316PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 16, 2007abuse@rt.ru
└ 78.37.0.0/198,192RU-AVANGARD-DSLOJSC "North-West Telecom"SUB-ALLOCATED PASep 19, 2025abuse@rt.ru
via RU-RTK-20070316

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

78.37.0.0/19

Routing history

Pattern
Stable
First seen
Feb 2008
Current origin since
Dec 2017 · 8.9 yr
Origin networks
2
Last change of origin
Dec 2017
Recorded history

History

Handoffs
1