Data as of Nov 11, 2026

86.59.200.0/24

32 residential-proxy exits · 30 days

Magyar Telekom Plc.

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

Residential-proxy exits

Proxy exits
32
13% of its addresses · 30 days
Providers
44
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.59.128.0/1732,768HU-HTC-20120910Magyar Telekom Plc. (ORG-HTM1-RIPE) · HUALLOCATED PASep 10, 2012abuse@telekom.hu
└ 86.59.160.0 - 86.59.223.25516,384MT-BROADBAND-DYNAMIC-DSLMagyar Telekom customers using dynamic IPASSIGNED PAJun 19, 2014abuse@telekom.hu
via HU-HTC-20120910

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 86.59.128.0/17

86.59.128.0/17

Routing history

Pattern
Stable
First seen
Aug 2011
Current origin since
Oct 2012 · 14 yr
Origin networks
2
Last change of origin
Oct 2012
Recorded history

History

Handoffs
1