Data as of Nov 13, 2026

217.65.96.0/19

2,176 residential-proxy exits · 30 days

Magyar Telekom Plc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
97% of it

Residential-proxy exits

Proxy exits
2,176
27% of its addresses · 30 days
Always-on exits
4
0.18% of its exits
Spread
22 of 32
/24s with at least one exit
Providers
108
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

419K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.65.96.0/198,192HU-HTC-20001101Magyar Telekom Plc. (ORG-HTM1-RIPE) · HUALLOCATED PAOct 26, 2001abuse@telekom.hu
└ 217.65.96.0/23512MT-HOSTINGHosting customers using static IPASSIGNED PAJul 25, 2012abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.98.0/23512MT-BROADBAND-DYNAMIC-DSLMagyar Telekom customers using dynamic IPASSIGNED PAMar 22, 2017abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.100.0/24256MT-HOSTINGHosting customers using static IPASSIGNED PAJun 11, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.101.0/24256MT-BROADBAND-STATIC-KTVMagyar Telekom customers using static IPASSIGNED PAJun 11, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.102.0/23512KABELSZAT-NETInternet service SG870012ASSIGNED PAJun 19, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.104.0/24256MLLN-SPLITBLOCKInternet service - splitblockASSIGNED PAOct 15, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.105.0 - 217.65.108.2551,024MT-BROADBAND-DYNAMIC-KTVMagyar Telekom customers using dynamic IPASSIGNED PANov 8, 2022abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.110.0/24256MLLN-SPLITBLOCKMagyar Telekom leased line customersASSIGNED PAJun 4, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.111.0/24256MT-BROADBAND-DYNAMIC-KTVMagyar Telekom customers using dynamic IPASSIGNED PANov 8, 2022abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.112.0/221,024MT-BROADBAND-DYNAMIC-DSLMagyar Telekom customers using dynamic IPASSIGNED PAMar 22, 2017abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.116.0 - 217.65.118.255768INETSInernet service SA350000ASSIGNED PAJun 30, 2014abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.119.0/24256MT-BROADBAND-DYNAMIC-KTVMagyar Telekom customers using dynamic IPASSIGNED PANov 8, 2022abuse@telekom.hu
via HU-HTC-20001101
└ 217.65.120.0/212,048MT-BROADBAND-NAT-FIXEDLINEMagyar Telekom customers using dynamic IPASSIGNED PAMay 6, 2022abuse@telekom.hu
via HU-HTC-20001101

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

8,192 addresses
TypeAddressesShareRanges
Residential7,93697%29
Hosting2563.1%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2008 · 18 yr
Origin networks
2
Last change of origin
Jun 2008
Recorded history

History

Handoffs
1