Skip to main content

AS37009

ORG-MMTL1-AFRINIC

MTC - Mobile Telecommunications, Ltd.

Registry

Authoritative registration data

AS number
37009
Name
ORG-MMTL1-AFRINIC
Organisation
MTC - Mobile Telecommunications, Ltd.
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

113

IPv6 prefixes

1

Total announced

114

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS37009
105.232.0.0/16 IPv4 /16 not checked
105.232.0.0/17 IPv4 /17 not checked
197.243.128.0/17 IPv4 /17 RPKI valid
197.243.128.0/18 IPv4 /18 not checked
197.243.192.0/18 IPv4 /18 not checked
41.219.64.0/18 IPv4 /18 RPKI valid
41.63.192.0/18 IPv4 /18 not checked
105.232.128.0/20 IPv4 /20 not checked
105.232.144.0/20 IPv4 /20 RPKI valid
105.232.160.0/20 IPv4 /20 RPKI valid
105.232.176.0/20 IPv4 /20 RPKI valid
41.219.124.0/23 IPv4 /23 RPKI valid
105.232.128.0/24 IPv4 /24 not checked
105.232.129.0/24 IPv4 /24 RPKI valid
105.232.130.0/24 IPv4 /24 not checked
105.232.131.0/24 IPv4 /24 not checked
105.232.132.0/24 IPv4 /24 not checked
105.232.133.0/24 IPv4 /24 not checked
105.232.134.0/24 IPv4 /24 RPKI valid
105.232.135.0/24 IPv4 /24 RPKI valid
105.232.136.0/24 IPv4 /24 not checked
105.232.137.0/24 IPv4 /24 not checked
105.232.138.0/24 IPv4 /24 not checked
105.232.139.0/24 IPv4 /24 RPKI valid
105.232.140.0/24 IPv4 /24 RPKI valid
105.232.141.0/24 IPv4 /24 RPKI valid
105.232.142.0/24 IPv4 /24 not checked
105.232.143.0/24 IPv4 /24 RPKI valid
105.232.144.0/24 IPv4 /24 RPKI valid
105.232.145.0/24 IPv4 /24 RPKI valid
105.232.146.0/24 IPv4 /24 RPKI valid
105.232.147.0/24 IPv4 /24 RPKI valid
105.232.148.0/24 IPv4 /24 RPKI valid
105.232.149.0/24 IPv4 /24 RPKI valid
105.232.150.0/24 IPv4 /24 not checked
105.232.151.0/24 IPv4 /24 RPKI valid
105.232.152.0/24 IPv4 /24 RPKI valid
105.232.153.0/24 IPv4 /24 not checked
105.232.154.0/24 IPv4 /24 RPKI valid
105.232.155.0/24 IPv4 /24 RPKI valid
105.232.156.0/24 IPv4 /24 RPKI valid
105.232.157.0/24 IPv4 /24 RPKI valid
105.232.158.0/24 IPv4 /24 not checked
105.232.159.0/24 IPv4 /24 RPKI valid
105.232.160.0/24 IPv4 /24 RPKI valid
105.232.161.0/24 IPv4 /24 RPKI valid
105.232.162.0/24 IPv4 /24 RPKI valid
105.232.163.0/24 IPv4 /24 not checked
105.232.164.0/24 IPv4 /24 not checked
105.232.165.0/24 IPv4 /24 not checked
105.232.166.0/24 IPv4 /24 not checked
105.232.167.0/24 IPv4 /24 RPKI valid
105.232.168.0/24 IPv4 /24 RPKI valid
105.232.169.0/24 IPv4 /24 RPKI valid
105.232.170.0/24 IPv4 /24 RPKI valid
105.232.171.0/24 IPv4 /24 not checked
105.232.172.0/24 IPv4 /24 not checked
105.232.173.0/24 IPv4 /24 RPKI valid
105.232.174.0/24 IPv4 /24 not checked
105.232.175.0/24 IPv4 /24 not checked
105.232.176.0/24 IPv4 /24 RPKI valid
105.232.177.0/24 IPv4 /24 not checked
105.232.178.0/24 IPv4 /24 not checked
105.232.179.0/24 IPv4 /24 not checked
105.232.180.0/24 IPv4 /24 RPKI valid
105.232.181.0/24 IPv4 /24 RPKI valid
105.232.182.0/24 IPv4 /24 not checked
105.232.183.0/24 IPv4 /24 not checked
105.232.184.0/24 IPv4 /24 not checked
105.232.185.0/24 IPv4 /24 not checked
105.232.186.0/24 IPv4 /24 RPKI valid
105.232.187.0/24 IPv4 /24 RPKI valid
105.232.188.0/24 IPv4 /24 not checked
105.232.189.0/24 IPv4 /24 not checked
105.232.190.0/24 IPv4 /24 RPKI valid
105.232.191.0/24 IPv4 /24 RPKI valid
105.232.192.0/24 IPv4 /24 RPKI valid
196.3.94.0/24 IPv4 /24 RPKI valid
197.243.239.0/24 IPv4 /24 not checked
197.243.255.0/24 IPv4 /24 RPKI valid
41.219.113.0/24 IPv4 /24 RPKI valid
41.219.114.0/24 IPv4 /24 RPKI valid
41.219.115.0/24 IPv4 /24 not checked
41.219.119.0/24 IPv4 /24 not checked
41.219.123.0/24 IPv4 /24 RPKI valid
41.219.64.0/24 IPv4 /24 RPKI valid
41.219.65.0/24 IPv4 /24 not checked
41.219.66.0/24 IPv4 /24 RPKI valid
41.219.67.0/24 IPv4 /24 RPKI valid
41.219.68.0/24 IPv4 /24 RPKI valid
41.219.69.0/24 IPv4 /24 RPKI valid
41.219.70.0/24 IPv4 /24 RPKI valid
41.219.71.0/24 IPv4 /24 RPKI valid
41.219.72.0/24 IPv4 /24 not checked
41.219.73.0/24 IPv4 /24 RPKI valid
41.219.74.0/24 IPv4 /24 not checked
41.219.75.0/24 IPv4 /24 not checked
41.219.78.0/24 IPv4 /24 not checked
41.219.80.0/24 IPv4 /24 not checked
41.219.82.0/24 IPv4 /24 RPKI valid
41.63.232.0/24 IPv4 /24 not checked
41.63.233.0/24 IPv4 /24 RPKI valid
41.63.234.0/24 IPv4 /24 not checked
41.63.235.0/24 IPv4 /24 not checked
41.63.236.0/24 IPv4 /24 RPKI valid
41.63.237.0/24 IPv4 /24 RPKI valid
41.63.238.0/24 IPv4 /24 not checked
41.63.240.0/24 IPv4 /24 RPKI valid
41.63.244.0/24 IPv4 /24 not checked
41.63.245.0/24 IPv4 /24 not checked
41.63.247.0/24 IPv4 /24 not checked
41.63.248.0/24 IPv4 /24 RPKI valid
41.63.249.0/24 IPv4 /24 RPKI valid
2c0f:f778::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS37009
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
IXP Namibia 10,000 Mbps IPv4
NAPAfrica IX Cape Town 20,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 50,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS37009 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS37009 in AS paths

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS37009 in AS paths

Observed downstreams
Families
AS37513 ORG-PoN1-AFRINIC 129 647
v4
AS37201 ORG-BW1-AFRINIC 57 64
v4
AS327694 ORG-NA24-AFRINIC 14 15
v4
AS37662 ORG-WIOC1-AFRINIC 5 5
v4

No rows match “”.

Showing – of

Uncertain adjacencies

42 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.