Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
I am having the same issues in Amanzimtoti, Durban. 340ms to Blizzard servers and Epic servers, locals network is fine. Getting pretty tired of this.

Please post some test data here for me to look at so I can better diagnose the issue.
 
What tests do you need afriguy?

A ping or a traceroute :)
As much info as possible with the posts really helps, a lot of data is passed onto our NOC and Networking teams.

So stuff like account type, location, DNS servers being used etc etc is all handy.
 
And so we go back to square one just a few working hours later. the trend continues.
tracert www.afrihost.com

Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 10.0.0.2
2 1064 ms 1068 ms 1159 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 945 ms 1223 ms * cpt-up1.ip.adsl.co.za [169.1.5.105]
4 909 ms 998 ms 1072 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 816 ms 1200 ms 937 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 1017 ms 953 ms 974 ms africainx.ixp.capetown [196.10.140.7]
7 922 ms 799 ms 898 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-1.AINX.P2P.10G.za.africainx.net [41.84.13.196]
8 1034 ms * 985 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 956 ms 1050 ms * 104.20.30.244
10 946 ms 929 ms * 104.20.30.244
11 1166 ms 1069 ms 1049 ms 104.20.30.244

Trace complete.
 
Tracing route to facebook.com [69.171.230.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 12 ms 12 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 12 ms 11 ms 11 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 192 ms 194 ms 188 ms 41.162.84.194
6 210 ms 204 ms 197 ms 172.18.1.162
7 174 ms 167 ms 174 ms if-ae-7-0.tcore2.JSO-Johannesburg.as6453.net [41.206.179.13]
8 351 ms 402 ms 356 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
9 364 ms 357 ms 341 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 332 ms 331 ms 327 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
11 362 ms 360 ms 352 ms if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
12 360 ms 358 ms 344 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 365 ms 365 ms 356 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 352 ms 360 ms 355 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 341 ms 356 ms 362 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 355 ms 363 ms 361 ms 80.231.62.2
17 355 ms 355 ms 350 ms ae11.mpr2.lhr2.uk.zip.zayo.com [64.125.30.52]
18 427 ms 421 ms 405 ms ae27.cs1.lhr11.uk.eth.zayo.com [64.125.30.236]
19 427 ms 424 ms 416 ms ae5.cs1.lga5.us.eth.zayo.com [64.125.29.126]
20 1170 ms 451 ms 413 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
21 421 ms 406 ms 402 ms ae2.er3.lga5.us.zip.zayo.com [64.125.31.214]
22 428 ms 416 ms 421 ms 128.177.165.234.IPYX-100687-870-ZYO.zip.zayo.com [128.177.165.234]
23 432 ms 442 ms 454 ms be8.bb02.ewr2.tfbnw.net [157.240.33.34]
24 445 ms 454 ms 449 ms be20.bb02.iad3.tfbnw.net [157.240.33.25]
25 511 ms 513 ms 504 ms be12.bb01.prn2.tfbnw.net [31.13.28.211]
26 491 ms 473 ms 467 ms ae41.dr06.prn2.tfbnw.net [31.13.27.133]
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to 212.205.126.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 12 ms 12 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 11 ms 10 ms 11 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 162 ms 163 ms 162 ms 41.162.84.194
6 167 ms 164 ms 171 ms 172.18.1.162
7 192 ms 192 ms 193 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 353 ms 357 ms 371 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 329 ms 332 ms 347 ms if-ae-5-80.tcore2.PV9-Lisbon.as6453.net [80.231.159.57]
10 350 ms 353 ms 362 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 346 ms 341 ms 356 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 354 ms * 334 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 359 ms 349 ms 345 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 358 ms 355 ms 346 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 362 ms 364 ms * 195.219.83.102
16 338 ms 343 ms 352 ms ae-236-3612.edge5.London1.Level3.net [4.69.166.61]
17 363 ms 360 ms 353 ms OTE-INTERNA.edge5.London1.Level3.net [195.50.118.170]
18 * * * Request timed out.
19 401 ms 402 ms 399 ms athe-crsa-Te0-6-6-0-crs01-otenet.ath.OTEGlobe.gr [62.75.3.14]
20 399 ms 396 ms 380 ms nyma-crsa-athe-crsa-8.backbone.otenet.net [79.128.224.62]
21 409 ms 406 ms 392 ms 212.205.126.10

Trace complete.
 
Ok. I used tracert for both Diablo 3 servers for EU region.

Results:

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 25 ms 25 ms 24 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 25 ms 24 ms 25 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 161 ms 162 ms 161 ms 41.162.84.194
6 157 ms 154 ms 156 ms 172.18.1.162
7 194 ms 183 ms 180 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 376 ms 376 ms 374 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 379 ms 374 ms 370 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
10 375 ms 367 ms 357 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
11 375 ms 360 ms 348 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
12 376 ms 370 ms 355 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
13 374 ms 358 ms 349 ms if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
14 376 ms 376 ms 363 ms if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
15 375 ms 374 ms 365 ms if-ae-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
16 372 ms 364 ms 365 ms 80.231.153.66
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 * * * Request timed out.
25 * * BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158] reports: Destination net unreachable.

