Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Genie you missed my post :( 6223 oh hello Fella.. Welcome back, hope you had a nice holiday :)

Yo Ice! :D Sorry about the missed post here. I think I still have your account details in my inbox... Will check it out for you.
 
The Durban issue has returned :(
Seriously what is going on between Joburg and Cape Town?

Tracing route to [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 11 ms 11 ms 15 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 14 ms 17 ms 10 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 12 ms 12 ms 11 ms 41.162.84.192
6 24 ms 25 ms 22 ms 172.18.1.162
7 188 ms 187 ms 189 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 355 ms 358 ms 368 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]

9 348 ms 349 ms 345 ms if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
10 350 ms 350 ms 351 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 349 ms 357 ms 355 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 354 ms 353 ms 355 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 345 ms 347 ms 346 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 * 348 ms 350 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 350 ms 351 ms 344 ms 80.231.62.2
16 351 ms 346 ms 348 ms ae11.mpr2.lhr2.uk.zip.zayo.com [64.125.30.52]
17 416 ms 415 ms 415 ms ae27.cs1.lhr11.uk.eth.zayo.com [64.125.30.236]
18 456 ms 410 ms 413 ms ae5.cs1.lga5.us.eth.zayo.com [64.125.29.126]
19 419 ms 421 ms 419 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
20 415 ms 413 ms 413 ms ae2.er3.lga5.us.zip.zayo.com [64.125.31.214]
21 417 ms 418 ms 415 ms 128.177.165.234.IPYX-100687-870-ZYO.zip.zayo.com [128.177.165.234]
22 447 ms 445 ms 445 ms be8.bb02.ewr2.tfbnw.net [157.240.33.34]
23 449 ms 469 ms 446 ms ae42.bb04.iad3.tfbnw.net [157.240.33.23]
24 507 ms 503 ms 503 ms be12.bb02.prn2.tfbnw.net [31.13.26.151]

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

Not looking too good here... We're not seeing a huge amount of complaints in general, but please PM me your username and I'll send these results over to our NOC Team to investigate. :)
 
Yo Ice! :D Sorry about the missed post here. I think I still have your account details in my inbox... Will check it out for you.
Cheers S, btw i know all your names now. :D

Spoke to Richard in support, as i would like to see my total remaining to reflect correctly. Bit confusing with over a TB data left, but only showing as 121 gigs in CZ
 
Having problems in Durban as well:cry:


Tracing route to [83.149.127.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 41 ms 31 ms 27 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 28 ms 28 ms 28 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 48 ms 40 ms 40 ms 41.162.84.192
6 51 ms 61 ms 105 ms 172.18.1.162
7 226 ms 209 ms 222 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41
.206.178.29]
8 * 429 ms 384 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.20
6.178.2]
9 383 ms 376 ms 376 ms if-ae-5-20.tcore2.PV9-Lisbon.as6453.net [80.231.
159.61]
10 380 ms 378 ms 378 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.1
58.5]
11 373 ms 375 ms 386 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.2
31.158.30]
12 384 ms 382 ms 383 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.
138.22]
13 376 ms 377 ms 373 ms if-ae-8-2.tcore2.AV2-Amsterdam.as6453.net [80.23
1.131.6]
14 378 ms 373 ms 371 ms if-ae-10-2.thar1.HNN-Amsterdam.as6453.net [80.23
1.205.9]
15 373 ms 379 ms 378 ms 195.219.162.82
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms
 
Hey guys, our Network Team just made a few configuration changes in the East. Could you please post new traceroutes for us to confirm? :)
 
Still not doing great in Cape Town.

Code:
 Pinging afrihost.com [104.20.30.244] with 64 bytes of data:

 Reply from 104.20.30.244:  bytes=64  time=210   TTL=52  seq=1
 Reply from 104.20.30.244:  bytes=64  time=31    TTL=52  seq=2
 Reply from 104.20.30.244:  bytes=64  time=312   TTL=52  seq=3
 Reply from 104.20.30.244:  bytes=64  time=512   TTL=52  seq=4
 Reply from 104.20.30.244:  bytes=64  time=305   TTL=52  seq=5
 Reply from 104.20.30.244:  bytes=64  time=430   TTL=52  seq=6
 Request timed out.
 Request timed out.
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=9
 Reply from 104.20.30.244:  bytes=64  time=29    TTL=52  seq=10
 Reply from 104.20.30.244:  bytes=64  time=1375  TTL=52  seq=11
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=12
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=13
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=14
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=15
 Reply from 104.20.30.244:  bytes=64  time=31    TTL=52  seq=16
 Reply from 104.20.30.244:  bytes=64  time=624   TTL=52  seq=17
 Request timed out.
 Reply from 104.20.30.244:  bytes=64  time=28    TTL=52  seq=19
 Reply from 104.20.30.244:  bytes=64  time=32    TTL=52  seq=20
 Reply from 104.20.30.244:  bytes=64  time=29    TTL=52  seq=21
 Reply from 104.20.30.244:  bytes=64  time=28    TTL=52  seq=22
 Reply from 104.20.30.244:  bytes=64  time=34    TTL=52  seq=23
 Reply from 104.20.30.244:  bytes=64  time=27    TTL=52  seq=24
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=25

 Ping statistics for afrihost.com
  Packets: Sent = 25, Received = 22, Lost = 3 (12% loss)
 Approximate round trip times in milliseconds:
  Minimum = 25, Maximum = 1375, Average = 190

