Fjorko

Senior Member
Joined
Jan 17, 2007
Messages
758
We are :)

To Fortaleza:

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

4 2 ms 2 ms 2 ms 154.0.3.114
5 24 ms 24 ms 24 ms 154.0.1.246
6 24 ms 31 ms 24 ms 154.0.4.162
7 23 ms 23 ms 25 ms 102.130.64.13
8 65 ms 57 ms 57 ms pe2-nc028.ang.sgn.as37468.angolacables.ao [197.149.151.194]
9 116 ms 116 ms 116 ms 170.238.232.145
10 124 ms 116 ms 124 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
11 115 ms 115 ms 117 ms 170.238.235.18
12 116 ms 116 ms 117 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
13 114 ms 114 ms 115 ms 192.168.128.38
14 230 ms 230 ms 230 ms 192.168.128.54
15 119 ms * 116 ms 138-36-0-38.texnet.net.br [138.36.0.38]
16 116 ms 116 ms 115 ms 138-36-3-214.texnet.net.br [138.36.3.214]
OK - I stand corrected then. So which traffic goes over the SACS cable ?
 

image132

Senior Member
Joined
Apr 3, 2010
Messages
748
Twitch is also buffering quite a bit for me on Octotel.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 107 | 107 | 0 | 0 | 0 | 0 |
| u6t-cust.coolideas.co.za - 0 | 107 | 107 | 0 | 0 | 3 | 1 |
| uwx-cust.coolideas.co.za - 0 | 107 | 107 | 0 | 0 | 3 | 1 |
| uoa-cust.coolideas.co.za - 0 | 107 | 107 | 140 | 142 | 320 | 141 |
| v1000.core1.lon3.he.net - 9 | 80 | 73 | 157 | 157 | 159 | 157 |
| 100ge14-1.core1.lon2.he.net - 0 | 107 | 107 | 157 | 169 | 396 | 166 |
| 100ge13-2.core1.nyc4.he.net - 0 | 107 | 107 | 225 | 227 | 424 | 226 |
| 100ge11-1.core1.nyc5.he.net - 0 | 107 | 107 | 225 | 227 | 424 | 226 |
| 10ge4-7.core2.sao1.he.net - 0 | 107 | 107 | 334 | 338 | 533 | 335 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
This is to live.twitch.tv

Got a bit of packet loss on one of the links and I'm not sure if its normal to be connecting to twitch from South America? I thought it would use EU servers.
 

Loppas

Well-Known Member
Joined
Dec 16, 2014
Messages
335
@PBCool

Any issue with the joburg to cpt link? Was playing counter strike this evening and even now i noticed its switching routes to joburg intermittently where it goes from 20ms to 30ms.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
5,012
@PBCool

Any issue with the joburg to cpt link? Was playing counter strike this evening and even now i noticed its switching routes to joburg intermittently where it goes from 20ms to 30ms.
Graphs for both paths and latencies are fine, did you manage an MTR by chance?
 

SpiderGear

Well-Known Member
Joined
Mar 8, 2010
Messages
258
We are :)

To Fortaleza:

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

4 2 ms 2 ms 2 ms 154.0.3.114
5 24 ms 24 ms 24 ms 154.0.1.246
6 24 ms 31 ms 24 ms 154.0.4.162
7 23 ms 23 ms 25 ms 102.130.64.13
8 65 ms 57 ms 57 ms pe2-nc028.ang.sgn.as37468.angolacables.ao [197.149.151.194]
9 116 ms 116 ms 116 ms 170.238.232.145
10 124 ms 116 ms 124 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
11 115 ms 115 ms 117 ms 170.238.235.18
12 116 ms 116 ms 117 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
13 114 ms 114 ms 115 ms 192.168.128.38
14 230 ms 230 ms 230 ms 192.168.128.54
15 119 ms * 116 ms 138-36-0-38.texnet.net.br [138.36.0.38]
16 116 ms 116 ms 115 ms 138-36-3-214.texnet.net.br [138.36.3.214]
My latency to the same IP is horrendous.

