Data as of Nov 20, 2026

89.221.125.0/24

7 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
7
2.7% of its addresses · 30 days
Providers
41
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 9HTTP
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.221.124.0/23
since Aug 2022
AS24651Residential7JSC Balticom
89.221.112.0/20
since Sep 2022
AS24651Residential164
59 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
Stable
First seen
Sep 2022
Current origin since
Sep 2022 · 4.2 yr
Origin networks
1