LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

188.36.4.0/24

17 residential-proxy exits · 30 days

Magyar Telekom Plc.

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
1
5.9% of its exits
Providers
39
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 2Captcha
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • KindProxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.36.0.0/1665,536HU-HTC-20090327Magyar Telekom Plc. (ORG-HTM1-RIPE) · HUALLOCATED PAMar 27, 2009abuse@telekom.hu
└ 188.36.0.0/1816,384MT-BROADBAND-DYNAMIC-KTVMagyar Telekom customers using dynamic IPASSIGNED PAMay 7, 2014abuse@telekom.hu
via HU-HTC-20090327

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 188.36.0.0/16

188.36.0.0/16

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1