Data as of Nov 12, 2026

46.221.60.0/24

15 residential-proxy exits · 30 days

Vodafone Net Iletisim Hizmetler AS · space held by Vodafone Telekomunikasyon A.S.

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Providers
56
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PrivateByte
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.221.0.0/18
since Jul 2019
AS15924Residential504
83 always on
Vodafone Telekomunikasyon A.S.
46.221.0.0/16
since Dec 2018
AS15897Mobile18,112
83 always on
Vodafone Telekomunikasyon A.S.

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
46.221.0.0/1665,536TR-RTNET-20110121Vodafone Telekomunikasyon A.S. (ORG-RIHV1-RIPE) · TRALLOCATED PAJan 21, 2011abuse-tr@vodafone.com
└ 46.221.0.0/1816,384TR-VFNET-20191121unknownSUB-ALLOCATED PANov 21, 2019abuse-tr@vodafone.com
via TR-RTNET-20110121

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
Jan 2019
Current origin since
May 2019 · 7.5 yr
Origin networks
2
Last change of origin
May 2019
Recorded history

History

Handoffs
1