Cool Ideas Fibre ISP – Feedback Thread 4

Status
Not open for further replies.

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
I checked steam settings, its set to unlimited. 224mbps is still slower than the speed i should be getting, it should be closer to 500mbps (+-60MB/s). View attachment 1438363


The speedtest on the FNO's speed test site is showing up as slower, 250 instead of 500. but general speedtest.net is showing 500+

View attachment 1438361 View attachment 1438369
Use the "Display download rates as bits per second option".

Yes, in theory you should get close to line speed, but steam does impose it's own rate limits on their CDN depending on capacity. It's not something we control.

If, using Resource Monitor -> Network tab, if you can find a host name or IP address of the connection with the highest TCP throughput during the download, I can check the route for you.
 

sewash14

Active Member
Joined
Aug 1, 2011
Messages
42
Use the "Display download rates as bits per second option".

Yes, in theory you should get close to line speed, but steam does impose it's own rate limits on their CDN depending on capacity. It's not something we control.

If, using Resource Monitor -> Network tab, if you can find a host name or IP address of the connection with the highest TCP throughput during the download, I can check the route for you.


Below is steam download and resource manager speeds. Kindly check the routes, thanks.
1670593700638.png 1670593840967.png
 

PBCool

Cool Ideas Rep
Company Rep
Joined
Jan 11, 2016
Messages
13,304

NR7

Senior Member
Joined
May 27, 2011
Messages
748
Nothing to do with routing on this one, I imagine it is a limitation with Steam.

If you look at the average speed:


Not on Steam side. You can see in an earlier post I was able to get 58MB/s on the same game download to the same jhb server and have no issues. Only difference was I am Openserve JHB and the other person with the slow speed is Vumatel Dbn.
 

CrypticZA

Expert Member
Joined
Sep 21, 2019
Messages
3,046
Can you guys like seriously fix CT to JHB every day now massive lag spike and then i get 308ms ping in Dota 2 and its only traffic to JHB

Just happened like 5 minutes ago again
 

PBCool

Cool Ideas Rep
Company Rep
Joined
Jan 11, 2016
Messages
13,304
Not on Steam side. You can see in an earlier post I was able to get 58MB/s on the same game download to the same jhb server and have no issues. Only difference was I am Openserve JHB and the other person with the slow speed is Vumatel Dbn.

If the customer is in KZN and receiving content from Steam in JHB, the slight latency variation will have a play on the throughput.
 

PBCool

Cool Ideas Rep
Company Rep
Joined
Jan 11, 2016
Messages
13,304
Can you guys like seriously fix CT to JHB every day now massive lag spike and then i get 308ms ping in Dota 2 and its only traffic to JHB

Just happened like 5 minutes ago again
Sure checking
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
If the customer is in KZN and receiving content from Steam in JHB, the slight latency variation will have a play on the throughput.
Indeed, and also from the resource monitor steam seems to be using only two connections, which with the increased latency from KZN throughput will never be as good as a speedtest.net test which uses up to 10 connections at a time.

Here is a theoretical calculation of an 8ms bandwith delay product and a 17Mb window size for windows.

 
Last edited:

NR7

Senior Member
Joined
May 27, 2011
Messages
748
If the customer is in KZN and receiving content from Steam in JHB, the slight latency variation will have a play on the throughput.
Indeed, and also from the resource monitor steam seems to be using only two connections, which with the increased latency from KZN throughput will never be as good as a speedtest.net test which uses up to 10 connections at a time.

But we aren't talking about a slight latency variation, we're talking about customer A on a 500Mbps Vuma line in DBN getting 28MB/s, while customer B gets 58MB/s in JHB on Openserve 500Mbps. If it was a Steam connection issue, both would be low.

Im on coolideas 500/200mbps vuma fibre. My steam downloads from JHB OR CPT serverare maxing at +-30mbps (same for epic games laucher downloads).

View attachment 1438143

All fine for me. Openserve 500Mbps (this is over wifi too). JHB though.

zQ145bG.png
 

Jason-ZA

Senior Member
Joined
Sep 23, 2019
Messages
625
@TheRoDent The JHB iperf servers seem to be down:
ter-jhb-iperf-1.cisp.co.za
is-jhb-iperf-1.cisp.co.za

Code:
iperf3 -R -u -b 10M -O2 -t 30 -p 17001 -c ter-jhb-iperf-1.cisp.co.za
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
iperf3: interrupt - the client has terminated

iperf3 -R -u -b 10M -O2 -t 30 -p 17001 -c is-jhb-iperf-1.cisp.co.za
iperf3: error - unable to connect to server: Connection refused

