Afrihost New Network Feedback - Part 2

Vorastra · Jul 26, 2016

AfriGuy said:
o.0
Pretty high latency there. What's your ping to the exchange like?

EDIT: Telkom confirm issues in KZN for DBN North and La Lucia, affecting:
031-562, 572, 563 & 564.

That 100% packet loss on the 2nd/3rd hop (isn't that the exchange?) made me suspicious, so I completely reset my router to the point where I have to refill everything in. Now I'm getting full-speed. I swear this router is possessed.

In future, how do I ping the exchange? Isn't that the bras.afrihost.com ?

AfriGuy · Jul 26, 2016

Rickster said:
I was under the impression that it optimises your line based on its statistics, why would a good line be put on interleaved?

Is the telkom guys you speak to able to remove it from my profile?

ASSIA will change the line sync based on the stats, not the mode though.
While it can be temporarily removed by some Telkom techs - automated passes will simply see it re-enabled.

AfriGuy · Jul 26, 2016

Vorastra said:
That 100% packet loss on the 2nd/3rd hop (isn't that the exchange?) made me suspicious, so I completely reset my router to the point where I have to refill everything in. Now I'm getting full-speed. I swear this router is possessed.

In future, how do I ping the exchange? Isn't that the bras.afrihost.com ?

It's OK if ICMP doesn't respond there, that's how the majority of the ESRs are setup now

Grab a ping to bras.afrihost.com and it'll show the latency to your exchange.

NewBiks · Jul 26, 2016

Every night the performance of streaming is greatly reduced

This is a 720p60fps stream

Twitch
http://puu.sh/qfa62/a66658ec71.png

http://puu.sh/qfach/cbfb34c643.png

Icemanbrfc · Jul 26, 2016

Whats the reason for disconnects? A line issue, or another problem? My line was down, after a few disconnects and had to get Telkom to sort it out

Hummercellc · Jul 26, 2016

And like clock work, Mweb peering down.
Can't access mweb.co.za, news24.com, dstv.com, etc
YouTube buffering
Facebook slow
Standard Bank not opening either now.

Rickster · Jul 26, 2016

krustyrsa said:
Nope, thats not the case...You have be added to the exclusion list for that to happen ...its telkoms new method of line monitoring, ASSIA DSM is here to stay.

Im not saying telkom should remove ASSIA, they must reconfigure it so that fast path is applied to stable lines while unstable lines get interleaved. Unless its bugged.

krustyrsa · Jul 26, 2016

Rickster said:
Im not saying telkom should remove ASSIA, they must reconfigure it so that fast path is applied to stable lines while unstable lines get interleaved. Unless its bugged.

It not bugged. Interleaving is part of the optimization...They can however configure it to stay stabilized until it detects a defect, but interleaving will still be there. Unless they completely remove ASSIA DSM...

standerr · Jul 26, 2016

This is getting tiring. Every evening things are slowing down. Anybody else experiencing issues?
Local and International

Code:

Tracing route to [url]www.mweb.co.za[/url] [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    23 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    38 ms    44 ms    35 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   124 ms   125 ms   146 ms  optinet.ixp.capetown [196.10.140.145] 
  6    75 ms    79 ms    74 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7   127 ms    63 ms    62 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8   118 ms   161 ms   140 ms  196.28.178.66 
  9    65 ms   199 ms    93 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    22 ms    22 ms    21 ms  [url]www.mweb.co.za[/url] [196.2.63.110] 

Trace complete.

Code:

Tracing route to stackoverflow.com [151.101.1.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    50 ms    47 ms    36 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    98 ms    98 ms    95 ms  41.164.52.40 
  6    71 ms    73 ms    72 ms  172.18.1.162 
  7   419 ms   419 ms   419 ms  ix-xe-0-0-0-231.thar2.1MH-Sydney.as6453.net [180.87.29.121] 
  8   482 ms   502 ms   506 ms  220.101.73.73 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   531 ms   502 ms   498 ms  59.154.142.178 
 13   399 ms   401 ms   425 ms  bundle-ether18.cha-edge902.brisbane.telstra.net [139.130.61.73] 
 14   414 ms   467 ms   476 ms  bundle-ether2.woo-edge902.brisbane.telstra.net [203.50.11.147] 
 15     *        *        *     Request timed out.
 16   397 ms   405 ms   451 ms  151.101.1.69 

Trace complete.

Freak_c · Jul 26, 2016

Getting very high pings, making streaming and general browsing a little frustrating. Edenvale area.
Router and some speedtests say all is good??

Slow browsing, international and even local.

Anyone else having some strange issues tonight?

Rickster · Jul 26, 2016

krustyrsa said:
It not bugged. Interleaving is part of the optimization...They can however configure it to stay stabilized until it detects a defect, but interleaving will still be there. Unless they completely remove ASSIA DSM...

Read this, that is how DLM is meant to work, ill try contact ASSIA to get some answers.

krustyrsa · Jul 26, 2016

Freak_c said:
Getting very high pings, making streaming and general browsing a little frustrating. Edenvale area.
Router and some speedtests say all is good??

Slow browsing, international and even local.

Anyone else having some strange issues tonight?

Streaming Netflix in HD at the moment, no issues here.

Freak_c · Jul 26, 2016

Heres mine

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

1 1 ms 1 ms 1 ms
2 * * * Request timed out.
3 2020 ms 2302 ms 2386 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 1759 ms 1301 ms 1360 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 1556 ms 1611 ms 1671 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
6 2297 ms 2320 ms 1978 ms 72.14.237.239
7 1805 ms 1855 ms 2066 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

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

1 1 ms <1 ms <1 ms
2 * * * Request timed out.
3 2370 ms 2382 ms 2033 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 1903 ms 2227 ms 2340 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 1856 ms 1652 ms 1924 ms mweb.ixp.joburg [196.46.25.145]
6 2203 ms 2284 ms 2336 ms te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
7 1749 ms 2115 ms 2145 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 1813 ms 1827 ms 1953 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 2119 ms 2259 ms 2199 ms 196.28.178.66
10 * 1804 ms 1898 ms cte-core-sw2.vwol.net [196.41.144.35]
11 2096 ms 2179 ms 2378 ms www.mweb.co.za [196.2.63.110]

Trace complete.

krustyrsa · Jul 26, 2016

Rickster said:
Read this, that is how DLM is meant to work, ill try contact ASSIA to get some answers.

m8 its a lost cause. I know how ASSIA DSM works I saw their official website...configurations won't be the same for every SP running their software.

Vio · Jul 26, 2016

Seeing unstable local latency on quakelive tonight spiking on the cpt-rx2.ip.adsl.co.za [169.1.5.82] to cpt-net1.ip.adsl.co.za [169.1.5.128] link with the latency rising from ~20ms to a ~100 for short periods causing stuttering in game:
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=23ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=35ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=37ms TTL=61
Reply from 169.1.5.128: bytes=32 time=18ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=79ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=20ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=27ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=29ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=29ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=17ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=18ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=27ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=144ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=24ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=119ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=36ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=43ms TTL=61
Reply from 169.1.5.128: bytes=32 time=28ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=78ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=30ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=22ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=33ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=11ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61

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

AfriGenie · Jul 27, 2016

Freak_c said:
Heres mine

Uh... There's something seriously wrong there... That looks like there's an issue on your line or Exchange.

How are your speedtests looking at the moment?

AfriGenie · Jul 27, 2016

Hummercellc said:
And like clock work, Mweb peering down.
Can't access mweb.co.za, news24.com, dstv.com, etc
YouTube buffering
Facebook slow
Standard Bank not opening either now.

Our Critical Care is making progress, they'll get to the bottom of this!

AfriGenie · Jul 27, 2016

NewBiks said:
Every night the performance of streaming is greatly reduced

This is a 720p60fps stream

Twitch
http://puu.sh/qfa62/a66658ec71.png

http://puu.sh/qfach/cbfb34c643.png

It looks like there were some isolated issues with Twitch itself last night which was affecting the quality as well as causing additional buffering.

Could you maybe test again this morning and see if there is any change.

AfriGenie · Jul 27, 2016

Vio said:
Seeing unstable local latency on quakelive tonight spiking on the cpt-rx2.ip.adsl.co.za [169.1.5.82] to cpt-net1.ip.adsl.co.za [169.1.5.128] link with the latency rising from ~20ms to a ~100 for short periods causing stuttering in game:
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=23ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=35ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=37ms TTL=61
Reply from 169.1.5.128: bytes=32 time=18ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=79ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=20ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=27ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=29ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=29ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=17ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=18ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=27ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=144ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=24ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=119ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=36ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=43ms TTL=61
Reply from 169.1.5.128: bytes=32 time=28ms TTL=61
Reply from 169.1.5.128: bytes=32 time=34ms TTL=61
Reply from 169.1.5.128: bytes=32 time=78ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=30ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=22ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=33ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=11ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61

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

That's not cool! Till what time were you experiencing those spikes in latency?

Icemanbrfc · Jul 27, 2016

krustyrsa said:
Streaming Netflix in HD at the moment, no issues here.

i was also streaming fine, also no issues.

Join the MyBroadband community

Get started

Afrihost New Network Feedback - Part 2

Honorary Master

Afrihost

Afrihost

Well-Known Member

Honorary Master

Expert Member

EVGA Fanatic

Senior Member

Well-Known Member

Well-Known Member

EVGA Fanatic

Senior Member

Well-Known Member

Senior Member

Expert Member

Afrihost

Afrihost

Afrihost

Afrihost

Honorary Master