Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Loads of packets being dropped @ the IPC for me still

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 32 ms 32 ms 45 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 34 ms 61 ms 53 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 33 ms 35 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * 33 ms * jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * 58 ms 41.181.180.10
7 50 ms 73 ms 40 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * 35 ms * 41.181.139.99
9 * 51 ms * 72.14.194.74
10 * * * Request timed out.
11 * * 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 33 ms 32 ms 34 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 35 ms * * jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * 35 ms 41 ms 72.14.194.74
10 * * * Request timed out.
11 * * * Request timed out.
12 * 51 ms 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 31 ms 34 ms 32 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * 35 ms 33 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 35 ms * * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 34 ms 63 ms 34 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 62 ms 71 ms 63 ms 41.181.180.10
7 36 ms 36 ms 37 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 36 ms 47 ms * 41.181.139.99
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 52 ms 55 ms 45 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 5 ms 192.168.1.254
2 35 ms 32 ms 31 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 36 ms 36 ms 33 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 47 ms * * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 37 ms 35 ms 33 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * 54 ms 41.181.180.10
7 * * * Request timed out.
8 42 ms * * 41.181.139.99
9 37 ms * * 72.14.194.74
10 * 41 ms 36 ms 72.14.239.129
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * 56 ms * jnb01s08-in-f3.1e100.net [216.58.223.35]
16 53 ms * * jnb01s08-in-f3.1e100.net [216.58.223.35]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 40 ms 39 ms 40 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 34 ms 32 ms 36 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * * * Request timed out.
4 61 ms 34 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * 98 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * * * Request timed out.
9 * 35 ms 36 ms 72.14.194.74
10 * 34 ms * 72.14.239.129
11 * 51 ms 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 34 ms 31 ms 32 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * 33 ms 35 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 36 ms 34 ms 35 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * 47 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * * * Request timed out.
9 * * 42 ms 72.14.194.74
10 290 ms 307 ms * 72.14.239.129
11 * * * Request timed out.
12 112 ms 63 ms 94 ms jnb01s08-in-f3.1e100.net [216.58.223.35]
 
Morning All

We are still seeing latency during the peak period in the evenings. Last night is seemed to start just after 8pm and then drop off just after 10pm. The technical team working on the network are monitoring this and doing what we can to manage the latency to give the best experience we can. We are considering all options in terms of improving overall performance in the South :(
 
What happened with Afrihost.

Afrihost business account trace route

Tracing route to www.movreel.com [89.46.103.114]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 145 ms 94 ms 127 ms 41.181.178.18
4 10 ms 10 ms 10 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178
.17]
5 10 ms 10 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 89 ms 58 ms 65 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
7 238 ms 260 ms 224 ms 41.181.180.10
8 207 ms 205 ms 205 ms ls-cr-2.uk--jh-cr-1.za.mtnns.net [196.44.31.114]

9 206 ms 205 ms 206 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
10 206 ms 236 ms 278 ms TenGigabitEthernet8-2.ar6.LON3.gblx.net [208.48.
238.185]
11 229 ms 252 ms 239 ms p1-0.globalcrossing.londen03.uk.bb.gin.ntt.net [
208.50.13.146]
12 208 ms 222 ms 207 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
13 209 ms 209 ms 236 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
14 238 ms 237 ms 234 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.5
4]
15 244 ms 244 ms 244 ms ae-3.r00.buchro01.ro.bb.gin.ntt.net [129.250.3.2
35]
16 248 ms 275 ms 242 ms te3-2-0-bb1.buc2.ro.m247.ro [83.217.231.82]
17 * * * Request timed out.
18 255 ms 254 ms 245 ms mx-pool114.intelicontacts.com [89.46.103.114]

Trace complete.

------------------

Web africa capped trace route

Tracing route to www.movreel.com [89.46.103.114]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 10 ms 10 ms cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]

4 10 ms 10 ms 10 ms 196.38.73.85
5 10 ms 10 ms 11 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 16 ms 14 ms 10 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]

