Data as of Nov 10, 2026

89.216.167.0/24

14 residential-proxy exits · 30 days

Yettel d.o.o.

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
2
14% of its exits
Providers
49
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

646 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • IPOasis
  • Infatica
  • KindProxy
  • LemonBright
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.216.0.0/16
since Sep 2006
AS31042Residential2,311
145 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.128.0/1816,384SBBNETSerbia BroadBandASSIGNED PASep 10, 2006abuse@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.128.0/17

Routing history

Pattern
Stable
First seen
Mar 2013
Current origin since
Nov 2016 · 10 yr
Origin networks
1