traceroute to 138.36.3.214 (138.36.3.214), 30 hops max, 60 byte packets
1 UniFiSecurityGateway4P (192.168.0.1) 0.481 ms 0.420 ms 0.386 ms
2 155.93.144.1 (155.93.144.1) 3.918 ms 4.297 ms 4.245 ms
3 uzm-cust.coolideas.co.za (154.0.5.2) 1.179 ms 154.0.2.133 (154.0.2.133) 1.182 ms uzm-cust.coolideas.co.za (154.0.5.2) 1.210 ms
4 154.0.5.152 (154.0.5.152) 1.727 ms 1.679 ms 1.693 ms
5 154.0.1.106 (154.0.1.106) 160.837 ms 154.0.4.250 (154.0.4.250) 160.780 ms 154.0.1.234 (154.0.1.234) 160.791 ms
6 195.66.226.95 (195.66.226.95) 163.242 ms 162.828 ms 163.002 ms
7 pe2-nce011.us.bca.as37468.angolacables.ao (170.238.232.45) 268.342 ms 170.238.232.41 (170.238.232.41) 268.259 ms 268.226 ms
8 pe2-nc022.br.ftz.as37468.angolacables.ao (170.238.232.38) 220.726 ms 220.705 ms 220.674 ms
9 pe1-nc014.br.ftz.as37468.angolacables.ao (170.238.232.97) 222.391 ms pe1-nc013.br.ftz.as37468.angolacables.ao (170.238.232.81) 220.284 ms pe2-nc021.br.ftz.as37468.angolacables.ao (170.238.232.34) 220.186 ms
10 170.238.235.18 (170.238.235.18) 222.251 ms 222.419 ms 222.385 ms
11 187.120.30.6.Cliente.primelinelatam.com.br (187.120.30.6) 220.221 ms 220.059 ms 220.028 ms
12 187.120.30.6.Cliente.primelinelatam.com.br (187.120.30.6) 220.244 ms 220.475 ms 192.168.128.38 (192.168.128.38) 222.346 ms
13 192.168.128.54 (192.168.128.54) 333.019 ms 332.704 ms 332.643 ms
14 138-36-0-38.texnet.net.br (138.36.0.38) 333.037 ms 332.736 ms 192.168.128.54 (192.168.128.54) 332.916 ms
15 138-36-0-38.texnet.net.br (138.36.0.38) 333.001 ms 332.980 ms 138-36-3-214.texnet.net.br (138.36.3.214) 222.877 ms
 

Fjorko

Senior Member
Joined
Jan 17, 2007
Messages
758
My latency to the same IP is horrendous.

traceroute to 138.36.3.214 (138.36.3.214), 30 hops max, 60 byte packets
1 UniFiSecurityGateway4P (192.168.0.1) 0.481 ms 0.420 ms 0.386 ms
2 155.93.144.1 (155.93.144.1) 3.918 ms 4.297 ms 4.245 ms
3 uzm-cust.coolideas.co.za (154.0.5.2) 1.179 ms 154.0.2.133 (154.0.2.133) 1.182 ms uzm-cust.coolideas.co.za (154.0.5.2) 1.210 ms
4 154.0.5.152 (154.0.5.152) 1.727 ms 1.679 ms 1.693 ms
5 154.0.1.106 (154.0.1.106) 160.837 ms 154.0.4.250 (154.0.4.250) 160.780 ms 154.0.1.234 (154.0.1.234) 160.791 ms
6 195.66.226.95 (195.66.226.95) 163.242 ms 162.828 ms 163.002 ms
7 pe2-nce011.us.bca.as37468.angolacables.ao (170.238.232.45) 268.342 ms 170.238.232.41 (170.238.232.41) 268.259 ms 268.226 ms
8 pe2-nc022.br.ftz.as37468.angolacables.ao (170.238.232.38) 220.726 ms 220.705 ms 220.674 ms
9 pe1-nc014.br.ftz.as37468.angolacables.ao (170.238.232.97) 222.391 ms pe1-nc013.br.ftz.as37468.angolacables.ao (170.238.232.81) 220.284 ms pe2-nc021.br.ftz.as37468.angolacables.ao (170.238.232.34) 220.186 ms
10 170.238.235.18 (170.238.235.18) 222.251 ms 222.419 ms 222.385 ms
11 187.120.30.6.Cliente.primelinelatam.com.br (187.120.30.6) 220.221 ms 220.059 ms 220.028 ms
12 187.120.30.6.Cliente.primelinelatam.com.br (187.120.30.6) 220.244 ms 220.475 ms 192.168.128.38 (192.168.128.38) 222.346 ms
13 192.168.128.54 (192.168.128.54) 333.019 ms 332.704 ms 332.643 ms
14 138-36-0-38.texnet.net.br (138.36.0.38) 333.037 ms 332.736 ms 192.168.128.54 (192.168.128.54) 332.916 ms
15 138-36-0-38.texnet.net.br (138.36.0.38) 333.001 ms 332.980 ms 138-36-3-214.texnet.net.br (138.36.3.214) 222.877 ms
Same here...not as low as they advertised . . . .

