Data as of Nov 19, 2026

188.92.16.0/21

178 residential-proxy exits · 30 days

JSC Balticom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
178
8.7% of its addresses · 30 days
Always-on exits
91
51% of its exits
Spread
5 of 8
/24s with at least one exit
Providers
83
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

466K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
188.92.22.0/24
since Dec 2024
AS24651Residential156
89 always on
JSC Balticom
via SIA AnaDana
188.92.23.0/24
since Sep 2024
AS24651ResidentialJSC Balticom
via SIA AnaDana

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
188.92.16.0/212,048LV-BALTICOM-20090421JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PAApr 21, 2009abuse@balticom.info
└ 188.92.16.0/23512LVBALTICOM-NETWORK-188-16"Balticom" JSCASSIGNED PAJul 22, 2013abuse@balticom.info
via LV-BALTICOM-20090421
└ 188.92.18.0/24256LVBALTICOM-NETWORK-188-18-R"Balticom" JSCASSIGNED PASep 16, 2019abuse@balticom.info
via LV-BALTICOM-20090421
└ 188.92.19.0/24256LVBALTICOM-SPILS-NETWORK-1"Balticom" JSCASSIGNED PASep 16, 2019abuse@balticom.info
via LV-BALTICOM-20090421
└ 188.92.20.0/23512LVBALTICOM-NETWORK-188-20-R"Balticom" JSCASSIGNED PASep 14, 2016abuse@balticom.info
via LV-BALTICOM-20090421
└ 188.92.22.0/23512anaDana-NetSIA AnaDana (ORG-SA1348-RIPE) · LVSUB-ALLOCATED PAApr 5, 2013abuse@balticom.info

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2009
Current origin since
Apr 2013 · 14 yr
Origin networks
2
Last change of origin
Apr 2013
Recorded history

History

Handoffs
1