Can't do anything as no pages load properly, speedtest is reporting my line as a 0.01Mbit connection.

I'm on a 100Mbit fibre connection. This has been a problem since Saturday. I'll have to cancel if this persists.

I've tried another ISP's account and it's working fine in comparison.
 
Still not doing great in Cape Town.

Code:
 Pinging afrihost.com [104.20.30.244] with 64 bytes of data:

 Reply from 104.20.30.244:  bytes=64  time=210   TTL=52  seq=1
 Reply from 104.20.30.244:  bytes=64  time=31    TTL=52  seq=2
 Reply from 104.20.30.244:  bytes=64  time=312   TTL=52  seq=3
 Reply from 104.20.30.244:  bytes=64  time=512   TTL=52  seq=4
 Reply from 104.20.30.244:  bytes=64  time=305   TTL=52  seq=5
 Reply from 104.20.30.244:  bytes=64  time=430   TTL=52  seq=6
 Request timed out.
 Request timed out.
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=9
 Reply from 104.20.30.244:  bytes=64  time=29    TTL=52  seq=10
 Reply from 104.20.30.244:  bytes=64  time=1375  TTL=52  seq=11
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=12
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=13
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=14
 Reply from 104.20.30.244:  bytes=64  time=26    TTL=52  seq=15
 Reply from 104.20.30.244:  bytes=64  time=31    TTL=52  seq=16
 Reply from 104.20.30.244:  bytes=64  time=624   TTL=52  seq=17
 Request timed out.
 Reply from 104.20.30.244:  bytes=64  time=28    TTL=52  seq=19
 Reply from 104.20.30.244:  bytes=64  time=32    TTL=52  seq=20
 Reply from 104.20.30.244:  bytes=64  time=29    TTL=52  seq=21
 Reply from 104.20.30.244:  bytes=64  time=28    TTL=52  seq=22
 Reply from 104.20.30.244:  bytes=64  time=34    TTL=52  seq=23
 Reply from 104.20.30.244:  bytes=64  time=27    TTL=52  seq=24
 Reply from 104.20.30.244:  bytes=64  time=25    TTL=52  seq=25

 Ping statistics for afrihost.com
  Packets: Sent = 25, Received = 22, Lost = 3 (12% loss)
 Approximate round trip times in milliseconds:
  Minimum = 25, Maximum = 1375, Average = 190

Can't do anything as no pages load properly, speedtest is reporting my line as a 0.01Mbit connection.

I'm on a 100Mbit fibre connection. This has been a problem since Saturday. I'll have to cancel if this persists.

I've tried another ISP's account and it's working fine in comparison.

This kind of P/L and latency is not coming up on our tests. Mind posting a traceroute?
 
My youtube is running at 720 for SafariLive stream, Al Jazeera does not go higher than 480, but it's consistent between AH and WA.
 
This kind of P/L and latency is not coming up on our tests. Mind posting a traceroute?

Yeah I dunno wtf is up. Now it's fine.

Code:
Tracing route to store.playstation.com [104.81.11.171] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     4ms     3ms     3ms    169.1.5.82
   3     4ms     4ms     4ms    169.1.5.128
   4     3ms     2ms     3ms    41.164.52.40
   5     3ms     5ms     8ms    41.206.164.53
   6   154ms   151ms   152ms    80.231.159.89
   7   152ms   154ms   152ms    80.231.158.5
   8   155ms   155ms   155ms    80.231.158.30
   9     *       *       *      Request timed out.
  10   158ms   158ms   158ms    80.231.131.118
  11   159ms   157ms   159ms    62.115.9.173
  12   153ms   172ms   153ms    80.91.247.93
  13   155ms   158ms   158ms    213.155.133.5
  14   153ms   155ms   155ms    62.115.55.74
  15   155ms   155ms   155ms    104.81.11.171

Trace complete.

Tracing route to afrihost.com [104.20.30.244] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     5ms     3ms     3ms    169.1.5.82
   3     5ms     3ms     3ms    169.1.5.128
   4     3ms     2ms     3ms    41.164.52.40
   5    22ms    24ms    24ms    172.18.1.162
   6    25ms    24ms    24ms    196.46.25.198
   7    24ms    24ms    24ms    104.20.30.244

Trace complete.

Tracing route to google.com [216.58.223.46] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     6ms     5ms     2ms    169.1.5.82
   3     7ms     4ms     4ms    169.1.5.128
   4     5ms     4ms     3ms    41.164.52.40
   5    24ms    24ms    24ms    172.18.1.162
   6    24ms    23ms    24ms    72.14.194.206
   7    24ms    24ms    24ms    72.14.239.129
   8    24ms    24ms    24ms    216.58.223.46

