Data as of Nov 11, 2026

196.7.0.0/16

1 residential-proxy exit · 30 days

MTN SA

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
97% of it

Residential-proxy exits

Proxy exits
1
<0.01% of its addresses · 30 days
Spread
1 of 256
/24s with at least one exit
Providers
3
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

31 observations

Proxy providers listing exits

  • IPFly
  • Oxylabs
  • PuraRoute

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
196.7.10.0/24
since Aug 2025
AS16637ResidentialMTN SA
196.7.11.0/24
since Aug 2025
AS16637ResidentialMTN SA
196.7.93.0/24
since Nov 2017
AS37353ResidentialMTN SA
196.7.127.0/24
since Nov 2017
AS37353ResidentialMTN SA

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
196.7.0.0/1665,536UUNETMTN SA (ORG-VSA1-AFRINIC) · ZAALLOCATED PA—abuse@mtnbusiness.co.za
└ 196.7.0.0/2816MTNBUSINESS-196-7-0-0-28comment = "UPS Room monitor network at CPT1"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.0.16/298MTNBUSINESS-196-7-0-16-29comment = "Net CT"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.0.24/298MTNBUSINESS-196-7-0-24-29comment = "CT office test net for Charl"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.0.32/2732MTNBUSINESS-196-7-0-32-27comment = "Proxy net CT"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.0.96/2732MTNBUSINESS-196-7-0-96-27comment = "Proxy net Countrywide"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.0.128/2664MTNBUSINESS-196-7-0-128-26comment = "Servers net CT"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.1.0/24256MTNBUSINESS-196-7-1-0-24comment = "Cape Town"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.2.0/24256MTNBUSINESS-196-7-2-0-24comment = "CT Point-to-Point nets"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.3.0/24256MTNBUSINESS-196-7-3-0-24comment = "CT Point-to-Point nets"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.4.0/24256MTNBUSINESS-196-7-4-0-24comment = "CPT voice lab"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.5.0/24256MTNBUSINESS-196-7-5-0-24comment = "CT Point-to-Point nets"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.0/2816MTNBUSINESS-196-7-6-0-28owner = "CON028"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.16/298MTNBUSINESS-196-7-6-16-29owner = "EBV001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.24/298MTNBUSINESS-196-7-6-24-29owner = "CES001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.32/298MTNBUSINESS-196-7-6-32-29comment = "WorldCom IDN Network"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.40/298MTNBUSINESS-196-7-6-40-29comment = "WorldCom IDN Network"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.48/298MTNBUSINESS-196-7-6-48-29comment = "WorldCom IDN Network"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.56/298MTNBUSINESS-196-7-6-56-29comment = "Charl testing GMS"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.64/298MTNBUSINESS-196-7-6-64-29comment = "Voip testing in cpt1"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.72/298MTNBUSINESS-196-7-6-72-29comment = "WorldCom IDN Network"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.80/2816MTNBUSINESS-196-7-6-80-28comment = "lab in cpt1"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.96/2816MTNBUSINESS-196-7-6-96-28comment = "new hosting router"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.112/298MTNBUSINESS-196-7-6-112-29comment = "1st Contact Recruitment CC"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.120/298MTNBUSINESS-196-7-6-120-29comment = "Pep Clothing"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.128/298MTNBUSINESS-196-7-6-128-29comment = "Used for MWeb HSRP"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.136/298MTNBUSINESS-196-7-6-136-29comment = "Used for servers-cpt1-2"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.144/2816MTNBUSINESS-196-7-6-144-28owner = "MAR005"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.160/2816MTNBUSINESS-196-7-6-160-28owner = "HER010"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.176/298MTNBUSINESS-196-7-6-176-29owner = "INF024"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.184/298MTNBUSINESS-196-7-6-184-29comment = "Used for HSRP nwl"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.192/2732MTNBUSINESS-196-7-6-192-27owner = "MOU002"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.6.224/2816MTNBUSINESS-196-7-6-224-28comment = "Novagroup (Pty) Ltd"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.7.0/24256MTNBUSINESS-196-7-7-0-24comment = "IAFRICA Static Dial-up"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.8.0/221,024MTNBUSINESS-196-7-8-0-22comment = "CT customers"ASSIGNED PA—abuse@mtnbusiness.co.za
└ 196.7.12.0/24256MTNBUSINESS-196-7-12-0-24owner = "ENT006"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.13.0/24256MTNBUSINESS-196-7-13-0-24comment = "PAM003 DSL monitoring IPs"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.14.0/24256MTNBUSINESS-196-7-14-0-24owner = "LIT003"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.15.0/24256MTNBUSINESS-196-7-15-0-24owner = "AST003"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.16.0/24256MTNBUSINESS-196-7-16-0-24owner = "PIC001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.17.0/24256MTNBUSINESS-196-7-17-0-24comment = "Cape Town clients"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.18.0/24256MTNBUSINESS-196-7-18-0-24owner = "HET001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.8/298MTNBUSINESS-196-7-19-8-29owner = "CON028"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.16/2816MTNBUSINESS-196-7-19-16-28owner = "BPS001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.32/2732MTNBUSINESS-196-7-19-32-27owner = "MAS015"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.64/2664MTNBUSINESS-196-7-19-64-26owner = "ROC010"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.128/2664MTNBUSINESS-196-7-19-128-26owner = "FOS003"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.224/298MTNBUSINESS-196-7-19-224-29owner = "FOS003"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.232/298MTNBUSINESS-196-7-19-232-29owner = "CON027"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.240/298MTNBUSINESS-196-7-19-240-29owner = "MOU002"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.19.248/298MTNBUSINESS-196-7-19-248-29owner = "MOS003"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.20.0/2664MTNBUSINESS-196-7-20-0-26owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.21.0/2664MTNBUSINESS-196-7-21-0-26owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.24.0/24256MTNBUSINESS-196-7-24-0-24owner = "PIC001"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.25.0/24256MTNBUSINESS-196-7-25-0-24comment = "Cape Town small client subnets"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.29.0/24256MTNBUSINESS-196-7-29-0-24comment = "Backbone testing - Brad"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.30.0/24256MTNBUSINESS-196-7-30-0-24comment = "Hosting in Newlands"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.31.0/2664MTNBUSINESS-196-7-31-0-26owner = "ECE002"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.31.128/2732MTNBUSINESS-196-7-31-128-27comment = "Helderberg Wireless Solutions"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.32.0/204,096MTNBUSINESS-196-7-32-0-20owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.48.0/212,048MTNBUSINESS-196-7-48-0-21owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.60.0/24256MTNBUSINESS-196-7-60-0-24owner = "THE110"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.61.0/304MTNBUSINESS-196-7-61-0-30owner = "UNI009"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.61.8/298MTNBUSINESS-196-7-61-8-29owner = "SHE017"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.61.16/2816MTNBUSINESS-196-7-61-16-28owner = "SEA011"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.61.32/2732MTNBUSINESS-196-7-61-32-27comment = "DBN office range"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.61.128/25128MTNBUSINESS-196-7-61-128-25comment = "Rob hunters Probe Project"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.62.0/23512MTNBUSINESS-196-7-62-0-23comment = "EMEA DAN JNB6"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.64.0/204,096MTNBUSINESS-196-7-64-0-20owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.80.0/204,096MTNBUSINESS-196-7-80-0-20owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
└ 196.7.96.0/198,192MTNBUSINESS-196-7-96-0-19owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
└ 196.7.128.0/198,192MTNBUSINESS-196-7-128-0-19owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.160.0/212,048MTNBUSINESS-196-7-160-0-21owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.168.0/221,024MTNBUSINESS-196-7-168-0-22owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.172.0/221,024MTNBUSINESS-196-7-172-0-22owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.176.0/204,096MTNBUSINESS-196-7-176-0-20owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.192.0/204,096MTNBUSINESS-196-7-192-0-20owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.208.0/212,048MTNBUSINESS-196-7-208-0-21owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.216.0/221,024MTNBUSINESS-196-7-216-0-22comment = "Jhb Subnets"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.220.0/24256MTNBUSINESS-196-7-220-0-24comment = "Verizon New Mobility"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.221.0/24256MTNBUSINESS-196-7-221-0-24comment = "Verizon New Mobility"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET
└ 196.7.224.0/198,192MTNBUSINESS-196-7-224-0-19owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via UUNET

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

65,536 addresses
TypeAddressesShareRanges
Residential63,74097%21
Business1,7962.7%48

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Feb 2010 · 17 yr
Origin networks
2
Last change of origin
Feb 2010
Recorded history

History

Handoffs
1