traceroute to 138.36.3.214 (138.36.3.214), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.343 ms 0.148 ms 0.279 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 21.403 ms 18.944 ms 21.972 ms
4 192.168.11.6 (192.168.11.6) 20.445 ms 18.656 ms 21.209 ms
5 c4i-backbone.coolideas.co.za (154.0.1.162) 29.816 ms 27.184 ms 27.151 ms
6 uwu-cust.coolideas.co.za (154.0.4.158) 167.129 ms 167.280 ms 167.436 ms
7 195.66.226.95 (195.66.226.95) 160.752 ms 160.420 ms 158.512 ms
8 170.238.232.41 (170.238.232.41) 274.322 ms pe2-nce011.us.bca.as37468.angolacables.ao (170.238.232.45) 268.562 ms 170.238.232.41 (170.238.232.41) 271.271 ms
9 pe2-nc021.br.ftz.as37468.angolacables.ao (170.238.232.34) 240.776 ms pe2-nc022.br.ftz.as37468.angolacables.ao (170.238.232.38) 240.244 ms 240.430 ms
10 pe1-nc014.br.ftz.as37468.angolacables.ao (170.238.232.97) 245.951 ms 243.242 ms 243.681 ms
11 170.238.235.18 (170.238.235.18) 246.506 ms 244.402 ms 243.777 ms
12 187.120.30.6.cliente.primelinelatam.com.br (187.120.30.6) 241.284 ms 241.223 ms 239.274 ms
13 192.168.128.38 (192.168.128.38) 338.058 ms 336.153 ms 337.824 ms
14 192.168.128.54 (192.168.128.54) 244.449 ms 241.075 ms 238.492 ms
15 138-36-0-38.texnet.net.br (138.36.0.38) 251.498 ms 254.058 ms 247.295 ms
16 138-36-3-214.texnet.net.br (138.36.3.214) 338.047 ms 337.984 ms 337.182 ms
 

macedon

Well-Known Member
Joined
Dec 15, 2010
Messages
143
Don't be an idiot for a few hours worth of bad connectivity.
Marcell, sorry for pissing you off, I am not an idiot, this has becoming a weekly thing now that something will go wrong and internet speeds will go to 0... so I guess you are an idiot to spend R 1500 a month and get subpar connectivity... or perhaps you are even bigger idiot if you have so much money and waste it for a bad service...
 

Hype

Well-Known Member
Joined
Jan 31, 2005
Messages
124
Same here...not as low as they advertised . . . .

traceroute to 138.36.3.214 (138.36.3.214), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.343 ms 0.148 ms 0.279 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 21.403 ms 18.944 ms 21.972 ms
4 192.168.11.6 (192.168.11.6) 20.445 ms 18.656 ms 21.209 ms
5 c4i-backbone.coolideas.co.za (154.0.1.162) 29.816 ms 27.184 ms 27.151 ms
6 uwu-cust.coolideas.co.za (154.0.4.158) 167.129 ms 167.280 ms 167.436 ms
7 195.66.226.95 (195.66.226.95) 160.752 ms 160.420 ms 158.512 ms
8 170.238.232.41 (170.238.232.41) 274.322 ms pe2-nce011.us.bca.as37468.angolacables.ao (170.238.232.45) 268.562 ms 170.238.232.41 (170.238.232.41) 271.271 ms
9 pe2-nc021.br.ftz.as37468.angolacables.ao (170.238.232.34) 240.776 ms pe2-nc022.br.ftz.as37468.angolacables.ao (170.238.232.38) 240.244 ms 240.430 ms
10 pe1-nc014.br.ftz.as37468.angolacables.ao (170.238.232.97) 245.951 ms 243.242 ms 243.681 ms
11 170.238.235.18 (170.238.235.18) 246.506 ms 244.402 ms 243.777 ms
12 187.120.30.6.cliente.primelinelatam.com.br (187.120.30.6) 241.284 ms 241.223 ms 239.274 ms
13 192.168.128.38 (192.168.128.38) 338.058 ms 336.153 ms 337.824 ms
14 192.168.128.54 (192.168.128.54) 244.449 ms 241.075 ms 238.492 ms
15 138-36-0-38.texnet.net.br (138.36.0.38) 251.498 ms 254.058 ms 247.295 ms
16 138-36-3-214.texnet.net.br (138.36.3.214) 338.047 ms 337.984 ms 337.182 ms
Showing the same results here

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.2
2 <1 ms <1 ms <1 ms 192.168.1.1
3 2 ms 2 ms 2 ms 155.93.236.1
4 2 ms 2 ms 2 ms uyu-cust.coolideas.co.za [154.0.4.230]
5 1 ms <1 ms 1 ms uyp-cust.coolideas.co.za [154.0.4.225]
6 1 ms <1 ms <1 ms uya-cust.coolideas.co.za [154.0.4.210]
7 162 ms 162 ms 162 ms c6i-backbone.coolideas.co.za [154.0.1.234]
8 161 ms 161 ms 161 ms 195.66.226.95
9 219 ms 219 ms 219 ms 170.238.232.41
10 220 ms 219 ms 219 ms pe2-nc021.br.ftz.as37468.angolacables.ao [170.238.232.34]
11 221 ms 221 ms * pe1-nc014.br.ftz.as37468.angolacables.ao [170.238.232.97]
12 222 ms 222 ms 223 ms 170.238.235.18
13 222 ms 223 ms 222 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
14 220 ms 220 ms 220 ms 192.168.128.38
15 220 ms 220 ms 220 ms 192.168.128.54
16 219 ms 219 ms 219 ms 138.36.0.38
17 347 ms 348 ms 347 ms 138-36-3-214.texnet.net.br [138.36.3.214]

