Google claims that its new Equiano subsea cable will increase South Africa's internet speed three-fold

DA-LION-619

Honorary Master
Joined
Aug 22, 2009
Messages
13,777
I could've sworn 10 years ago I was getting ~180ms to Germany, now it's ~200.
I'm absolute convinced that if routing was taken seriously Cape Town would be seeing ~140ms and Durban would be seeing ~160ms to London.
It’s not a conspiracy lol.
Your transit isn’t handled by Seacom.
 

Vorastra

Honorary Master
Joined
Jan 13, 2013
Messages
14,117
Router: lg-01-dur.za
Command: ping ip 172.107.96.75
Sending 5, 100-byte ICMP Echos to 172.107.96.75, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 164/164/168 ms

Well done, you managed to get a reading from Seacom PoP to Seacom PoP which means optimal routing.

It’s not a conspiracy lol.
No one said it was, just you.

Your transit isn’t handled by Seacom.
So I used that tool to ping from their London PoP to my 2nd hop which is at the Teraco building <2ms away.

Code:
PING 102.67.179.3 (102.67.179.3) 56(84) bytes of data.
64 bytes from 102.67.179.3: icmp_seq=1 ttl=57 time=182 ms
64 bytes from 102.67.179.3: icmp_seq=2 ttl=57 time=182 ms
64 bytes from 102.67.179.3: icmp_seq=3 ttl=57 time=182 ms
64 bytes from 102.67.179.3: icmp_seq=4 ttl=57 time=182 ms

Oh look. It's basically the same ping (184ms) I'm getting.
Going up Seacom changes nothing. It's local routing, as @Geoff.D and I are discussing.

Like I said, local routing is garbage. If routing was as preferential and optimal as Seacom to Seacom PoP then I'd be getting 164ms too. But no one does because garbage local routing.
 

DA-LION-619

Honorary Master
Joined
Aug 22, 2009
Messages
13,777
It would basically be no different. @DA-LION-619 has just posted an intra-Seacom trace, which obviously means optimal routing.
Seacom's London PoP get's the same ~184ms to me, as I get to it on whatever cable I'm on.
No I posted a ping test to https://lg.lon.psychz.net/
Tracing the route to lg.lon.psychz.net (172.107.96.75)
VRF info: (vrf in name/id, vrf out name/id)
1 ae-2-21.er-02-dur.za.seacomnet.com (105.23.232.1) [AS 37100] 0 msec 0 msec 0 msec
2 xe-0-0-32-1.cr-02-emg.za.seacomnet.com (105.16.14.113) [AS 37100] [MPLS: Label 37835 Exp 0] 148 msec 152 msec 152 msec
3 xe-0-0-66-2.cr-01-mrs.fr.seacomnet.com (105.16.10.198) [AS 37100] [MPLS: Label 7573 Exp 0] 148 msec 152 msec 148 msec
4 xe-0-0-1-0.br-02-mrs.fr.seacomnet.com (105.16.33.253) [AS 37100] 152 msec 148 msec 152 msec
5 92.60.248.233 [AS 3257] 148 msec 152 msec 148 msec
6 ae33.cr0-lon1.ip4.gtt.net (89.149.137.105) [AS 3257] 164 msec 164 msec 164 msec
7 77.67.124.46 [AS 3257] 168 msec 168 msec 164 msec
8 routing-spree-lon.AS40676.net (104.216.182.19) [AS 40676] 168 msec 164 msec 168 msec
9 lg.lon.psychz.net (172.107.96.75) [AS 40676] 168 msec 164 msec 164 msec

