Status
Not open for further replies.
It shouldn't. My pc and phone have no difference in speed, I'll get a speedtest from my phone tonight.

I've already tried everything possible from my end to try sort this out, new router, new ethernet cables, different pc, reboot router, format, that weird plugin for twitch, running that application that "optimizes your windows tcp stack." You name it I've tried it, nothing has helped except the proxy rodent setup but that's not guaranteed to work anymore for whatever reason.

I doubt its anything to do with me because @TheRoDent installed his black box here, which connected directly to the ont and was before any device in my house, and he saw the packet loss too. Also MDE who lives in the same "Claremont fiber block" as me is having similar issues.

Speaking of which, @MDE how's your internet been since the maintenance?

Right now...constant 1% packet loss and only the nanny is at home. Was in bed early last night with sick kid so didnt use much of the net last night. But this is the iPerf which I have running as a cron in peak hours:

Linux HPM.Home 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64
Time: Mon, 12 Mar 2019 17:10:02 GMT
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
Cookie: HPM.Home.1552324201.765462.3bab29fb3
[ 4] local 192.168.1.8 port 53553 connected to 154.0.15.181 port 17001
Starting Test: protocol: UDP, 1 streams, 1400 byte blocks, omitting 2 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 130 KBytes 1.06 Mbits/sec 0.982 ms 0/95 (0%) (omitted)
[ 4] 1.00-2.00 sec 122 KBytes 997 Kbits/sec 1.696 ms 0/89 (0%) (omitted)
[ 4] 0.00-1.00 sec 122 KBytes 997 Kbits/sec 0.130 ms 0/89 (0%)
[ 4] 1.00-2.00 sec 120 KBytes 986 Kbits/sec 1.776 ms 1/89 (1.1%)
[ 4] 2.00-3.00 sec 122 KBytes 997 Kbits/sec 0.340 ms 1/90 (1.1%)
[ 4] 3.00-4.00 sec 122 KBytes 997 Kbits/sec 0.137 ms 0/89 (0%)
[ 4] 4.00-5.00 sec 122 KBytes 997 Kbits/sec 0.218 ms 0/89 (0%)
[ 4] 5.00-6.00 sec 123 KBytes 1.01 Mbits/sec 0.603 ms 0/90 (0%)
[ 4] 6.00-7.00 sec 122 KBytes 997 Kbits/sec 1.401 ms 0/89 (0%)
[ 4] 7.00-8.00 sec 97.1 KBytes 795 Kbits/sec 2.615 ms 17/88 (19%)
[ 4] 8.00-9.00 sec 123 KBytes 1.01 Mbits/sec 0.169 ms 0/90 (0%)
[ 4] 9.00-10.00 sec 123 KBytes 1.01 Mbits/sec 0.289 ms 0/90 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 1.20 MBytes 1.01 Mbits/sec 0.289 ms 19/893 (2.1%)
[ 4] Sent 893 datagrams
CPU Utilization: local/receiver 0.5% (0.1%u/0.4%s), remote/sender 0.2% (0.0%u/0.1%s)
 
It does seem like MTN has sorted out the issue. Our handoff interface from them seems back to normal levels. You still have an issue ?

Seems fine now, but I want to know what CI/MTN are going to give the customers affected by the 2 day borkage .. there has to be a financial penalty for bad service otherwise we get back to the Telkom "best effort" rubbish
 
Seems fine now, but I want to know what CI/MTN are going to give the customers affected by the 2 day borkage .. there has to be a financial penalty for bad service otherwise we get back to the Telkom "best effort" rubbish

Fibre to the home seems to be "best effort", same as ADSL - the FNOs just "do their best" to keep you online at all times.

If you want better than that, you'll probably have to sign up for some business line with SLAs in place.
 
Fibre to the home seems to be "best effort", same as ADSL - the FNOs just "do their best" to keep you online at all times.

If you want better than that, you'll probably have to sign up for some business line with SLAs in place.
At least you got a prorata refund from Telkom ADSL.
 
