Telkom SA IP Ranges
Telkom SA is the fixed-line carrier that grew out of South Africa's state telephone monopoly, and it also runs a mobile network. AS37457 is its retail internet arm, an AFRINIC object with the as-name Telkom-Internet, held by Telkom SA Ltd under the organisation handle ORG-TSL2-AFRINIC with routing maintained by TELKOM-SA-IPNET-MNT. It is not the company's only number: the older AS5713 sits in ARIN-administered space rather than AFRINIC's, carries the Openserve wholesale side, and supplies most of AS37457's transit.
- Provider
- Telkom SA
- Primary ASN
- AS37457
- Category
- ISP
- Headquarters
- Centurion, South Africa
- Announced IPv4 prefixes
- 462
- Registry
- AFRINIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS37457 (Telkom SA Ltd. - Telkom SA Ltd.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
105.224.0.0/14
105.184.0.0/14
105.228.0.0/15
197.228.0.0/15
102.249.0.0/16
105.228.0.0/16
41.149.0.0/16
102.252.0.0/16
154.69.0.0/16
105.184.0.0/16
2c0e:2200::/28
2c0e:2700::/28
2c0e:2203::/32 (IPv6)
What does a Telkom SA IP mean in a privacy test?
Telkom SA is the network on this list whose reverse DNS answers the interesting question for you, so run the lookup before anything else. A name ending in dsl.telkomsa.net is a fixed line, and the label immediately before it is a regional pool - south and east both appear in the 105.224.0.0/14 and 105.228.0.0/15 space, with the four octets of the address written out dash-separated in front. A name ending apn.mobile.telkomsa.net is a mobile data session rather than a household, and so is a name that begins 8ta- and ends telkomadsl.co.za, a survival of Telkom's old 8ta mobile brand still serving blocks in 197.228.0.0/15 and 102.249.0.0/16. Reading that label first stops you concluding a geolocation result is wrong when the address simply belongs to something moving. And some blocks return nothing at all even though the zone is properly delegated, with 41.149.0.0/16 giving NXDOMAIN from ns1.telkomsa.net, so a missing name is not evidence of anything on its own.
Where Telkom SA files its routing data
Telkom does its registry work at AFRINIC and its routing work somewhere else entirely. The aut-num for AS37457 is an AFRINIC object with routes maintained under TELKOM-SA-IPNET-MNT, but the route objects themselves are registered in NTT's IRR, and Telkom's PeeringDB record names its AS-SET with the source attached: NTTCOM::AS-37457. Those NTT objects are the most informative thing the company publishes, because their description fields say what each block is for. Inside 41.149.0.0/16 alone they read Telkom-Internet-LL, four blocks marked Telkom-Mobile, and Telkom-HIA, against an AFRINIC inetnum whose netname is TELKOM-RETAIL-INTERNET.
What none of it does is place a block in a town: there is no geofeed on the AFRINIC objects or the NTT ones. Two further cautions. Telkom's own PeeringDB entry declares unicast IPv4 support and sets its IPv6 flag to no, which sits oddly beside the IPv6 space AFRINIC has allocated it and the v6 routes it announces, so a filter built from those fields will silently drop its IPv6. And at least one route object for 41.149.0.0/16 is registered in RADB under an unrelated origin ASN, so cross-check the live origin before treating a single IRR entry as Telkom's word on anything.
Fixed line, mobile handset, or leased circuit
Separating Telkom from its customers here means watching two ASNs rather than one. AS37457 is the retail internet side and it sits behind the company's own AS5713, an older ARIN-administered number that carries the Openserve wholesale routes: the NTT route object for the covering 41.144.0.0/13 reads Telkom South Africa (Openserve) with origin AS5713, while the retail 41.149.0.0/16 inside it originates here. The same brand therefore answers from two registries and two autonomous systems, and only the origin distinguishes them. Below AS37457 the downstreams are few - five observed, among them Telkom's sibling AS37167, also registered to Telkom SA Ltd.
On inbound connections the route-object labels are the shortcut again. A block marked Telkom-Internet-LL is leased-line space where a reachable server is a normal thing to find, while an address whose PTR says apn.mobile is a handset session that will not be accepting one. Telkom's peering footprint reinforces the reading: its PeeringDB record lists only South African exchanges, DINX Durban and NAPAfrica in Cape Town, Durban and Johannesburg, with scope given as Africa and traffic as mostly inbound. This is an eyeball network terminating consumer and business access, not a hosting platform, so a listening service on AS37457 belongs to a customer rather than to Telkom.
Related tools
Frequently asked questions
What IP ranges does Telkom SA use?
Telkom's retail internet side announces them under AS37457, an AFRINIC object with the as-name Telkom-Internet held by Telkom SA Ltd. The largest announced blocks are listed above. Route objects for the space are registered in NTT's IRR rather than at AFRINIC, and Telkom's PeeringDB record names its AS-SET with that source attached, as NTTCOM::AS-37457.
Why does a Telkom SA IP appear in my privacy test?
Telkom SA is the network on this list whose reverse DNS answers the interesting question for you, so run the lookup before anything else. A name ending in dsl.telkomsa.net is a fixed line, and the label immediately before it is a regional pool - south and east both appear in the 105.224.0.0/14 and 105.228.0.0/15 space, with the four octets of the address written out dash-separated in front. A name ending apn.mobile.telkomsa.net is a mobile data session rather than a household, and so is a name that begins 8ta- and ends telkomadsl.co.za, a survival of Telkom's old 8ta mobile brand still serving blocks in 197.228.0.0/15 and 102.249.0.0/16. Reading that label first stops you concluding a geolocation result is wrong when the address simply belongs to something moving. And some blocks return nothing at all even though the zone is properly delegated, with 41.149.0.0/16 giving NXDOMAIN from ns1.telkomsa.net, so a missing name is not evidence of anything on its own.
How can I tell a Telkom fixed line from a Telkom mobile address?
By the reverse DNS. Fixed lines resolve to the four octets written dash-separated, then a regional label, then dsl.telkomsa.net, with south and east both in use. Mobile data sessions resolve under apn.mobile.telkomsa.net, and older mobile blocks answer with names that begin 8ta- and end telkomadsl.co.za, left over from Telkom's former 8ta mobile brand.
What is the difference between AS37457 and AS5713?
They are two networks of one company recorded in two different places. AS37457 is the AFRINIC-registered retail internet ASN; AS5713 is an older ARIN-administered number that carries the Openserve wholesale routes and provides most of AS37457's transit. The covering 41.144.0.0/13 has a route object originating in AS5713 while the retail 41.149.0.0/16 inside it originates in AS37457, so the origin is what tells them apart.
Does Telkom SA publish a geofeed or an allowlist?
Neither. What it does publish is unusually descriptive IRR route objects: within 41.149.0.0/16 the entries are labelled Telkom-Internet-LL, Telkom-Mobile and Telkom-HIA, which is the closest thing to an official statement of what a block is used for. Note that at least one object for that same prefix is registered in RADB under an unrelated origin ASN, so check the live origin as well.