Not all networks peer, neither does everything go over the internet.
Tracing the route to ethernet8-100.terdbn-igw1.net.echosp.link (102.67.179.3)
VRF info: (vrf in name/id, vrf out name/id)
1 ae-2-21.er-01-lhr.uk.seacomnet.com (105.22.128.1) [AS 37100] 0 msec 0 msec 0 msec
2 ae-1.cr-01-lhr.uk.seacomnet.com (105.16.34.1) [AS 37100] [MPLS: Label 24251 Exp 0] 148 msec
ae-2.cr-02-lhr.uk.seacomnet.com (105.16.34.2) [AS 37100] [MPLS: Label 24053 Exp 0] 152 msec
ae-2.cr-01-lhr.uk.seacomnet.com (105.16.35.1) [AS 37100] [MPLS: Label 24251 Exp 0] 148 msec
3 105.16.15.233 [AS 37100] [MPLS: Label 24026 Exp 0] 144 msec
xe-0-0-0-9.cr-01-cpt.za.seacomnet.com (105.16.10.229) [AS 37100] [MPLS: Label 24030 Exp 0] 156 msec
xe-0-7-0-0.cr-01-cpt.za.seacomnet.com (105.16.14.82) [AS 37100] [MPLS: Label 24030 Exp 0] 144 msec
4 xe-0-1-5.pp-01-cpt.za.seacomnet.com (105.16.30.8) [AS 37100] 148 msec
xe-0-1-6.pp-01-cpt.za.seacomnet.com (105.16.31.8) [AS 37100] 144 msec
xe-0-1-5.pp-01-cpt.za.seacomnet.com (105.16.30.8) [AS 37100] 152 msec
5 * * *
6 rtdcj-os-cer-1-wan.osnet.co.za (196.25.199.141) [AS 5713] 168 msec
rtdcj-os-cer-1-wan.osnet.co.za (196.25.153.41) [AS 5713] 160 msec
rtdcj-os-cer-1-wan.osnet.co.za (196.25.199.141) [AS 5713] 160 msec
7 echotel-gw.osnet.co.za (196.25.199.142) [AS 5713] 164 msec 164 msec 160 msec
8 ethernet8-100.terdbn-igw1.net.echosp.link (102.67.179.3) [AS 327693] 176 msec 172 msec 172 msec
Tracing the route to ethernet8-100.terdbn-igw1.net.echosp.link (102.67.179.3)
VRF info: (vrf in name/id, vrf out name/id)
1 ae-2-21.er-02-dur.za.seacomnet.com (105.23.232.1) [AS 37100] 0 msec 0 msec 0 msec
2 105.16.13.70 [AS 37100] 4 msec 0 msec 0 msec
3 * * *
4 rtdcj-os-cer-1-wan.osnet.co.za (196.25.153.41) [AS 5713] 12 msec 16 msec
rtdcj-os-cer-1-wan.osnet.co.za (196.25.199.141) [AS 5713] 12 msec
5 echotel-gw.osnet.co.za (196.25.199.142) [AS 5713] 12 msec 8 msec
echotel-gw.osnet.co.za (196.25.153.42) [AS 5713] 12 msec
6 ethernet8-100.terdbn-igw1.net.echosp.link (102.67.179.3) [AS 327693] 8 msec 8 msec 8 msec
 
Last edited:

PaulMurkin

Expert Member
Joined
Jan 31, 2020
Messages
3,455
so my next question, is it possible to reduce latency over vast distances? or its simply not possible technically?
Not possible with the current state of technology. Light travels at 3 x 10 E 8 metres/second, its not changing, nor has it changed. Imagine if it did, we'd be able to probably succeed at time travel
 

PaulMurkin

Expert Member
Joined
Jan 31, 2020
Messages
3,455

cguy

Executive Member
Joined
Jan 2, 2013
Messages
8,527
Last edited:

Magnum

Executive Member
Joined
Mar 12, 2013
Messages
6,592
You had a whole 3GB? Larnie.
Remember when 1GB top-ups were R99.
Good times.
I started thinking of uncapped when a Gig was R15. Not that the 384Kbps line could eat that much.. Now there 100Mbps fiber. If you told me this is the Kind of internet speeds I would have laughed at you.
 

DA-LION-619

Honorary Master
Joined
Aug 22, 2009
Messages
13,777
I could've sworn 10 years ago I was getting ~180ms to Germany, now it's ~200.
I'm absolute convinced that if routing was taken seriously Cape Town would be seeing ~140ms and Durban would be seeing ~160ms to London.
Hurricane Electric
core1.cpt1.he.net> traceroute 172.107.96.75 source 216.218.252.112 | 149.134ms
core1.jnb1.he.net> traceroute 172.107.96.75 source 216.218.252.236 | 157ms
core1.dur1.he.net> traceroute 172.107.96.75 source 216.218.252.103 | 164.457ms

Web Squad
[capetown.lg.as328137.net] trace to 172.107.96.75 | 144ms
[durban.lg.as328137.net] trace to 172.107.96.75 | 202.5ms
[joburg.lg.as328137.net] trace to 172.107.96.75 | 194.8ms