7 178 ms 192 ms 176 ms 168.209.246.1
8 184 ms 186 ms 184 ms te0-7-0-1.ccr21.lon02.atlas.cogentco.com [149.6.
148.129]
9 177 ms 176 ms 176 ms be2329.ccr22.lon01.atlas.cogentco.com [130.117.4
9.89]
10 190 ms 185 ms 187 ms be2163.ccr41.lon13.atlas.cogentco.com [130.117.5
0.202]
11 193 ms 192 ms 192 ms be2194.ccr41.ams03.atlas.cogentco.com [130.117.5
0.242]
12 194 ms 192 ms 193 ms be2186.ccr41.ham01.atlas.cogentco.com [154.54.74
.122]
13 200 ms 201 ms 201 ms be2018.ccr21.prg01.atlas.cogentco.com [130.117.0
.158]
14 214 ms 213 ms 213 ms be2167.ccr22.bts01.atlas.cogentco.com [130.117.0
.185]
15 212 ms 212 ms 211 ms be2197.ccr21.bud01.atlas.cogentco.com [130.117.1
.98]
16 242 ms 238 ms 235 ms be2195.ccr21.buh01.atlas.cogentco.com [130.117.0
.198]
17 221 ms 220 ms 219 ms m247.demarc.cogentco.com [149.6.50.154]
18 * * * Request timed out.
19 222 ms 219 ms 222 ms mx-pool114.intelicontacts.com [89.46.103.114]

Trace complete.

-------------------

and then when I switched back to Afrihost business account

Tracing route to www.movreel.com [89.46.103.114]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 12 ms 11 ms 41.181.178.6
4 11 ms 9 ms 11 ms ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178
.5]
5 10 ms 9 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 10 ms 10 ms 9 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
7 208 ms 228 ms 207 ms 41.181.180.10
8 207 ms 207 ms 216 ms ls-cr-2.uk--jh-cr-1.za.mtnns.net [196.44.31.114]

9 206 ms 206 ms 205 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
10 188 ms 188 ms 188 ms TenGigabitEthernet8-2.ar6.LON3.gblx.net [208.48.
238.185]
11 207 ms 209 ms 207 ms p1-0.globalcrossing.londen03.uk.bb.gin.ntt.net [
208.50.13.146]
12 271 ms 208 ms 207 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
13 210 ms 214 ms 345 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
14 281 ms 306 ms 275 ms ae-2.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.2
17]
15 344 ms 244 ms 347 ms ae-4.r00.buchro01.ro.bb.gin.ntt.net [129.250.3.7
9]
16 248 ms 245 ms 245 ms te3-2-0-bb1.buc2.ro.m247.ro [83.217.231.82]
17 * * * Request timed out.
18 257 ms 255 ms 255 ms mx-pool114.intelicontacts.com [89.46.103.114]

Trace complete.

In the traces you sent me by PM I saw latency on both ISP accounts at the 3rd hop. This test also fits my suspicion that you line is degrading but improves after a port reset and then possibly degrades again. Explains why the second Afrihost test seems perfect again.

As far as I can tell latency in the East was stable at the time of your post.
 
Loads of packets being dropped @ the IPC for me still

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 32 ms 32 ms 45 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 34 ms 61 ms 53 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 33 ms 35 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * 33 ms * jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * 58 ms 41.181.180.10
7 50 ms 73 ms 40 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * 35 ms * 41.181.139.99
9 * 51 ms * 72.14.194.74
10 * * * Request timed out.
11 * * 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 33 ms 32 ms 34 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 35 ms * * jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * 35 ms 41 ms 72.14.194.74
10 * * * Request timed out.
11 * * * Request timed out.
12 * 51 ms 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 31 ms 34 ms 32 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * 35 ms 33 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 35 ms * * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 34 ms 63 ms 34 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 62 ms 71 ms 63 ms 41.181.180.10
7 36 ms 36 ms 37 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 36 ms 47 ms * 41.181.139.99
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 52 ms 55 ms 45 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 5 ms 192.168.1.254
2 35 ms 32 ms 31 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 36 ms 36 ms 33 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 47 ms * * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 37 ms 35 ms 33 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * * 54 ms 41.181.180.10
7 * * * Request timed out.
8 42 ms * * 41.181.139.99
9 37 ms * * 72.14.194.74
10 * 41 ms 36 ms 72.14.239.129
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * 56 ms * jnb01s08-in-f3.1e100.net [216.58.223.35]
16 53 ms * * jnb01s08-in-f3.1e100.net [216.58.223.35]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 40 ms 39 ms 40 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 34 ms 32 ms 36 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * * * Request timed out.
4 61 ms 34 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * 98 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * * * Request timed out.
9 * 35 ms 36 ms 72.14.194.74
10 * 34 ms * 72.14.239.129
11 * 51 ms 58 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 34 ms 31 ms 32 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * 33 ms 35 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 36 ms 34 ms 35 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * 47 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * * * Request timed out.
9 * * 42 ms 72.14.194.74
10 290 ms 307 ms * 72.14.239.129
11 * * * Request timed out.
12 112 ms 63 ms 94 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Looking at your 2nd hop latency, this should never be above 30ms, but should really be closer to 10ms or less, so I don't think this is specific to the network. North region latency is reporting stable at present, so I think we need to consider that it may be on the line. Have you tested with a different ISP network?
 