Bump - @TheRoDent I think you might have missed this post :)
 

Jason-ZA

Senior Member
Joined
Sep 23, 2019
Messages
625
I think there may be some asymetrical routing going on atm, to blizzard.
Higher than usual latency to EU, the return path is whats odd, i think.

Not a big deal for me atm, just thought I would mention it.

Me to Blizzard:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -    0 |   22 |   22 |    0 |    0 |    1 |    0 |
|                             154.0.0.242 -    0 |   22 |   22 |   11 |   13 |   39 |   12 |
|                              100.98.0.3 -    0 |   22 |   22 |   11 |   13 |   40 |   12 |
|                            100.99.0.126 -    0 |   21 |   21 |  151 |  151 |  152 |  151 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                             62.115.9.28 -    0 |   21 |   21 |  181 |  185 |  208 |  181 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           62.115.134.26 -    0 |   21 |   21 |  187 |  189 |  221 |  188 |
|                          62.115.120.229 -    0 |   21 |   21 |  173 |  174 |  192 |  174 |
|                          62.115.178.203 -    0 |   21 |   21 |  182 |  186 |  222 |  190 |
|                           137.221.78.33 -    0 |    9 |    9 |  219 | 1059 | 3819 |  266 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           137.221.78.57 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|                           137.221.66.43 -    0 |   21 |   21 |  192 |  194 |  223 |  192 |
|                          185.60.112.157 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Blizzard to Me:
Code:
TRACEROUTE:
traceroute to 102.132.213.xxx (102.132.213.xxx), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.677 ms  2.287 ms  2.919 ms
 2  * * *
 3  137.221.66.46 (137.221.66.46)  0.371 ms  0.379 ms  0.385 ms
 4  137.221.78.52 (137.221.78.52)  99.428 ms  315.556 ms  315.572 ms
 5  137.221.65.74 (137.221.65.74)  14.703 ms  14.753 ms  14.756 ms
 6  137.221.65.28 (137.221.65.28)  6.275 ms  6.001 ms  5.985 ms
 7  137.221.80.32 (137.221.80.32)  6.236 ms  7.524 ms  7.496 ms
 8  ae114-0.ffttr6.frankfurt.opentransit.net (81.52.179.221)  6.125 ms  6.205 ms  6.205 ms
 9  193.251.241.143 (193.251.241.143)  186.851 ms  186.879 ms  187.989 ms
10  193.251.250.170 (193.251.250.170)  191.123 ms  191.139 ms  191.334 ms
11  168.209.1.201 (168.209.1.201)  191.712 ms  191.731 ms  190.750 ms
12  za-gp-pkl-p-2-be-212.ip.ddii.network (168.209.129.146)  191.906 ms  191.931 ms  191.936 ms
13  za-gp-tis-p-2-hu-0-0-1-4.ip.ddii.network (168.209.90.19)  181.182 ms  181.515 ms  181.392 ms
14  168.209.132.137 (168.209.132.137)  182.509 ms  182.443 ms  181.994 ms
15  197.103.32.149 (197.103.32.149)  190.417 ms  190.303 ms  190.131 ms

- Blizzard caps the trace at 15 hops max.
 

grantduke

Senior Member
Joined
Mar 12, 2011
Messages
713
Code:
traceroute speedtest.mybroadband.co.za
traceroute to speedtest.mybroadband.co.za (196.10.98.18), 64 hops max, 52 byte packets
 1  192.168.5.1 (192.168.5.1)  2.401 ms  3.684 ms  2.498 ms
 2  u6m-cust.coolideas.co.za (154.0.0.238)  4.951 ms  4.431 ms  3.437 ms
 3  100.98.0.1 (100.98.0.1)  3.668 ms  4.316 ms  4.604 ms
 4  100.98.0.12 (100.98.0.12)  4.514 ms  4.749 ms  5.710 ms
 5  vox.ixp.capetown (196.60.70.69)  4.689 ms  4.804 ms  5.838 ms
 6  41-193-120-2.vox.co.za (41.193.120.2)  6.748 ms  6.725 ms  5.264 ms
 7  41-193-118-5.vox.co.za (41.193.118.5)  23.876 ms  30.701 ms  23.124 ms
 8  41-193-119-34.vox.co.za (41.193.119.34)  23.104 ms  174.042 ms  25.693 ms
 9  teraco.ixp.joburg (196.60.8.200)  25.300 ms  24.364 ms  22.385 ms
10  196.10.98.18.teraco.co.za (196.10.98.18)  24.023 ms  23.460 ms  22.652 ms

