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

88.82.92.0/23

2 residential-proxy exits · 30 days

Radiokom Ltd. · space held by PJSC "Vimpelcom"

Announcement
this exact prefix
No RPKI
Announced by
AS34518
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
21
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

217 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
88.82.92.0/2401
88.82.93.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • IPPeak
  • Infatica
  • LightningProxies
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.82.92.0/22
since Jun 2024
AS34518Residential5PJSC "Vimpelcom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
88.82.64.0/198,192RU-SOVINTEL-20051216PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 16, 2005abuse-b2b@beeline.ru
└ 88.82.92.0 - 88.82.92.2324Fatum_network_for_clients-net1Fatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.24/298cristal_fatum"Cristal" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.32 - 88.82.92.11988Fatum_network_for_clients-net2Fatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.120/298eldorado1_fatum"Eldorado" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.128/298eldorado2_fatum"Eldorado" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.136/298eldorado3_fatum"Eldorado" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.144/298Fatum_network_for_clients-net3Fatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.152/298master_clining_fatum"Master Clining" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.160/298Fatum_network_for_clients-net4Fatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.168/298snabzhenec_fatum"Snabzhenec" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.92.176 - 88.82.93.103184Fatum_network_for_clientsFatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.93.104/298PONachalo_fatumPO "Nachalo" ltdASSIGNED PAApr 15, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216
└ 88.82.93.112 - 88.82.93.255144Fatum_network_for_clients-net5Fatum network for clients 07.08.2008ASSIGNED PAApr 22, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2008
Current origin since
Dec 2025 · 11 mo
Origin networks
1