Afriman, should I send the PM I sent to AfriGuy last night to you as well? Havent heard anything back yet. Maybe Afriguy is of today or something.
 
Looking at your 2nd hop latency, this should never be above 30ms, but should really be closer to 10ms or less, so I don't think this is specific to the network. North region latency is reporting stable at present, so I think we need to consider that it may be on the line. Have you tested with a different ISP network?

Yes, I have tested with a web africa account and the packet loss goes away 100%. I am in Edenvale. I have also tested a friends business account in Boksburg and he is also having the same packet loss at the same time, ok it was a few days ago and did not save the log.

Just ran a tracert now.. No packet loss... My guess is it is happening when the network is busy...
C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 35 ms 35 ms 36 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [1
5.1]
3 37 ms 36 ms 44 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41
.17]
4 35 ms 48 ms 33 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41
.115]
5 35 ms 33 ms 41 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [4
5.114]
6 62 ms 47 ms 47 ms 41.181.180.10
7 74 ms 48 ms 50 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44
8 35 ms 35 ms 46 ms 41.181.139.99
9 37 ms 36 ms 42 ms 72.14.194.74
10 36 ms 35 ms 36 ms 72.14.239.129
11 53 ms 57 ms 35 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

2nd hop still @ 30ms... but i accept that that is my exchange. I cant give you an webafrica tracert at the moment because I cannot change my internet settings remotely without losing my remote connection.

Edit:.... made a plan

WebAfrica Tracert

C:\Users\Neil>tracert www.google.co.za

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

1 1 ms <1 ms 1 ms 192.168.1.254
2 34 ms 32 ms 31 ms 196-210-112-129.dynamic.isadsl.co.za [196.210.112.129]
3 35 ms 36 ms 37 ms 196.38.73.85
4 34 ms 44 ms 35 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 69 ms 66 ms 38 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 60 ms 59 ms 39 ms 196.26.0.130
7 35 ms 35 ms 38 ms 72.14.205.16
8 38 ms 35 ms 34 ms 72.14.239.129
9 35 ms 36 ms 37 ms jnb01s08-in-f3.1e100.net [216.58.223.35]
 
Last edited:
Yes, I have tested with a web africa account and the packet loss goes away 100%. I am in Edenvale. I have also tested a friends business account in Boksburg and he is also having the same packet loss at the same time, ok it was a few days ago and did not save the log.

Just ran a tracert now.. No packet loss... My guess is it is happening when the network is busy...
C:\Users\Neil>tracert www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 35 ms 35 ms 36 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [1
5.1]
3 37 ms 36 ms 44 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41
.17]
4 35 ms 48 ms 33 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41
.115]
5 35 ms 33 ms 41 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [4
5.114]
6 62 ms 47 ms 47 ms 41.181.180.10
7 74 ms 48 ms 50 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44
8 35 ms 35 ms 46 ms 41.181.139.99
9 37 ms 36 ms 42 ms 72.14.194.74
10 36 ms 35 ms 36 ms 72.14.239.129
11 53 ms 57 ms 35 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

2nd hop still @ 30ms... but i accept that that is my exchange. I cant give you an webafrica tracert at the moment because I cannot change my internet settings remotely without losing my remote connection.

Thanks for running the test!