Trace complete.


 Pinging afrihost.com [104.20.31.244] with 64 bytes of data:

 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=1
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=2
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=3
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=4
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=5
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=6
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=7
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=8
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=9
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=10
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=11
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=12
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=13
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=14
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=15
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=16
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=17
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=18
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=19
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=20
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=21
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=22
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=23
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=24
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=25

 Ping statistics for afrihost.com
  Packets: Sent = 25, Received = 25, Lost = 0 (0% loss)
 Approximate round trip times in milliseconds:
  Minimum = 23, Maximum = 26, Average = 24



 
Last edited:
Yeah I dunno wtf is up. Now it's fine.

Code:
Tracing route to store.playstation.com [104.81.11.171] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     4ms     3ms     3ms    169.1.5.82
   3     4ms     4ms     4ms    169.1.5.128
   4     3ms     2ms     3ms    41.164.52.40
   5     3ms     5ms     8ms    41.206.164.53
   6   154ms   151ms   152ms    80.231.159.89
   7   152ms   154ms   152ms    80.231.158.5
   8   155ms   155ms   155ms    80.231.158.30
   9     *       *       *      Request timed out.
  10   158ms   158ms   158ms    80.231.131.118
  11   159ms   157ms   159ms    62.115.9.173
  12   153ms   172ms   153ms    80.91.247.93
  13   155ms   158ms   158ms    213.155.133.5
  14   153ms   155ms   155ms    62.115.55.74
  15   155ms   155ms   155ms    104.81.11.171

Trace complete.

Tracing route to afrihost.com [104.20.30.244] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     5ms     3ms     3ms    169.1.5.82
   3     5ms     3ms     3ms    169.1.5.128
   4     3ms     2ms     3ms    41.164.52.40
   5    22ms    24ms    24ms    172.18.1.162
   6    25ms    24ms    24ms    196.46.25.198
   7    24ms    24ms    24ms    104.20.30.244

Trace complete.

Tracing route to google.com [216.58.223.46] over a maximum of 20 hops

   1     *       *       *      Request timed out.
   2     6ms     5ms     2ms    169.1.5.82
   3     7ms     4ms     4ms    169.1.5.128
   4     5ms     4ms     3ms    41.164.52.40
   5    24ms    24ms    24ms    172.18.1.162
   6    24ms    23ms    24ms    72.14.194.206
   7    24ms    24ms    24ms    72.14.239.129
   8    24ms    24ms    24ms    216.58.223.46

Trace complete.


 Pinging afrihost.com [104.20.31.244] with 64 bytes of data:

 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=1
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=2
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=3
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=4
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=5
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=6
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=7
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=8
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=9
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=10
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=11
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=12
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=13
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=14
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=15
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=16
 Reply from 104.20.31.244:  bytes=64  time=26    TTL=52  seq=17
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=18
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=19
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=20
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=21
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=22
 Reply from 104.20.31.244:  bytes=64  time=25    TTL=52  seq=23
 Reply from 104.20.31.244:  bytes=64  time=23    TTL=52  seq=24
 Reply from 104.20.31.244:  bytes=64  time=24    TTL=52  seq=25

 Ping statistics for afrihost.com
  Packets: Sent = 25, Received = 25, Lost = 0 (0% loss)
 Approximate round trip times in milliseconds:
  Minimum = 23, Maximum = 26, Average = 24




Awesome! :) Keep us posted with feedback.
 
Still looking fine

Tracing route to [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 13 ms 11 ms 12 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 11 ms 11 ms 11 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 11 ms 11 ms 13 ms 41.162.84.192
6 19 ms 22 ms 19 ms 172.18.1.162
7 20 ms 19 ms 19 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 192 ms 219 ms 192 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 179 ms 180 ms 181 ms if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
10 183 ms 182 ms 181 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 187 ms 188 ms 212 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 184 ms 185 ms 184 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 179 ms 181 ms 181 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 183 ms 182 ms 181 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 181 ms 181 ms 181 ms 80.231.62.2
 
Still looking fine

Tracing route to [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 13 ms 11 ms 12 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 11 ms 11 ms 11 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 11 ms 11 ms 13 ms 41.162.84.192
6 19 ms 22 ms 19 ms 172.18.1.162
7 20 ms 19 ms 19 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 192 ms 219 ms 192 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 179 ms 180 ms 181 ms if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
10 183 ms 182 ms 181 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 187 ms 188 ms 212 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 184 ms 185 ms 184 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 179 ms 181 ms 181 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 183 ms 182 ms 181 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 181 ms 181 ms 181 ms 80.231.62.2

Awesome-sauce! :D
 
Hi Afrihost –

Over the previous three weeks I reported about latency issues with YouTube live streams in the evenings in the Cape region on Afrihost capped dsl. So far tonight it's been fine (can stream full 1080p). Will report back tomorrow evening, as well.
 
That 120GB remaining definitely doesn't make sense... I'll pass it on to to our Dev Team to look at. :) You will, however, see all your data links listed below the usage graph, as well as the total listed under data statistics. :) Good luck using it all!
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X