DrJohnZoidberg
Honorary Master
Also, I cannot get to telkom.co.za from my Rocketnet account - works fine with my Vox ADSL and my mobile 4G. Any ideas?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Octotel?
Tracing route to sp1.interworks.in [160.19.114.66]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
2 1 ms 1 ms <1 ms 196-10-140-82.ixp.capetown [196.10.140.82]
3 1 ms 1 ms 1 ms s1-b1.interworks.in [160.19.112.38]
4 1 ms 1 ms 1 ms 160.19.114.66
Trace complete.
where u based? my 100mbps vuma is flying like a bat out of hell.
Definitely an issue with your connection. Here is speed test to the same server taken on phone over wifi also 100/100 Vumatel AE directelonc again only a 1/4 of line speed
Definitely an issue with your connection. Here is speed test to the same server taken on phone over wifi also 100/100 Vumatel AE directel
onc again only a 1/4 of line speed
it's a metro fibre issue.. had the same on cool ideas.. but rocketnet is slightly better
having said that my line is currently down![]()
Anyone in Cape Town with RocketNet on Octotel by any chance? Having trouble this evening - Netflix not working, along with some other website. Local speedtests are zipping along ok, except to Telkom, so not sure where the problem isCan anyone help?
traceroute to capetown.spdtst.saix.net (196.25.37.14), 64 hops max, 52 byte packets
1 45-222-25-1.pool.rocketnet.co.za (45.222.25.1) 2.585 ms 3.253 ms 2.621 ms
2 197.157.79.78 (197.157.79.78) 5.273 ms 3.132 ms 4.600 ms
3 * * *
4 agr2-gwf-cr2-gi0-0-1.wolcomm.net (197.157.77.7) 3.270 ms 2.614 ms 2.309 ms
5 196-10-140-228.ixp.capetown (196.10.140.228) 127.285 ms 125.798 ms 123.598 ms
6 196.43.39.58 (196.43.39.58) 110.843 ms 105.284 ms 110.013 ms
7 196.25.37.2 (196.25.37.2) 122.379 ms !X * 106.709 ms !X
Yep, there is something seriously wrong with the routing there, same on my side.
I've had it before where Telkom simply didn't work from my Rockenet account (reported a bit earlier in this thread).
Evening DrJohnZoidberg, thank you for bringing this to our attention. Apologies for the inconvenience. I can confirm that this has been passed on to our core engineers to investigate. Will revert back with feedback. Thank you.Yep, there is something seriously wrong with the routing there, same on my side.
I've had it before where Telkom simply didn't work from my Rockenet account (reported a bit earlier in this thread).
Code:traceroute to capetown.spdtst.saix.net (196.25.37.14), 64 hops max, 52 byte packets 1 45-222-25-1.pool.rocketnet.co.za (45.222.25.1) 2.585 ms 3.253 ms 2.621 ms 2 197.157.79.78 (197.157.79.78) 5.273 ms 3.132 ms 4.600 ms 3 * * * 4 agr2-gwf-cr2-gi0-0-1.wolcomm.net (197.157.77.7) 3.270 ms 2.614 ms 2.309 ms 5 196-10-140-228.ixp.capetown (196.10.140.228) 127.285 ms 125.798 ms 123.598 ms 6 196.43.39.58 (196.43.39.58) 110.843 ms 105.284 ms 110.013 ms 7 196.25.37.2 (196.25.37.2) 122.379 ms !X * 106.709 ms !X
@RocketNet-Rep Can you investigate what's going on here?
Hi Dames, thank you for letting us know about this. I can confirm that this as been assigned to our core engineers to investigate. Will revert back with feedback. Thank you.Ok - glad to know it’s not just me. Hopefully @RocketNet-Rep can assist!
Hi Dames, I can confirm that our core engineers are ivestigating this and we will revert with feedback.Anyone in Cape Town with RocketNet on Octotel by any chance? Having trouble this evening - Netflix not working, along with some other website. Local speedtests are zipping along ok, except to Telkom, so not sure where the problem isCan anyone help?
https://www.speedtest.net/result/8178603080 (Good result)
https://www.speedtest.net/result/8178611538 (Horrible result)
Tracing route to www.us-west-2.prodaa.netflix.com [34.209.185.102]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.0.1
2 3 ms 1 ms 2 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 3 ms 3 ms 7 ms 197.157.79.78
4 * * * Request timed out.
5 2 ms 2 ms 2 ms agr2-gwf-cr2-gi0-0-1.wolcomm.net [197.157.77.7]
6 * * * Request timed out.
7 * * * Request timed out.
8 144 ms 144 ms 144 ms 197.157.77.131
9 144 ms 144 ms 168 ms xe-4-1-0.edge6.london1.level3.net [212.187.165.245]
10 278 ms 278 ms 278 ms ae-0-11.bar1.sanfrancisco1.level3.net [4.69.140.145]
11 286 ms 281 ms 281 ms 4.35.164.86
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
Tracing route to www.google.com [216.58.223.36]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 1 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 54 ms 50 ms * jhb-io-ter-ibr-1.directel.co.za [169.255.0.225]
4 66 ms 58 ms 57 ms google.ixp.joburg [196.60.8.166]
5 * 55 ms 55 ms 72.14.239.129
6 52 ms 51 ms 50 ms jnb01s08-in-f36.1e100.net [216.58.223.36]
Trace complete.
Tracing route to www.telkom.co.za [165.143.151.47]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 3 ms 2 ms 3 ms 197.157.79.78
4 * * * Request timed out.
5 22 ms 2 ms 2 ms agr2-gwf-cr2-gi0-0-1.wolcomm.net [197.157.77.7]
6 412 ms 88 ms 87 ms 196-10-140-228.ixp.capetown [196.10.140.228]
7 72 ms 80 ms 90 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
8 77 ms 79 ms 75 ms telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]
9 81 ms 84 ms * gis.telkom.co.za [165.143.151.47]
10 87 ms 86 ms 71 ms gis.telkom.co.za [165.143.151.47]
Trace complete.
Hi Dames, please can we ask that you in the mean while our core engineers resolve this issue, please use local DNS and local Netflix please. Thank youAnyone in Cape Town with RocketNet on Octotel by any chance? Having trouble this evening - Netflix not working, along with some other website. Local speedtests are zipping along ok, except to Telkom, so not sure where the problem isCan anyone help?
https://www.speedtest.net/result/8178603080 (Good result)
https://www.speedtest.net/result/8178611538 (Horrible result)
Tracing route to www.us-west-2.prodaa.netflix.com [34.209.185.102]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.0.1
2 3 ms 1 ms 2 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 3 ms 3 ms 7 ms 197.157.79.78
4 * * * Request timed out.
5 2 ms 2 ms 2 ms agr2-gwf-cr2-gi0-0-1.wolcomm.net [197.157.77.7]
6 * * * Request timed out.
7 * * * Request timed out.
8 144 ms 144 ms 144 ms 197.157.77.131
9 144 ms 144 ms 168 ms xe-4-1-0.edge6.london1.level3.net [212.187.165.245]
10 278 ms 278 ms 278 ms ae-0-11.bar1.sanfrancisco1.level3.net [4.69.140.145]
11 286 ms 281 ms 281 ms 4.35.164.86
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
Tracing route to www.google.com [216.58.223.36]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 1 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 54 ms 50 ms * jhb-io-ter-ibr-1.directel.co.za [169.255.0.225]
4 66 ms 58 ms 57 ms google.ixp.joburg [196.60.8.166]
5 * 55 ms 55 ms 72.14.239.129
6 52 ms 51 ms 50 ms jnb01s08-in-f36.1e100.net [216.58.223.36]
Trace complete.
Tracing route to www.telkom.co.za [165.143.151.47]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 45-222-25-1.pool.rocketnet.co.za [45.222.25.1]
3 3 ms 2 ms 3 ms 197.157.79.78
4 * * * Request timed out.
5 22 ms 2 ms 2 ms agr2-gwf-cr2-gi0-0-1.wolcomm.net [197.157.77.7]
6 412 ms 88 ms 87 ms 196-10-140-228.ixp.capetown [196.10.140.228]
7 72 ms 80 ms 90 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
8 77 ms 79 ms 75 ms telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]
9 81 ms 84 ms * gis.telkom.co.za [165.143.151.47]
10 87 ms 86 ms 71 ms gis.telkom.co.za [165.143.151.47]
Trace complete.