Vodacom
ZAF West Coast Cape Town [AS 36994] | 140ms
ZAF Central Midrand [AS 36994] | 158ms

Going up Seacom changes nothing. It's local routing, as @Geoff.D and I are discussing.

Like I said, local routing is garbage. If routing was as preferential and optimal as Seacom to Seacom PoP then I'd be getting 164ms too. But no one does because garbage local routing.
No one? My trace routes must be a hoax.
Tracing route to unassigned.psychz.net [172.107.96.75]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms 172.16.0.1
2 7 ms 7 ms 6 ms 197.234.241.1
4 177 ms 180 ms 180 ms ce-0-2-0-0.cr-01-jnb.za.seacomnet.com [105.16.28.1]
5 167 ms 166 ms 171 ms ce-0-2-0-1.cr-01-cpt.za.seacomnet.com [105.16.15.250]
6 164 ms 164 ms 164 ms xe-0-1-0-3.cr-01-lhr.uk.seacomnet.com [105.16.11.78]
7 161 ms 161 ms 160 ms xe-0-0-1-0.br-02-lhr.uk.seacomnet.com [105.16.35.253]
8 161 ms 162 ms 161 ms 82.112.115.169
9 162 ms 160 ms 162 ms ce-0-2-3.a02.londen12.uk.ce.gin.ntt.net [83.231.146.170]
10 161 ms 161 ms 162 ms routing-spree-lon.AS40676.net [104.216.182.19]
11 161 ms 161 ms 160 ms unassigned.psychz.net [172.107.96.75]
Tracing route to uk.torguard.com [109.123.118.38]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 172.16.0.1
2 7 ms 6 ms 6 ms 197.234.241.1
3 6 ms 5 ms 5 ms ae-2-113.er-01-jnb.za.seacomnet.com [105.22.32.217]
4 162 ms 166 ms 164 ms ce-0-3-0-0.cr-02-jnb.za.seacomnet.com [105.16.29.2]
5 168 ms 164 ms 164 ms ce-0-3-0-3.cr-02-cpt.za.seacomnet.com [105.16.14.194]
6 166 ms 168 ms 165 ms xe-0-0-0-3.cr-02-lhr.uk.seacomnet.com [105.16.10.154]
7 164 ms 160 ms 161 ms ae-3-0.pp-01-lhr.uk.seacomnet.com [105.16.34.8]
8 163 ms 162 ms 161 ms linx-224.inx.as13213.net [195.66.226.9]
9 161 ms 182 ms 162 ms no-ptr.midphase.com [98.158.181.117]
10 161 ms 162 ms 161 ms 212.78.92.1
11 162 ms 163 ms 162 ms MP5.mpdedicated.com [109.123.118.38]
Tracing route to ger.torguard.com [93.177.73.202]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms 172.16.0.1
2 5 ms 5 ms 4 ms 197.234.241.1
3 5 ms 5 ms 5 ms be6296.ccr51.jnb01.atlas.cogentco.com [206.249.0.209]
4 160 ms 160 ms 475 ms be2436.ccr21.lon02.atlas.cogentco.com [130.117.0.89]
5 161 ms 179 ms 161 ms be2573.ccr42.lon13.atlas.cogentco.com [154.54.62.5]
6 167 ms 168 ms 168 ms be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]
7 194 ms 273 ms 194 ms be2814.ccr42.fra03.atlas.cogentco.com [130.117.0.142]
8 193 ms 193 ms 194 ms be3187.agr41.fra03.atlas.cogentco.com [130.117.1.117]
9 175 ms 173 ms 263 ms be3576.nr51.b015923-1.fra03.atlas.cogentco.com [154.25.5.50]
10 173 ms 189 ms 174 ms m247.demarc.cogentco.com [149.11.180.202]
11 174 ms 174 ms 174 ms vlan2946.agg1.fra4.de.m247.com [193.27.15.243]
12 178 ms 177 ms 178 ms irb-0.agg1.thg1.nl.m247.com [212.103.51.25]
13 173 ms 173 ms 174 ms 93.177.73.202
 

itareanlnotani