This is a very weird routing via VOX in Cape Town and then off to Teraco in Joburg? @PBCool @TheRoDent Still fine tuning the routes?
 

AfricanTech

Honorary Master
Joined
Mar 19, 2010
Messages
40,369
Frogfoot 100/100 trenched

Pinelands, Cape Town

Internet down for most of the day.

ONT led 2 and 3 off.

Ticket ref: #COOL-20221209-1082610
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
I think there may be some asymetrical routing going on atm, to blizzard.
Higher than usual latency to EU, the return path is whats odd, i think.

Not a big deal for me atm, just thought I would mention it.

Me to Blizzard:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -    0 |   22 |   22 |    0 |    0 |    1 |    0 |
|                             154.0.0.242 -    0 |   22 |   22 |   11 |   13 |   39 |   12 |
|                              100.98.0.3 -    0 |   22 |   22 |   11 |   13 |   40 |   12 |
|                            100.99.0.126 -    0 |   21 |   21 |  151 |  151 |  152 |  151 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                             62.115.9.28 -    0 |   21 |   21 |  181 |  185 |  208 |  181 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           62.115.134.26 -    0 |   21 |   21 |  187 |  189 |  221 |  188 |
|                          62.115.120.229 -    0 |   21 |   21 |  173 |  174 |  192 |  174 |
|                          62.115.178.203 -    0 |   21 |   21 |  182 |  186 |  222 |  190 |
|                           137.221.78.33 -    0 |    9 |    9 |  219 | 1059 | 3819 |  266 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           137.221.78.57 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|                           137.221.66.43 -    0 |   21 |   21 |  192 |  194 |  223 |  192 |
|                          185.60.112.157 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Blizzard to Me:
Code:
TRACEROUTE:
traceroute to 102.132.213.xxx (102.132.213.xxx), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.677 ms  2.287 ms  2.919 ms
 2  * * *
 3  137.221.66.46 (137.221.66.46)  0.371 ms  0.379 ms  0.385 ms
 4  137.221.78.52 (137.221.78.52)  99.428 ms  315.556 ms  315.572 ms
 5  137.221.65.74 (137.221.65.74)  14.703 ms  14.753 ms  14.756 ms
 6  137.221.65.28 (137.221.65.28)  6.275 ms  6.001 ms  5.985 ms
 7  137.221.80.32 (137.221.80.32)  6.236 ms  7.524 ms  7.496 ms
 8  ae114-0.ffttr6.frankfurt.opentransit.net (81.52.179.221)  6.125 ms  6.205 ms  6.205 ms
 9  193.251.241.143 (193.251.241.143)  186.851 ms  186.879 ms  187.989 ms
10  193.251.250.170 (193.251.250.170)  191.123 ms  191.139 ms  191.334 ms
11  168.209.1.201 (168.209.1.201)  191.712 ms  191.731 ms  190.750 ms
12  za-gp-pkl-p-2-be-212.ip.ddii.network (168.209.129.146)  191.906 ms  191.931 ms  191.936 ms
13  za-gp-tis-p-2-hu-0-0-1-4.ip.ddii.network (168.209.90.19)  181.182 ms  181.515 ms  181.392 ms
14  168.209.132.137 (168.209.132.137)  182.509 ms  182.443 ms  181.994 ms
15  197.103.32.149 (197.103.32.149)  190.417 ms  190.303 ms  190.131 ms

- Blizzard caps the trace at 15 hops max.
Yep, we'll be refining these routes over the coming days.
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
But we aren't talking about a slight latency variation, we're talking about customer A on a 500Mbps Vuma line in DBN getting 28MB/s, while customer B gets 58MB/s in JHB on Openserve 500Mbps. If it was a Steam connection issue, both would be low.
Check the RTT calculations I updated my post with.

TCP peak throughput is affected directly by latency.


Even a 10ms difference can have a significant impact on TCP performance, depending on the receiver's buffer size.


@cavedog has some good posts about Windows TCP stack settings as well.

There is a 'netsh int tcp" command mentioned in this thread.

Also, no person's home network is the same, Wifi, cables etc.

