Data as of Nov 18, 2026

84.110.108.0/22

5 residential-proxy exits · 30 days

Bezeq International Ltd.

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2.8K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • CliProxy
  • DataImpulse
  • FastProxy
  • GloryCloud
  • IPFly
  • IPROCKET_BASIC
  • IPRoyal
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • NiuProxy
  • Novada
  • Proxy302
  • Proxy4U
  • ProxyRack
  • RapidProxy
  • RolaProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.110.96.0/20
since Nov 2005
AS8551Internet provider27
1 always on
Bezeq International Ltd.

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
84.108.0.0 - 84.111.135.255231,424IL-BEZEQ-INTERNATIONAL-20040510Bezeq International Ltd. (ORG-IL9-RIPE) · ILALLOCATED PANov 21, 2025abuse@bezeqint.net
└ 84.110.108.0/221,024BEZEQINT-STATICfor static customersASSIGNED PAFeb 13, 2008abuse@bezeqint.net
via IL-BEZEQ-INTERNATIONAL-20040510

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2012
Current origin since
Jan 2012 · 15 yr
Origin networks
1