Data as of Nov 15, 2026

89.216.100.0/24

24 residential-proxy exits · 30 days

Yettel d.o.o.

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Always-on exits
3
13% of its exits
Providers
43
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

15K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GoProxies
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.216.0.0/16
since Sep 2006
AS31042Residential2,488
120 always on
Yettel d.o.o.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.216.0.0/1665,536RS-SBB-NET-20060621Yettel d.o.o. (ORG-SKMS1-RIPE) · RSALLOCATED PAJun 21, 2006abuse@yettel.rs
└ 89.216.96.0/204,096SBBNETIP range for cable modem customersASSIGNED PANov 24, 2008abuse@yettel.rs
via RS-SBB-NET-20060621

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

89.216.0.0/17

Routing history

Pattern
Stable
First seen
Aug 2008
Current origin since
Aug 2008 · 18 yr
Origin networks
1