So it's not really apples and apples.
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
Code:
traceroute speedtest.mybroadband.co.za
traceroute to speedtest.mybroadband.co.za (196.10.98.18), 64 hops max, 52 byte packets
 1  192.168.5.1 (192.168.5.1)  2.401 ms  3.684 ms  2.498 ms
 2  u6m-cust.coolideas.co.za (154.0.0.238)  4.951 ms  4.431 ms  3.437 ms
 3  100.98.0.1 (100.98.0.1)  3.668 ms  4.316 ms  4.604 ms
 4  100.98.0.12 (100.98.0.12)  4.514 ms  4.749 ms  5.710 ms
 5  vox.ixp.capetown (196.60.70.69)  4.689 ms  4.804 ms  5.838 ms
 6  41-193-120-2.vox.co.za (41.193.120.2)  6.748 ms  6.725 ms  5.264 ms
 7  41-193-118-5.vox.co.za (41.193.118.5)  23.876 ms  30.701 ms  23.124 ms
 8  41-193-119-34.vox.co.za (41.193.119.34)  23.104 ms  174.042 ms  25.693 ms
 9  teraco.ixp.joburg (196.60.8.200)  25.300 ms  24.364 ms  22.385 ms
10  196.10.98.18.teraco.co.za (196.10.98.18)  24.023 ms  23.460 ms  22.652 ms

This is a very weird routing via VOX in Cape Town and then off to Teraco in Joburg? @PBCool @TheRoDent Still fine tuning the routes?
Yes, indeed. We are limiting changes to early mornings now as we refine our BGP routes, so changes will happen over he next few days.

The feedback is appreciated however, as it allows us to investigate specific cases from you guys, so please keep it up.
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
6,218
I think there may be some asymetrical routing going on atm, to blizzard.
Higher than usual latency to EU, the return path is whats odd, i think.

Not a big deal for me atm, just thought I would mention it.

Me to Blizzard:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -    0 |   22 |   22 |    0 |    0 |    1 |    0 |
|                             154.0.0.242 -    0 |   22 |   22 |   11 |   13 |   39 |   12 |
|                              100.98.0.3 -    0 |   22 |   22 |   11 |   13 |   40 |   12 |
|                            100.99.0.126 -    0 |   21 |   21 |  151 |  151 |  152 |  151 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                             62.115.9.28 -    0 |   21 |   21 |  181 |  185 |  208 |  181 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           62.115.134.26 -    0 |   21 |   21 |  187 |  189 |  221 |  188 |
|                          62.115.120.229 -    0 |   21 |   21 |  173 |  174 |  192 |  174 |
|                          62.115.178.203 -    0 |   21 |   21 |  182 |  186 |  222 |  190 |
|                           137.221.78.33 -    0 |    9 |    9 |  219 | 1059 | 3819 |  266 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           137.221.78.57 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|                           137.221.66.43 -    0 |   21 |   21 |  192 |  194 |  223 |  192 |
|                          185.60.112.157 -    0 |   21 |   21 |  192 |  193 |  223 |  192 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Blizzard to Me:
Code:
TRACEROUTE:
traceroute to 102.132.213.xxx (102.132.213.xxx), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.677 ms  2.287 ms  2.919 ms
 2  * * *
 3  137.221.66.46 (137.221.66.46)  0.371 ms  0.379 ms  0.385 ms
 4  137.221.78.52 (137.221.78.52)  99.428 ms  315.556 ms  315.572 ms
 5  137.221.65.74 (137.221.65.74)  14.703 ms  14.753 ms  14.756 ms
 6  137.221.65.28 (137.221.65.28)  6.275 ms  6.001 ms  5.985 ms
 7  137.221.80.32 (137.221.80.32)  6.236 ms  7.524 ms  7.496 ms
 8  ae114-0.ffttr6.frankfurt.opentransit.net (81.52.179.221)  6.125 ms  6.205 ms  6.205 ms
 9  193.251.241.143 (193.251.241.143)  186.851 ms  186.879 ms  187.989 ms
10  193.251.250.170 (193.251.250.170)  191.123 ms  191.139 ms  191.334 ms
11  168.209.1.201 (168.209.1.201)  191.712 ms  191.731 ms  190.750 ms
12  za-gp-pkl-p-2-be-212.ip.ddii.network (168.209.129.146)  191.906 ms  191.931 ms  191.936 ms
13  za-gp-tis-p-2-hu-0-0-1-4.ip.ddii.network (168.209.90.19)  181.182 ms  181.515 ms  181.392 ms
14  168.209.132.137 (168.209.132.137)  182.509 ms  182.443 ms  181.994 ms
15  197.103.32.149 (197.103.32.149)  190.417 ms  190.303 ms  190.131 ms

- Blizzard caps the trace at 15 hops max.
We are bringing up direct blizzard paths during the coming days.

We have made major changes to our UK POP due to equipment moves, so some LINX traffix is preferring assymetrical paths at this point.
 
Status
Not open for further replies.
Top