Trace complete.


Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 25 ms 24 ms 24 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 26 ms 24 ms 26 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 201 ms 196 ms 195 ms 41.162.84.194
6 192 ms 187 ms 187 ms 172.18.1.162
7 204 ms * 194 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 386 ms 384 ms 381 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 394 ms 413 ms 392 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
10 391 ms 380 ms 383 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
11 379 ms 381 ms 380 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
12 373 ms 388 ms 382 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
13 358 ms 367 ms 378 ms if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
14 381 ms 372 ms 372 ms if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
15 378 ms 376 ms 375 ms if-ae-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
16 376 ms 361 ms 365 ms 80.231.153.66
17 * * * Request timed out.
18 * * * Request timed out.
19 * BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158] reports: Destination net unreachable.

Trace complete.
 
And so we go back to square one just a few working hours later. the trend continues.
/Snip
Our routes differ completely.

Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert www.afrihost.com

Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    25 ms    24 ms    24 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    32 ms    31 ms    31 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    34 ms    34 ms    32 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    57 ms    58 ms    53 ms  africainx.ixp.capetown [196.10.140.7]
  7    42 ms    42 ms    42 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
  8    50 ms    51 ms    50 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
  9    42 ms    42 ms    43 ms  104.20.31.244

Trace complete.
 
Ok. I used tracert for both Diablo 3 servers for EU region.
/Snip
My results look a lot better but I'm in the Eastern Cape. :)

Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    19 ms    17 ms    16 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    17 ms    17 ms    17 ms  cpt-rx1.ip.adsl.co.za [169.1.5.94]
  5    70 ms    68 ms   108 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    34 ms    28 ms    27 ms  41.164.52.40
  7    31 ms    32 ms    31 ms  if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  8   204 ms   218 ms   221 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
  9   226 ms   222 ms   210 ms  if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
 10   222 ms   221 ms   234 ms  if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
 11   214 ms   191 ms   199 ms  if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
 12   209 ms   208 ms   218 ms  if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
 13   205 ms   202 ms   198 ms  if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
 14   183 ms   181 ms   185 ms  if-ae-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
 15   200 ms   203 ms   211 ms  80.231.153.66
 16     *        *        *     Request timed out.
 17     *     BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158]  reports: Destination net unreachable.

Trace complete.
 
And so we go back to square one just a few working hours later. the trend continues.
tracert www.afrihost.com

Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 10.0.0.2
2 1064 ms 1068 ms 1159 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 945 ms 1223 ms * cpt-up1.ip.adsl.co.za [169.1.5.105]
4 909 ms 998 ms 1072 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 816 ms 1200 ms 937 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 1017 ms 953 ms 974 ms africainx.ixp.capetown [196.10.140.7]
7 922 ms 799 ms 898 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-1.AINX.P2P.10G.za.africainx.net [41.84.13.196]
8 1034 ms * 985 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 956 ms 1050 ms * 104.20.30.244
10 946 ms 929 ms * 104.20.30.244
11 1166 ms 1069 ms 1049 ms 104.20.30.244

Trace complete.

This looks like congestion :(
How's the experience when connecting with another ISP?
 
Horrible............... EUW League of Legends

tracert_afrihsot_1.png
 
Tracing route to facebook.com [69.171.230.68]
over a maximum of 30 hops:

-snip

It's starting again. Friend and I having the same packet loss only in evening.
Times in are in the screenshots. Top left.
http://i.imgur.com/1xXsqCX.png
http://i.imgur.com/E9CaEfn.png

Ok. I used tracert for both Diablo 3 servers for EU region.

Results:

-snip

Not looking good guys :(
Starting to see a trend coming in from DBN - I've asked our NOC team to take a closer look at this to see what's happening.
 
20Mbps VDSL line. Anything international is crawling including but not limited to gaming,p2p and even http downloads...

Local:
5571867510.png


UK:
5571862523.png
 
High Latency and packet loss to all international services.
I normally see 200ms to London, currently sitting at 400ms with an average packet loss of 10%.
Seriously how many more tests must be posted by everyone before Afrihost fixes this problem? I see people complaining on Facebook as well.
 
High Latency and packet loss to all international services.
I normally see 200ms to London, currently sitting at 400ms with an average packet loss of 10%.
Seriously how many more tests must be posted by everyone before Afrihost fixes this problem? I see people complaining on Facebook as well.

Seems to be a KZN issue......
 
20Mbps VDSL line. Anything international is crawling including but not limited to gaming,p2p and even http downloads...

Local:
5571867510.png


UK:
5571862523.png

High Latency and packet loss to all international services.
I normally see 200ms to London, currently sitting at 400ms with an average packet loss of 10%.
Seriously how many more tests must be posted by everyone before Afrihost fixes this problem? I see people complaining on Facebook as well.

Please see the post below.

Not looking good guys :(
Starting to see a trend coming in from DBN - I've asked our NOC team to take a closer look at this to see what's happening.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X