Data as of Nov 12, 2026

217.16.136.0/24

3 residential-proxy exits · 30 days

Jotel d.o.o.

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

281 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • CatProxies
  • DataImpulse
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • Kookey
  • LemonBright
  • Maskify
  • MoMoProxy
  • Novada
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.16.128.0/20
since Dec 2014
AS197423Residential158
18 always on
Jotel d.o.o.

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
217.16.128.0/204,096RS-JOTEL-20090325Jotel d.o.o. (ORG-JD4-RIPE) · RSALLOCATED PAMar 25, 2009abuse@jotel.co.rs
└ 217.16.136.0/23512JOTEL-NETBroadband users NISASSIGNED PAApr 23, 2012abuse@jotel.co.rs
via RS-JOTEL-20090325

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
Nov 2019
Current origin since
Nov 2019 · 7.0 yr
Origin networks
1