Some day I'll be able to play twitch clips without buffering on my 200/200 line..
 
@TheRoDent I can confirm that while 'live' switch broadcasts are better on the proxy, as well as general browsing for me - which is why I am now always using it - twitch vods/clips always seem erratic in playback. But this might not be a CI exclusive issue as i have seen the same behaviour on vox.

And to provide more feedback to the above, the mtr is higher than it used to be for me.

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |   31 |   31 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    7 |    0 |    0 |    0 |    0 |    0 |
|                            192.168.10.5 -    0 |   31 |   31 |    3 |    4 |   11 |    4 |
|                            192.168.11.6 -    0 |   31 |   31 |    2 |    3 |    5 |    2 |
|                             154.0.4.161 -    0 |   31 |   31 |    2 |    3 |    5 |    3 |
|                             154.0.4.158 -    0 |   31 |   31 |  142 |  143 |  145 |  143 |
|                              154.0.5.18 -    0 |   31 |   31 |  142 |  143 |  145 |  143 |
|              be20.asr01.thn.as20860.net -    0 |   31 |   31 |  172 |  173 |  175 |  172 |
|              po201.dc9core1.as20860.net -    0 |   31 |   31 |  170 |  176 |  232 |  171 |
|        94.zone.4.r.dc9.redstation.co.uk -    0 |   31 |   31 |  166 |  169 |  181 |  167 |
|                        queen.cisp.co.za -    0 |   31 |   31 |  173 |  174 |  181 |  175 |
|________________________________________________|______|______|______|______|______|______|
 
@TheRoDent I can confirm that while 'live' switch broadcasts are better on the proxy, as well as general browsing for me - which is why I am now always using it - twitch vods/clips always seem erratic in playback. But this might not be a CI exclusive issue as i have seen the same behaviour on vox.

And to provide more feedback to the above, the mtr is higher than it used to be for me.

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |   31 |   31 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    7 |    0 |    0 |    0 |    0 |    0 |
|                            192.168.10.5 -    0 |   31 |   31 |    3 |    4 |   11 |    4 |
|                            192.168.11.6 -    0 |   31 |   31 |    2 |    3 |    5 |    2 |
|                             154.0.4.161 -    0 |   31 |   31 |    2 |    3 |    5 |    3 |
|                             154.0.4.158 -    0 |   31 |   31 |  142 |  143 |  145 |  143 |
|                              154.0.5.18 -    0 |   31 |   31 |  142 |  143 |  145 |  143 |
|              be20.asr01.thn.as20860.net -    0 |   31 |   31 |  172 |  173 |  175 |  172 |
|              po201.dc9core1.as20860.net -    0 |   31 |   31 |  170 |  176 |  232 |  171 |
|        94.zone.4.r.dc9.redstation.co.uk -    0 |   31 |   31 |  166 |  169 |  181 |  167 |
|                        queen.cisp.co.za -    0 |   31 |   31 |  173 |  174 |  181 |  175 |
|________________________________________________|______|______|______|______|______|______|
Looks like the return path for your IP range is wrong. As in it probably routes out west coast, but inbound somehow looks like its going east coast.
 