At the moment our network demand is quite high, so it's great to hear that packet loss is at the level you noted. It means we're finally smoothing out any lingering issues.

If things start to look a bit worse for the wear, please let us know! Any traceroutes you can provide if things get a bit wonky will always help.
 
My GTA V download is almost done, 4GB's to go, been getting full speed the entire way. Thanks Afrihost :D
 
Thanks for running the test!

At the moment our network demand is quite high, so it's great to hear that packet loss is at the level you noted. It means we're finally smoothing out any lingering issues.

If things start to look a bit worse for the wear, please let us know! Any traceroutes you can provide if things get a bit wonky will always help.

ok.. I'll post another trace tonight from myself and my friend in Boksburg. It has happened for the past week or so (That I have noticed) when I get a change to play warcraft at about 8pm. Warcraft is more or less playable, but heroes of the storm suffers badly with the packet loss, changing to Webafrica fixes all of the disconnecting issues.
 
ok.. I'll post another trace tonight from myself and my friend in Boksburg. It has happened for the past week or so (That I have noticed) when I get a change to play warcraft at about 8pm. Warcraft is more or less playable, but heroes of the storm suffers badly with the packet loss, changing to Webafrica fixes all of the disconnecting issues.

Thanks, I'd really appreciate that.
 
Thanks for running the test!

At the moment our network demand is quite high, so it's great to hear that packet loss is at the level you noted. It means we're finally smoothing out any lingering issues.

If things start to look a bit worse for the wear, please let us know! Any traceroutes you can provide if things get a bit wonky will always help.

As promised my current tracert
From Afrihost
C:\Users\Neil>tracert -d www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 38 ms 33 ms 54 ms 105.236.15.1
3 * 146 ms 190 ms 41.181.178.17
4 * 34 ms * 41.181.165.115
5 61 ms * * 41.181.165.114
6 46 ms 66 ms 39 ms 196.44.0.224
7 * 423 ms 322 ms 196.44.31.170
8 * 43 ms 43 ms 41.181.139.109
9 * 209 ms * 72.14.194.74
10 99 ms 362 ms 164 ms 72.14.239.129
11 * * * Request timed out.
12 * * * Request timed out.
13 * * 36 ms 216.58.223.35

Trace complete.


From webafrica
C:\Users\Neil>tracert -d www.google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 34 ms 41 ms 32 ms 196.210.112.129
3 35 ms 33 ms 62 ms 196.38.73.213
4 33 ms 36 ms 35 ms 196.38.73.9
5 114 ms 38 ms 37 ms 168.209.1.163
6 34 ms 33 ms 35 ms 196.26.0.130
7 99 ms 46 ms 47 ms 72.14.205.16
8 34 ms 35 ms 36 ms 72.14.239.129
9 33 ms 35 ms 36 ms 216.58.223.35

cant remote into my buds computer in boksburg currently, it is in use :)
 
As promised my current tracert
From Afrihost
C:\Users\Neil>tracert -d www.google.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 38 ms 33 ms 54 ms 105.236.15.1
3 * 146 ms 190 ms 41.181.178.17
4 * 34 ms * 41.181.165.115
5 61 ms * * 41.181.165.114
6 46 ms 66 ms 39 ms 196.44.0.224
7 * 423 ms 322 ms 196.44.31.170
8 * 43 ms 43 ms 41.181.139.109
9 * 209 ms * 72.14.194.74
10 99 ms 362 ms 164 ms 72.14.239.129
11 * * * Request timed out.
12 * * * Request timed out.
13 * * 36 ms 216.58.223.35

Trace complete.


From webafrica
C:\Users\Neil>tracert -d www.google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 34 ms 41 ms 32 ms 196.210.112.129
3 35 ms 33 ms 62 ms 196.38.73.213
4 33 ms 36 ms 35 ms 196.38.73.9
5 114 ms 38 ms 37 ms 168.209.1.163
6 34 ms 33 ms 35 ms 196.26.0.130
7 99 ms 46 ms 47 ms 72.14.205.16
8 34 ms 35 ms 36 ms 72.14.239.129
9 33 ms 35 ms 36 ms 216.58.223.35

cant remote into my buds computer in boksburg currently, it is in use :)

Not looking that great here :(
Would you be able to run another test in an hours time to compare?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X