Data as of Nov 14, 2026

82.81.32.0/20

12 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
12
0.29% of its addresses · 30 days
Always-on exits
1
8.3% of its exits
Spread
7 of 16
/24s with at least one exit
Providers
49
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PacketStream
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.80.0.0/15
since Apr 2022
AS8551Internet provider286
13 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
82.80.0.0/15131,072IL-BEZEQ-INTERNATIONAL-20030512Bezeq International Ltd. (ORG-IL9-RIPE) · ILALLOCATED PAMay 12, 2003abuse@bezeqint.net
└ 82.81.0.0/1816,384CABLES-L2TPunknownASSIGNED PAMar 16, 2011abuse@bezeqint.net
via IL-BEZEQ-INTERNATIONAL-20030512

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
Feb 2006
Current origin since
Feb 2006 · 21 yr
Origin networks
1