Data as of Nov 16, 2026

92.100.126.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
32
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

650 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EZProxies
  • EnigmaProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.100.112.0/20
since Jan 2017
AS12389Residential324
7 always on
PJSC Rostelecom
92.100.0.0/16
since Oct 2018
AS12389Residential7,756
136 always on
PJSC Rostelecom
92.100.0.0/15
since Oct 2018
AS12389Residential15,825
358 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.120.0/21

Routing history

Pattern
Stable
First seen
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1