Data as of Nov 21, 2026

62.201.126.0/24

9 residential-proxy exits · 30 days

Magyar Telekom Plc.

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Providers
39
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 9HTTP
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GoProxies
  • HASDATA
  • Infatica
  • KocerRoxy
  • LemonBright
  • NSTPROXY_LITE
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • Proxying
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.201.64.0/1816,384HU-HTC-20011101Magyar Telekom Plc. (ORG-HTM1-RIPE) · HUALLOCATED PAJan 10, 2002abuse@telekom.hu
└ 62.201.104.0 - 62.201.127.2556,144MT-BROADBAND-DYNAMIC-KTVMagyar Telekom customers using dynamic IPASSIGNED PAJun 30, 2014abuse@telekom.hu
via HU-HTC-20011101

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 62.201.64.0/18

62.201.64.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1