No that is just HE picking up prefixes from local free peering ixp's and reannouncing it to other markets to make money....
Telkom doesn't peer. They only peer with tier 1 ISPs or transit providers or big networks with strict equal traffic share.
True story about both HE and Telkom.
We don't see Telkom's prefixes on any of the IX's route servers. They also have a selective bilateral peering policy.
The Interconnection Database
www.peeringdb.com
Telkom seems to buy from Openserve, HE and PCCW.
AS37457 Telkom SA Ltd. Network Information
bgp.he.net
HE are ubiquitous .... You'll find them everywhere.
Openserve also have a selective bilateral peering policy.
The Interconnection Database
www.peeringdb.com
We were the first network to go onto NAP using a Mikrotik Cloud Core routers 11 or 12 years ago. They kept us in quarantine for a long time as they suspected those "toys" would not talk to Ciscos and Junipers. Today a substantial portion of IX's traffic around the world is Mikrotik, while us early adopters have grown enough to move on to more "carrier grade" routers and switches like Juniper and Arista.
It's similar with the "big" networks and their peering policies. They don't want to peer on route servers. I suspect they think Janindiebos Wireless with this CCR and his /22 block of IP addresses will cause a broadcast storm on their network, so he needs to tow the line and talk to them via IP Transit until he's big enough to sit at the top table with them.
Another example: Back in the day, I had to set up peering at LINX before IS would peer bilaterally with me in South Africa.
Today that's changed for most networks who have realised that paying INX-ZA a couple of grand a month, or peering for free with NAP is a better option than paying for transit.
Remember, this works both ways. If ABC Security and Monitoring is a client of Telkom and 90% of their clients' camera traffic is on ISPs that don't peer with Telkom, that traffic has to enter Telkom's network via IP transit. If it's cameras above cash registers in shops and restaurants, black screen monitoring is off the table. That client's a dead loss to Telkom. They only way they could make money is on the last mile fibre service to the client.
Today, the likes of Netflix and Google not only peer everywhere, but they'll drop their equipment in an ISP's cabinets, where it can connect to "upstream" servers over internet exchanges' fabric.
Imagine an ISP having to buy 40Gb or 100Gb of IPT at R20 per Mb, plus ME charges, plus port charges from Openserve just so that your clients can stream Netflix and YouTube at night. ISPs can't contend video traffic and think they'll be in business in six months. Those costs can only go one way - to the customer. That is why the likes of INX-ZA and NAP are critical to ISPs.
To assist the likes of Janindiebos Wireless - who don't meet Netflix and google's minimum bandwidth criteria for being allocated servers - there's ZANOG. We put down an array of Netflix cache servers in ADC Cape Town, connected to CINX and filled with content thanks to a very generous sponsorship from Liquid Intelligent Technologies. Now the WISP in Beaufort West or Orania can connect to CINX, peer bilaterally with ZANOG and his clients can watch Netflix for the cost of the link from his POP back to Cape Town.
Meanwhile Telkom's trying to drag themselves past Y2K.
South-Route-Viewer>traceroute 154.66.88.189
Type escape sequence to abort.
Tracing the route to core-ctn.as37640.net (154.66.88.189)
VRF info: (vrf in name/id, vrf out name/id)
1 wblv-os-cer-1-eth-t-7-100.osnet.co.za (196.25.9.25) 1 msec 2 msec 1 msec
2 196.10.140.181 2 msec 4 msec 2 msec
3 * * *
4 * * *
5 afrix-telecom-s-l.e0-19.switch1.lis1.he.net (184.104.224.113) [AS 6939] 151 msec 150 msec 150 msec
6 102.220.216.97 [AS 60171] 264 msec 263 msec 264 msec
7 core-ctn.as37640.net (154.66.88.189) [AS 37640] 263 msec 264 msec 263 msec
South-Route-Viewer>
263 Milliseconds from Bellville to Rondebosch.
The sad part of all this is that they have a brilliant network. We have less support tickets in any 12 month period from Openserve FTTx clients than we do in one day on certain other FNOs. ...Croak..