From Cpt:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          192.168.77.254 -    0 |   69 |   69 |    0 |    0 |    1 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                            192.168.10.5 -    0 |   69 |   69 |    2 |    4 |   13 |    3 |
|                            192.168.11.6 -    0 |   69 |   69 |    1 |    3 |    4 |    4 |
|                uwx-cust.coolideas.co.za -    0 |   69 |   69 |    1 |    2 |    4 |    2 |
|                             154.0.4.158 -    0 |   69 |   69 |  141 |  142 |  144 |  143 |
|                              154.0.5.18 -    0 |   69 |   69 |  141 |  142 |  144 |  143 |
|              be20.asr01.thn.as20860.net -    0 |   69 |   69 |  169 |  171 |  174 |  171 |
|              po201.dc9core1.as20860.net -    0 |   69 |   69 |  174 |  181 |  225 |  193 |
|        94.zone.4.r.dc9.redstation.co.uk -    0 |   69 |   69 |  174 |  178 |  203 |  178 |
|                        queen.cisp.co.za -    0 |   69 |   69 |  174 |  175 |  177 |  175 |
|________________________________________________|______|______|______|______|______|______|
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 54 | 54 | 0 | 0 | 1 | 0 |
| u3e-cust.coolideas.co.za - 0 | 54 | 54 | 0 | 0 | 6 | 0 |
| uya-cust.coolideas.co.za - 0 | 54 | 54 | 0 | 0 | 3 | 0 |
| u12a-cust.coolideas.co.za - 0 | 54 | 54 | 1 | 1 | 4 | 1 |
| 154.0.1.138 - 0 | 54 | 54 | 1 | 1 | 4 | 1 |
| 197.96.214.112 - 0 | 54 | 54 | 1 | 3 | 12 | 2 |
| 168.209.100.212 - 0 | 54 | 54 | 172 | 175 | 195 | 176 |
| be20.asr01.thn.as20860.net - 0 | 54 | 54 | 166 | 166 | 171 | 166 |
| po202.dc9core1.as20860.net - 0 | 54 | 54 | 181 | 188 | 255 | 181 |
| 94.zone.4.r.dc9.redstation.co.uk - 0 | 54 | 54 | 180 | 182 | 195 | 189 |
| queen.cisp.co.za - 0 | 54 | 54 | 175 | 175 | 176 | 175 |
|________________________________________________|______|______|______|______|______|______|
 
Right now...constant 1% packet loss and only the nanny is at home. Was in bed early last night with sick kid so didnt use much of the net last night. But this is the iPerf which I have running as a cron in peak hours:

Linux HPM.Home 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64
Time: Mon, 12 Mar 2019 17:10:02 GMT
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
Cookie: HPM.Home.1552324201.765462.3bab29fb3
[ 4] local 192.168.1.8 port 53553 connected to 154.0.15.181 port 17001
Starting Test: protocol: UDP, 1 streams, 1400 byte blocks, omitting 2 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 130 KBytes 1.06 Mbits/sec 0.982 ms 0/95 (0%) (omitted)
[ 4] 1.00-2.00 sec 122 KBytes 997 Kbits/sec 1.696 ms 0/89 (0%) (omitted)
[ 4] 0.00-1.00 sec 122 KBytes 997 Kbits/sec 0.130 ms 0/89 (0%)
[ 4] 1.00-2.00 sec 120 KBytes 986 Kbits/sec 1.776 ms 1/89 (1.1%)
[ 4] 2.00-3.00 sec 122 KBytes 997 Kbits/sec 0.340 ms 1/90 (1.1%)
[ 4] 3.00-4.00 sec 122 KBytes 997 Kbits/sec 0.137 ms 0/89 (0%)
[ 4] 4.00-5.00 sec 122 KBytes 997 Kbits/sec 0.218 ms 0/89 (0%)
[ 4] 5.00-6.00 sec 123 KBytes 1.01 Mbits/sec 0.603 ms 0/90 (0%)
[ 4] 6.00-7.00 sec 122 KBytes 997 Kbits/sec 1.401 ms 0/89 (0%)
[ 4] 7.00-8.00 sec 97.1 KBytes 795 Kbits/sec 2.615 ms 17/88 (19%)
[ 4] 8.00-9.00 sec 123 KBytes 1.01 Mbits/sec 0.169 ms 0/90 (0%)
[ 4] 9.00-10.00 sec 123 KBytes 1.01 Mbits/sec 0.289 ms 0/90 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 1.20 MBytes 1.01 Mbits/sec 0.289 ms 19/893 (2.1%)
[ 4] Sent 893 datagrams
CPU Utilization: local/receiver 0.5% (0.1%u/0.4%s), remote/sender 0.2% (0.0%u/0.1%s)

Sorry to hear about your child man, hope he or she gets better soon.

That iperf actually looks a whole lot better, aside from the one random 19% loss result.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X