Data as of Nov 11, 2026

217.65.112.0/22

25 residential-proxy exits · 30 days

Magyar Telekom Plc.

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

Residential-proxy exits

Proxy exits
25
2.4% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

476 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.65.114.0/24010
217.65.112.0/2408
217.65.115.0/2407

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Decodo
  • FastProxy
  • GSocks
  • Geonix
  • IPRoyal
  • Infatica
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyHat
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each 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.112.0/221,024MT-BROADBAND-DYNAMIC-DSLMagyar Telekom customers using dynamic IPASSIGNED PAMar 22, 2017abuse@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.

Network & registry

Routing timeline

Who has announced 217.65.96.0/19

217.65.96.0/19

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