Web Squad ISP

Status
Not open for further replies.
websquadza said:
Looked into this. Twofold there, 1 the subnet is advertised in all 3 regions. 2, it seems Amazon is preferring our JHB peering session over CPT.. We're going to play around with the path lengths a tad to try steer CPT prefixes via the CPT peering session. Here's a traceroute to EC2 hosted in Ireland from speedtest.cpt:

Code: 
traceroute to 54.194.77.13 (54.194.77.13), 30 hops max, 60 byte packets
1  core.as-01.cp1.za.ws.net.za (160.119.233.121)  0.187 ms  0.179 ms  0.164 ms
2  core.cr-01.cp1.za.ws.net.za (160.119.233.189)  0.256 ms  0.197 ms  0.185 ms
3  ixp-xe-4000.pe-ix01.cp1.za.ws.net.za (160.119.232.20)  0.228 ms  0.282 ms  0.214 ms
4  196-10-140-110.ixp.capetown (196.10.140.110)  0.430 ms  0.467 ms  0.410 ms << Out Via Amazon CPT
5  52.93.57.10 (52.93.57.10)  19.791 ms 52.93.57.42 (52.93.57.42)  21.383 ms 52.93.57.74 (52.93.57.74)  19.142 ms
6  52.93.57.23 (52.93.57.23)  22.981 ms 52.93.57.103 (52.93.57.103)  22.698 ms 52.93.57.17 (52.93.57.17)  19.007 ms
7  54.239.46.81 (54.239.46.81)  171.348 ms 54.239.46.85 (54.239.46.85)  171.135 ms  173.295 ms
8  * * *
9  54.239.44.140 (54.239.44.140)  169.487 ms 54.239.44.146 (54.239.44.146)  170.260 ms  170.565 ms
10  * * *
11  52.93.6.180 (52.93.6.180)  199.160 ms 52.93.6.182 (52.93.6.182)  193.815 ms 52.93.6.160 (52.93.6.160)  184.844 ms
12  52.93.101.57 (52.93.101.57)  169.713 ms 52.93.101.37 (52.93.101.37)  169.830 ms 52.93.101.1 (52.93.101.1)  170.367 ms
13  52.93.101.56 (52.93.101.56)  206.639 ms 52.93.101.60 (52.93.101.60)  208.102 ms 52.93.101.26 (52.93.101.26)  204.014 ms
14  52.93.7.115 (52.93.7.115)  170.576 ms  170.564 ms 52.93.7.103 (52.93.7.103)  170.826 ms
15  * * *

Will update further and test to other CPT only prefixes.
Click to expand...

Just wondering if you managed to solve it? I know it can get complex especially with small prefixes so if I should be checking to another IP let me know.
 
Waylander said:
It doesn't cache them, but loads them via their CDN which is massive and covers nearly all exchanges in the world, which essentially means my 1000Mbps local download comes from their JHB CDN instead of my server in the US which would cap at 200Mbit less TCP overheads.
Click to expand...

i have been using seedboxes for about 5 years now
this is really interesting if i can download via our local CDN`s as this, as you say maxes your line
 
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datag
rams
[ 4] 0.00-10.01 sec 235 MBytes 197 Mbits/sec 0.056 ms 3835/176087 (2.2
%)
[ 4] Sent 176087 datagrams
[SUM] 0.0-10.0 sec 124 datagrams received out-of-order
CPU Utilization: local/receiver 33.4% (9.6%u/23.8%s), remote/sender 5.4% (0.8%u/
4.6%s)

iperf Done.
 
Since the issue was with me I changed to 100/10 package from 20/20 from 200/20 from 200/200 from 50/50.

Now I want to go back to 200/20 but shop.vuma won't let me. I guess there is a limit to how many times you can change.
 
wingnut771 said:
Since the issue was with me I changed to 100/10 package from 20/20 from 200/20 from 200/200 from 50/50.

Now I want to go back to 200/20 but shop.vuma won't let me. I guess there is a limit to how many times you can change.
Click to expand...

Will get this sorted for you asap!
 
Last week ping to Hong Kong was 230 if my eyes weren't deceiving me, now it's 330.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X