Data as of Nov 12, 2026

202.70.41.0/24

58 residential-proxy exits · 30 days

Univision LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
58
23% of its addresses · 30 days
Providers
53
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

912 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LemonLabs
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • Novada
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
202.70.32.0/204,096UNIVISIONLLC-MNUnivision LLC (ORG-UL8-AP) · MNALLOCATED PORTABLE—abuse@unitel.mn
└ 202.70.41.1 - 202.70.41.66MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.9 - 202.70.41.146MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.17 - 202.70.41.226MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.25 - 202.70.41.306MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.33 - 202.70.41.386MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.41 - 202.70.41.466MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.65 - 202.70.41.706MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.73 - 202.70.41.786MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.81 - 202.70.41.866MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.89 - 202.70.41.946MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.97 - 202.70.41.1026MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.105 - 202.70.41.1106MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.113 - 202.70.41.1186MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.121 - 202.70.41.1266MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.129 - 202.70.41.1346MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.137 - 202.70.41.1426MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.153 - 202.70.41.1586MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.161 - 202.70.41.1666MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.169 - 202.70.41.1746MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.177 - 202.70.41.1826MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.185 - 202.70.41.1906MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.193 - 202.70.41.1986MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.201 - 202.70.41.2066MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.225 - 202.70.41.2306MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn
└ 202.70.41.233 - 202.70.41.2386MCSCOMUnivision LLC (ORG-UL8-AP) · MNASSIGNED NON-PORTABLE—abuse@unitel.mn

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2008
Current origin since
May 2008 · 18 yr
Origin networks
1