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

188.68.26.0/24

36 residential-proxy exits · 30 days

LTD AtelRybinsk

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

Residential-proxy exits

Proxy exits
36
14% of its addresses · 30 days
Providers
47
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

608 observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BlurPath
  • BottingTools
  • BuyingProxy
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxiesVision
  • Proxio
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.68.16.0/204,096RU-ATELRYBINSK-20090825LTD AtelRybinsk (ORG-LA723-RIPE) · RUALLOCATED PAOct 29, 2014aparikov@atel.me
└ 188.68.16.0 - 188.68.30.2553,840AtelRybinsk_PPTPclientsunknownASSIGNED PASep 2, 2016aparikov@atel.me
via RU-ATELRYBINSK-20090825

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 188.68.16.0/20

188.68.16.0/20

Routing history

Pattern
Rotating
First seen
Dec 2012
Current origin since
Dec 2014 · 12 yr
Origin networks
3
Last change of origin
Oct 2022
Recorded history

History

Handoffs
2