Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
As is par for the course. Android updates not possible. Been 5 minutes to download 800Kb

Tonight actually worse than before when it comes to latency.
Code:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    10 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4     8 ms     7 ms     9 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    41 ms    43 ms    45 ms  optinet.ixp.capetown [196.10.140.145] 
  6   101 ms   100 ms   218 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  7     8 ms     8 ms     8 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8    54 ms    52 ms    53 ms  196.28.178.66 
  9    58 ms    30 ms    17 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    64 ms    62 ms    62 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Bras fine
Code:
 Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     7 ms     6 ms     6 ms  155.239.255.250 

Trace complete.

this is me to Mweb


C:\Users\Dell>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 6 ms 6 ms 192.168.1.1
2 * * * Request timed out.
3 44 ms 27 ms 16 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 22 ms 30 ms 14 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 11 ms 10 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 11 ms 10 ms optinet.ixp.capetown [196.10.140.145]
7 14 ms 14 ms 13 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
8 16 ms 16 ms 14 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 63 ms 34 ms 27 ms 196.28.178.66
10 51 ms 26 ms 24 ms cte-core-sw2.vwol.net [196.41.144.35]
11 82 ms 37 ms 27 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Dell>
 
Tracing route to www.google.com [216.58.223.36]
over a maximum of 30 hops:

1 3 ms 9 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 24 ms 15 ms 13 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 16 ms 14 ms 14 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 28 ms 38 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 24 ms 14 ms 14 ms 41.164.52.40
7 83 ms 32 ms 31 ms 172.18.1.162
8 38 ms 38 ms 38 ms 72.14.194.206
9 33 ms 46 ms 47 ms 72.14.239.129
10 32 ms 51 ms 44 ms jnb01s08-in-f4.1e100.net [216.58.223.36]

Trace complete.

C:\Users\Dell>tracert www.twitch.com

Tracing route to redirect.comlaude.com [213.212.81.71]
over a maximum of 30 hops:

1 8 ms 3 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 15 ms 12 ms 13 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 17 ms 10 ms 10 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 11 ms 10 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 10 ms 10 ms 11 ms 41.164.52.40
7 11 ms 10 ms 10 ms if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
8 160 ms 159 ms 196 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
9 206 ms 203 ms 201 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
10 168 ms 207 ms 169 ms if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 169 ms 168 ms 228 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 169 ms * 163 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 161 ms 161 ms 160 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 164 ms 164 ms 165 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 166 ms 166 ms 165 ms be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
16 176 ms 169 ms 177 ms te0-0-2-0.agr11.lon01.atlas.cogentco.com [154.54.39.94]
17 170 ms 168 ms 168 ms te0-0-2-0.nr11.b015774-1.lon01.atlas.cogentco.com [154.25.1.142]
18 162 ms 161 ms 161 ms 149.11.142.246
19 163 ms 163 ms 166 ms houir4-xe-2-1-0-0.sgns.net [62.73.137.137]
20 157 ms 160 ms 157 ms redirect.comlaude.com [213.212.81.71]
21 157 ms 158 ms 158 ms redirect.comlaude.com [213.212.81.71]

Trace complete.

C:\Users\Dell>
 
My internet is back! Let the chaos begin...


Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 13 ms 4 ms 3 ms 192.168.2.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * 96 ms 93 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
5 * 36 ms 28 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 109 ms 97 ms 90 ms mweb.ixp.joburg [196.46.25.145]
7 * 52 ms 51 ms te0-0-0-3.vic-p-1.optinet.net [197.80.7.65]
8 * 102 ms 102 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
9 * 50 ms 49 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 49 ms 51 ms 49 ms 196.28.178.66
11 * 128 ms 121 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

12 112 ms 106 ms 99 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 72 ms 63 ms 62 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
14 48 ms 49 ms 48 ms 41-86-110-200.mweb.co.za [41.86.110.200]

Trace complete.


Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 4 ms 4 ms 3 ms 192.168.2.1
2 * * * Request timed out.
3 * * * Request timed out.
4 34 ms 31 ms 33 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 28 ms 27 ms 29 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 64 ms 69 ms 77 ms mweb.ixp.joburg [196.46.25.145]
7 50 ms 51 ms 51 ms te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
8 * 51 ms 51 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
9 48 ms 48 ms 49 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 51 ms 50 ms 48 ms 196.28.178.66
11 51 ms 49 ms 49 ms cte-core-sw2.vwol.net [196.41.144.35]
12 50 ms 49 ms 50 ms www.mweb.co.za [196.2.63.110]

Trace complete.


And then my local TeamSpeak 3 server, I usually get 30-40ms on it;


Tracing route to 154.127.60.101 over a maximum of 30 hops

1 4 ms 6 ms 4 ms 192.168.2.1
2 * * * Request timed out.
3 * 88 ms 87 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 34 ms 38 ms 39 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 32 ms 29 ms 27 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 26 ms 28 ms 27 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 29 ms 28 ms 29 ms 41.169.57.216
8 * 107 ms 98 ms is.jinx.net.za [196.223.14.10]
9 29 ms 29 ms 28 ms csw5-pkl-tg2-7.ip.isnet.net [168.209.1.188]
10 * * * Request timed out.
11 * 64 ms 59 ms za-node3.host1plus.com [154.70.152.52]
12 29 ms 28 ms 29 ms 154.127.60.101

Trace complete.
 
And then Twitch...

Tracing route to redirect.comlaude.com [213.212.81.71]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms 192.168.2.1
2 * * * Request timed out.
3 * * * Request timed out.
4 88 ms 83 ms 80 ms jhb-in2.ip.adsl.co.za [169.1.5.30]
5 28 ms 29 ms 28 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 * 107 ms 108 ms he.ixp.joburg [196.46.25.42]
7 261 ms 274 ms 254 ms 10ge3-11.core1.lon2.he.net [184.105.81.253]
8 * 191 ms 198 ms 10ge8-4.core1.lon1.he.net [72.52.92.221]
9 * * * Request timed out.
10 * 196 ms 190 ms 31.13.159.74
11 * 203 ms 190 ms houir4-xe-2-1-1-0.sgns.net [62.73.137.145]
12 * 191 ms 191 ms redirect.comlaude.com [213.212.81.71]
13 192 ms 192 ms 193 ms redirect.comlaude.com [213.212.81.71]

Trace complete.
 
AH have a CDN?

a1b970b322.png
 
Afriguy please can we have some feedback? I am now seriously cancelling all my services with Afrihost.

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 20 ms 19 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 21 ms 19 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 20 ms 18 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 19 ms optinet.ixp.durban [196.10.141.75]
7 * 1462 ms 433 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
8 * 2143 ms 2312 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
9 * 2955 ms 2377 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
10 222 ms 132 ms 140 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 * * 621 ms 196.28.178.66
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

This is now unacceptable.

We will be getting an update later today, the moment we hear from the guys working on this we'll let you know.
 
World of warships. Also see prev post for tracert local teamspeak 3 server. I'm at work so can't do tests now

The latency to the World of Warships should be hovering around 220ms usually. Is there a specific time of day or night when the latency worsens?
 
A whole month has passed, and we are still awaiting an update. This is really unacceptable.

The lack of an update from us does not mean that the Team has stopped working on this issue. There are multiple upstream providers working to figure out what is going on, they unfortunately keep us updated on every single step in the processes that they are using.

When I have a clear update with information to share, I will definitely share that information.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X