Trace complete.
 

Tinuva

The Magician
Joined
Feb 10, 2005
Messages
8,290
Marcell, sorry for pissing you off, I am not an idiot, this has becoming a weekly thing now that something will go wrong and internet speeds will go to 0... so I guess you are an idiot to spend R 1500 a month and get subpar connectivity... or perhaps you are even bigger idiot if you have so much money and waste it for a bad service...
No pain no gain.

That said, I guess there are better ways to implement new transit and peering paths.
But I also know, from experience, its not always as easy to do as it is to say it.

I do hope your weekly issues get sorted out, as I haven't had the same bad experience as you. Maybe I am lucky, but the services I use at least wasn't impacted by the temporary uptime on the SACS cable.
 

StoneCold

Expert Member
Joined
Jul 18, 2006
Messages
3,051
Showing the same results here

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.2
2 <1 ms <1 ms <1 ms 192.168.1.1
3 2 ms 2 ms 2 ms 155.93.236.1
4 2 ms 2 ms 2 ms uyu-cust.coolideas.co.za [154.0.4.230]
5 1 ms <1 ms 1 ms uyp-cust.coolideas.co.za [154.0.4.225]
6 1 ms <1 ms <1 ms uya-cust.coolideas.co.za [154.0.4.210]
7 162 ms 162 ms 162 ms c6i-backbone.coolideas.co.za [154.0.1.234]
8 161 ms 161 ms 161 ms 195.66.226.95
9 219 ms 219 ms 219 ms 170.238.232.41
10 220 ms 219 ms 219 ms pe2-nc021.br.ftz.as37468.angolacables.ao [170.238.232.34]
11 221 ms 221 ms * pe1-nc014.br.ftz.as37468.angolacables.ao [170.238.232.97]
12 222 ms 222 ms 223 ms 170.238.235.18
13 222 ms 223 ms 222 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
14 220 ms 220 ms 220 ms 192.168.128.38
15 220 ms 220 ms 220 ms 192.168.128.54
16 219 ms 219 ms 219 ms 138.36.0.38
17 347 ms 348 ms 347 ms 138-36-3-214.texnet.net.br [138.36.3.214]

Trace complete.
Perhaps it isn't implemented yet for us as customers? Maybe from 1 Nov only?
 

Joker

Expert Member
Joined
Aug 10, 2004
Messages
1,601
So Cool Ideas has multiple transit providers now:
HE, IS, eNetworks, Seacom, Liquid, WIOCC + SACS

How does it work internally - is the lowest latency route/provider automatically selected when connecting to intl servers?
 

Hype

Well-Known Member
Joined
Jan 31, 2005
Messages
124
Perhaps it isn't implemented yet for us as customers? Maybe from 1 Nov only?
Possibly or just tweaking the routing still.
My Afrihost link is showing this so its not all gloomy

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.2
2 <1 ms <1 ms <1 ms 192.168.1.1
3 1 ms <1 ms <1 ms 102-182-232-1.ip.afrihost.co.za [102.182.232.1]
4 2 ms 1 ms 1 ms 169-1-21-101.ip.afrihost.co.za [169.1.21.101]
5 1 ms 1 ms 1 ms 77.246.59.254.liquidtelecom.net [77.246.59.254]
6 157 ms 157 ms 157 ms hu-0-0-0-3.lza-p4-jhb.liquidtelecom.net [46.17.232.152]
7 158 ms 157 ms 157 ms xe-0-1-5-0.lfr-pe2-mrs.liquidtelecom.net [46.17.232.25]
8 174 ms 174 ms 174 ms core01.angolacables.co.ao [80.81.193.103]
9 182 ms 183 ms 182 ms pe1-nce012.uk.lon.as37468.angolacables.ao [185.148.112.85]
10 232 ms 232 ms 232 ms 170.238.232.41
11 237 ms 232 ms 232 ms pe2-nc021.br.ftz.as37468.angolacables.ao [170.238.232.34]
12 230 ms 230 ms 250 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
13 232 ms 232 ms 232 ms 170.238.235.18
14 232 ms 232 ms 232 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
15 232 ms 232 ms 232 ms 192.168.128.38
16 230 ms 230 ms 230 ms 192.168.128.54
17 348 ms 348 ms 348 ms 138-36-0-38.texnet.net.br [138.36.0.38]
18 349 ms 349 ms 349 ms 138-36-3-214.texnet.net.br [138.36.3.214]

Trace complete.
 
Top