Data as of Nov 17, 2026

217.16.138.0/23

9 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
9
1.8% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
32
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

95 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.16.139.0/2407
217.16.138.0/2403

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • DataImpulse
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • MoMoProxy
  • NovaProxy
  • Novada
  • Proxy302
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • RH7Proxy
  • RapidProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.16.128.0/20
since Dec 2014
AS197423Residential161
17 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.138.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