Data as of Nov 10, 2026

92.100.77.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
Providers
31
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

416 observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BuyingProxy
  • ByteProxies
  • Byteful
  • EZProxies
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.100.0.0/16
since Oct 2018
AS12389Residential7,763
319 always on
PJSC Rostelecom
92.100.0.0/15
since Oct 2018
AS12389Residential15,951
716 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.100.0.0/15131,072RU-RTK-20080404PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 4, 2008abuse@rt.ru
└ 92.100.0.0/1732,768RU-AVANGARD-DSL"St.Petersburg Telephone Network"ASSIGNED PAApr 21, 2008abuse@rt.ru
via RU-RTK-20080404

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

92.100.76.0/22

Routing history

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