Executive Member
Joined
Sep 14, 2008
Messages
6,760
I started thinking of uncapped when a Gig was R15. Not that the 384Kbps line could eat that much.. Now there 100Mbps fiber. If you told me this is the Kind of internet speeds I would have laughed at you.
I remember dial-up, back in the day when it was unlimited time for a single call, although that didn't often last long as parents or other household humans would often interrupt my bbs activities.

I did get to go to UCT labs every now and then to visit friends with access, and marvel at the amazing speeds, as we'd get them to download stuff, and copy off their network.

uucp and newsgroups :)
 

Vorastra

Honorary Master
Joined
Jan 13, 2013
Messages
14,117
Hurricane Electric
core1.cpt1.he.net> traceroute 172.107.96.75 source 216.218.252.112 | 149.134ms
core1.jnb1.he.net> traceroute 172.107.96.75 source 216.218.252.236 | 157ms
core1.dur1.he.net> traceroute 172.107.96.75 source 216.218.252.103 | 164.457ms

Web Squad
[capetown.lg.as328137.net] trace to 172.107.96.75 | 144ms
[durban.lg.as328137.net] trace to 172.107.96.75 | 202.5ms
[joburg.lg.as328137.net] trace to 172.107.96.75 | 194.8ms

Vodacom
ZAF West Coast Cape Town [AS 36994] | 140ms
ZAF Central Midrand [AS 36994] | 158ms


No one? My trace routes must be a hoax.
Sweet PoP-to-Pop traces again. It's a good thing we're talking about intra-ZA consumer routing and peering though.

Sweet Durban ping on Web Squad. What's going on there.
Vodacom users don't get even close to that real world. Interesting.

Explain to me why consumer grade is not getting this ping?

Edited to be nice.
 
Last edited:

Vorastra

Honorary Master
Joined
Jan 13, 2013
Messages
14,117
I remember dial-up, back in the day when it was unlimited time for a single call, although that didn't often last long as parents or other household humans would often interrupt my bbs activities.

I did get to go to UCT labs every now and then to visit friends with access, and marvel at the amazing speeds, as we'd get them to download stuff, and copy off their network.

uucp and newsgroups :)
*scrambled screeching noises*
Not gonna lie, kinda liked it.
 

Vorastra

Honorary Master
Joined
Jan 13, 2013
Messages
14,117
@DA-LION-619 There's at least some light at the end of the tunnel. My route to London via CogentCo is pretty good it seems.

Code:
Target Name: gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com
         IP: 130.117.254.57
  Date/Time: 2021/10/09 06:43:37 - 2021/10/09 06:53:37

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1     2    0    0.40    0.43    0.42  192.168.1.1 [192.168.1.1]
  2     2  100       0       0       0   [-]
  3     2    0    1.41    1.59    1.50  ethernet8-100.terdbn-igw1.net.echosp.link [102.67.179.3]
  4     2    0    1.90    2.54    2.22  100.127.4.210 [100.127.4.210]
  5     2    0    1.88    1.90    1.89  102.67.179.62 [102.67.179.62]
  6     2    0    3.39    3.43    3.41  ntrce-os-cer-1-wan.osnet.co.za [196.25.134.29]
  7     2    0  161.69  162.19  161.94  10.189.30.2 [10.189.30.2]
  8     2    0  163.17  163.20  163.18  be5956.rcr21.b023101-0.lon13.atlas.cogentco.com [149.11.248.209]
  9     2    0  164.67  165.62  165.14  be2350.ccr42.lon13.atlas.cogentco.com [130.117.51.137]
10     2    0  163.12  163.51  163.31  te0-0-2-2.agr11.lon13.atlas.cogentco.com [154.54.39.22]
11     2    0  163.67  163.89  163.78  gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com [130.117.254.57]

Now this has confused me.

~160ms to London is possible on my connection, yet still not in general reality.
It's possible but not the norm. :unsure:

The funny part is that Seacom LG Mtunzini (close to the Seacom cable break) to Cogent London is 188ms.
Well that blows the "lol it's because you're not on Seacom" comment away...again.

Again, this is down to garbage routing as per my point.
These low pings are possible, yet not accessible to normal people as a whole.

160ms to London should be the norm we (in Durban) should all expect and yet...
 
Last edited:

DA-LION-619

Honorary Master
Joined
Aug 22, 2009
Messages
13,777
Sweet PoP-to-Pop traces again. It's a good thing we're talking about intra-ZA consumer routing and peering though.

