Data as of Nov 14, 2026

89.221.124.0/23

7 residential-proxy exits · 30 days

JSC Balticom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.221.112.0/20
since Sep 2022
AS24651Residential161
57 always on
JSC Balticom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
89.221.124.0/24
since Nov 2024
AS24651ResidentialJSC Balticom
89.221.125.0/24
since Sep 2022
AS24651Residential7JSC 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
Feb 2007
Current origin since
Aug 2022 · 4.2 yr
Origin networks
2
Last change of origin
Aug 2022
Recorded history

History

Handoffs
1