Data as of Nov 21, 2026

89.221.120.0/24

5 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
37
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

5.0K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.221.112.0/20
since Sep 2022
AS24651Residential210
58 always on
JSC Balticom

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
89.221.112.0/204,096LV-BALTICOM-20061002JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PAJun 22, 2022abuse@balticom.info
└ 89.221.120.0 - 89.221.127.2542,047Net-BalticomJSC Balticom (ORG-JB1-RIPE) · LVASSIGNED PAFeb 17, 2010abuse@balticom.info

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Rotating
First seen
Jul 2022
Current origin since
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Jun 2025
Recorded history

History

Handoffs
3