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

196.22.64.0/18

No anonymizer space · no proxy exits in 30 days

MTN SA

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

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.22.64.0/1816,384NET-196-22-64-0-1MTN SA (ORG-VSA1-AFRINIC) · ZAALLOCATED PA—abuse@mtnbusiness.co.za
└ 196.22.64.0/2664MTNBUSINESS-196-22-64-0-26comment = "Nic's ip telephony systems"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.65.0/2664MTNBUSINESS-196-22-65-0-26comment = "CCM Cluster North"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.65.64/2664MTNBUSINESS-196-22-65-64-26comment = "Broadsoft cluster north"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.65.128/2664MTNBUSINESS-196-22-65-128-26comment = "CCM Cluster South"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.65.192/2664MTNBUSINESS-196-22-65-192-26comment = "Broadsoft cluster south"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.66.0/2664MTNBUSINESS-196-22-66-0-26comment = "Managment subnet behind JNB6 servers PIX"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.66.64/2664MTNBUSINESS-196-22-66-64-26comment = "voice-inbound messages in jnb6"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.67.0/24256MTNBUSINESS-196-22-67-0-24comment = "voice-demo area in jnb6"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.68.0/24256MTNBUSINESS-196-22-68-0-24comment = "EWS deployment in jnb6"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.70.0/23512MTNBUSINESS-196-22-70-0-23comment = "L2TP terminate ERX (gw13.jnb6)"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.72.0/221,024MTNBUSINESS-196-22-72-0-22comment = "new UUDial router - gw13.jnb6"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.79.0/24256MTNBUSINESS-196-22-79-0-24comment = "Point-to-Point subnets"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.79.0/2816MTNBUSINESS-196-22-79-0-28owner = "UUN004"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.56/304MTNBUSINESS-196-22-79-56-30owner = "SPO001"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.60/304MTNBUSINESS-196-22-79-60-30owner = "MIL007"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.108/304MTNBUSINESS-196-22-79-108-30comment = "hosting unknown server"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.148/304MTNBUSINESS-196-22-79-148-30comment = "UUC-VID001-1-ZA"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.152/304MTNBUSINESS-196-22-79-152-30owner = "MAV001"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.160/2732MTNBUSINESS-196-22-79-160-27owner = "COM010"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.79.204/304MTNBUSINESS-196-22-79-204-30owner = "COM027"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-79-0-24
└ 196.22.80.0/221,024MTNBUSINESS-196-22-80-0-22comment = "Mostly Available"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.81.0/24256MTNBUSINESS-196-22-81-0-24comment = "being used by Datacentrix"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-80-0-22
└ 196.22.82.0/23512MTNBUSINESS-196-22-82-0-23comment = "EMEA DAN"ASSIGNED PA—abuse@mtnbusiness.co.za
via MTNBUSINESS-196-22-80-0-22
└ 196.22.84.0/221,024MTNBUSINESS-196-22-84-0-22comment = "EMEA DAN"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.94.0/24256MTNBUSINESS-196-22-94-0-24owner = "COM027"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.96.0/221,024MTNBUSINESS-196-22-96-0-22comment = "SME Customers in Gauteng"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.100.0/221,024MTNBUSINESS-196-22-100-0-22comment = "SME Customers in Cape Town"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.104.0/23512MTNBUSINESS-196-22-104-0-23comment = "SME Customers in Durban"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.106.0/23512MTNBUSINESS-196-22-106-0-23comment = "SME Customers in PE"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.112.64/2664MTNBUSINESS-196-22-112-64-26owner = "COM010"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.112.128/2664MTNBUSINESS-196-22-112-128-26owner = "COM010"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1
└ 196.22.126.0/24256MTNBUSINESS-196-22-126-0-24owner = "COM027"ASSIGNED PA—abuse@mtnbusiness.co.za
via NET-196-22-64-0-1

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

16,384 addresses
TypeAddressesShareRanges
Residential12,66477%10
Business3,72023%21

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

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

History

Handoffs
1