Sweet Durban ping on Web Squad. What's going on there.
Vodacom users don't get even close to that real world. Interesting.

Explain to me why consumer grade is not getting this ping?

Edited to be nice.
It was those with a network looking glass.
Similar to how you have a FON but you pay your ISP and they sort things out behind the scenes just on a different scale, your traffic gets to the exchange then decisions have to be made.
I'm not saying ISPs aren't blameless, some can be useless like RSAWEB.
Others can be really good like CoolIdeas, but do you pay to get your international traffic to the UK or just peer with AWS locally and let them handle the transit?

@DA-LION-619 There's at least some light at the end of the tunnel. My route to London via CogentCo is pretty good it seems.

Now this has confused me.

~160ms to London is possible on my connection, yet still not in general reality.
It's possible but not the norm. :unsure:

The funny part is that Seacom LG Mtunzini (close to the Seacom cable break) to Cogent London is 188ms.
Well that blows the "lol it's because you're not on Seacom" comment away...again.
Not really, look at your trace, it's via SAIX.

Not all networks peer, like Cogent and Hurricane Electric also that the path taken for a ping request doesn't mean that's the same path for the reply.
Then there's the cloud providers with their private networks, not forgetting Orange's ACE network.
Again, this is down to garbage routing as per my point.
These low pings are possible, yet not accessible to normal people as a whole.

160ms to London should be the norm we (in Durban) should all expect and yet...
Like @ToxicBunny mentioned, latency doesn't tell the whole story and is application dependent.
Do you want lower latency and more packet loss?
I personally use Cloudflare's WARP VPN as they have nodes in all the Teraco DCs, of which Durban is the smallest.

RSAWEB
Tracing route to gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com [130.117.254.57]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 5 ms 4 ms 4 ms 165.0.61.1
3 5 ms 5 ms 5 ms v-2183.core01.trc.jhb.rsaweb.net [165.0.40.169]
4 21 ms 21 ms 21 ms v-74.core-01.trc.cpt.rsaweb.net [41.71.70.121]
5 21 ms 21 ms 21 ms 196.250.236.22
6 161 ms 160 ms 160 ms 154.66.247.185
7 160 ms 161 ms 161 ms 154.66.247.148
8 161 ms 160 ms 160 ms 154.66.247.71
9 161 ms 160 ms 160 ms hundredgige0-4-0-28.lontr5.london.opentransit.net [193.251.141.13]
10 * * * Request timed out.
11 161 ms 160 ms 161 ms be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
12 161 ms 160 ms 161 ms te0-0-2-2.agr11.lon13.atlas.cogentco.com [154.54.39.22]
13 161 ms 161 ms 161 ms gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com [130.117.254.57]
CF
Tracing route to gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com [130.117.254.57]
over a maximum of 30 hops:

1 4 ms 5 ms 4 ms 172.16.0.1
2 7 ms 7 ms 5 ms 197.234.241.1
3 5 ms 5 ms 5 ms be6296.ccr51.jnb01.atlas.cogentco.com [206.249.0.209]
4 161 ms 161 ms 161 ms be2436.ccr21.lon02.atlas.cogentco.com [130.117.0.89]
5 161 ms 160 ms 161 ms be2573.ccr42.lon13.atlas.cogentco.com [154.54.62.5]
6 162 ms 161 ms 162 ms te0-0-2-2.agr12.lon13.atlas.cogentco.com [154.54.39.26]
7 164 ms 161 ms 161 ms gi0-0-1-15.7.nr12.b025687-0.lon13.atlas.cogentco.com [130.117.254.57]
 

Cage Rattler

Senior Member
Joined
Nov 29, 2005
Messages
789
Ex St Helena Independent .. On Tuesday noon time the cable ship tasked with laying the Equiano cable surprisingly aborted its mission and ferried to Walvis Bay shortly before entering the South African Exclusive Economic Zone. ... While weather conditions are a plausible explanation for the abortion it suspiciously happened just 4 nautical miles from the maritime boundary of the South African exclusive economic zone (EEZ), a seam of 200 nautical miles extending from the world’s coastlines. ...For the time being the Equiano cable system which now consists of a trunk of 3600km on top of the 1150km long branch to St Helena has still not made landfall outside of St Helena. 1635185429951.png
 
Top