Data as of Nov 20, 2026

89.216.33.80/29

No anonymizer space · no proxy exits in 30 days

Yettel d.o.o.

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

Residential-proxy exits

Proxy exits
2
25% of its addresses · listed by providers
Always-on exits
1
50% of its exits
Providers
20
selling exits here

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GSocks
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.216.0.0/16
since Sep 2006
AS31042Residential2,651
119 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.33.80/298URSA-NETURSA Beograd d.o.o.ASSIGNED PADec 18, 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