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

188.6.149.0/24

38 residential-proxy exits · 30 days

Magyar Telekom Plc.

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

Residential-proxy exits

Proxy exits
38
15% of its addresses · 30 days
Providers
46
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • 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
188.6.0.0/1665,536HU-HTC-20110930Magyar Telekom Plc. (ORG-HTM1-RIPE) · HUALLOCATED PASep 30, 2011abuse@telekom.hu
└ 188.6.128.0/198,192MT-BROADBAND-DYNAMIC-DSLMagyar Telekom customers using dynamic IPASSIGNED PAJun 19, 2014abuse@telekom.hu
via HU-HTC-20110930

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.6.0.0/16

188.6.0.0/16

Routing history

Pattern
Stable
First seen
Mar 2009
Current origin since
Oct 2011 · 15 yr
Origin networks
2
Last change of origin
Oct 2011
Recorded history

History

Handoffs
1