Status
Not open for further replies.
i am also on Vuma Aerial in Radiokop and have very very bad packet loss. Restarted everything a few times without a resolve. it comes and goes... makes it very hard to play counter trike
 
Intermittent connectivity in Little Falls - Any Issues @PBCool ? On cable - Both local and International dropping.

Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=8ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=8ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=11ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=11ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.13.95: bytes=32 time=6ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=17ms TTL=59
Reply from 154.0.13.95: bytes=32 time=26ms TTL=59
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 355 | 355 | 0 | 0 | 0 | 0 |
| x.x.x.x - 0 | 355 | 355 | 1 | 2 | 47 | 2 |
| c4x-backbone.coolideas.co.za - 6 | 295 | 280 | 0 | 3 | 78 | 2 |
| cx-backbone.coolideas.co.za - 6 | 295 | 280 | 1 | 4 | 274 | 3 |
| c3u-backbone.coolideas.co.za - 6 | 295 | 280 | 1 | 3 | 86 | 3 |
| 154.0.4.101 - 10 | 256 | 231 | 1 | 5 | 227 | 2 |
| c2y-backbone.coolideas.co.za - 6 | 295 | 280 | 159 | 164 | 366 | 162 |
| be20.asr01.thn.as20860.net - 6 | 295 | 280 | 160 | 169 | 276 | 163 |
| po201.dc9core1.as20860.net - 6 | 291 | 275 | 164 | 179 | 453 | 207 |
| 94.zone.4.r.dc9.redstation.co.uk - 6 | 295 | 280 | 165 | 170 | 371 | 166 |

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

My packet loss is occurring after my 1st hop (last mile). I stand corrected, but doesn't this mean an issue on CISP side?
 
I'm getting insane packet loss at the moment with vumatel aerial:


--- 8.8.8.8 ping statistics ---
881 packets transmitted, 672 received, 23% packet loss, time 882262ms
rtt min/avg/max/mdev = 1.178/4.468/174.533/9.900 ms
 
--- 155.93.141.1 ping statistics ---
83 packets transmitted, 83 received, 0% packet loss, time 82127ms
rtt min/avg/max/mdev = 0.897/1.856/6.633/1.001 ms



--- 8.8.8.8 ping statistics ---
69 packets transmitted, 44 received, 36% packet loss, time 68093ms
rtt min/avg/max/mdev = 2.031/2.799/12.216/1.582 ms




$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 155.93.141.1 (155.93.141.1) 2.404 ms 2.506 ms 2.446 ms
3 154.0.1.177 (154.0.1.177) 2.674 ms 2.658 ms 2.718 ms
4 cx-backbone.coolideas.co.za (154.0.2.33) 3.124 ms 3.272 ms 3.314 ms
5 154.0.2.114 (154.0.2.114) 3.156 ms 154.0.1.138 (154.0.1.138) 3.347 ms 154.0.2.114 (154.0.2.114) 3.189 ms
6 154.0.4.101 (154.0.4.101) 4.095 ms 5.234 ms 5.217 ms
7 c11-backbone.coolideas.co.za (154.0.2.37) 5.676 ms 5.415 ms 154.0.1.141 (154.0.1.141) 5.399 ms
8 google.ixp.joburg (196.60.8.166) 5.376 ms 4.995 ms 4.961 ms
9 72.14.239.117 (72.14.239.117) 5.925 ms 5.909 ms 5.896 ms
10 google-public-dns-a.google.com (8.8.8.8) 5.705 ms 4.915 ms 2.931 ms


Seems problem lies is after the first hop.
 
All taken over same period of time:


--- 155.93.141.1 ping statistics ---
152 packets transmitted, 152 received, 0% packet loss, time 151209ms
rtt min/avg/max/mdev = 0.703/1.920/7.965/1.116 ms


--- 154.0.1.177 ping statistics ---
153 packets transmitted, 108 received, 29% packet loss, time 152468ms
rtt min/avg/max/mdev = 1.117/3.700/53.334/6.755 ms


--- 8.8.8.8 ping statistics ---
155 packets transmitted, 110 received, 29% packet loss, time 154417ms
rtt min/avg/max/mdev = 1.945/4.008/55.347/5.588 ms
 
Yeah some sort of blip on the Aerial network, throughput dropped for a while but seems to be back to normal.

Edit and now down completely.
 
Looks to be a loop on the Aerial network, so working on resolution, shouldn't take too long.
 
Yeah some sort of blip on the Aerial network, throughput dropped for a while but seems to be back to normal.

Edit and now down completely.

It has been intermittent for me the whole day but seems worse now that earlier today. When it is up it is perfect - but then it gets packet loss for about a minute or so at a time.

When there is no packet loss the speed is what I expect it to be:

$ speedtest-cli --share --server 6591
Retrieving speedtest.net configuration...
Testing from Cool Ideas Service Provider (Pty) Ltd (155.93.141.178)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Cool Ideas (Randburg) [9.68 km]: 10.275 ms
Testing download speed................................................................................
Download: 100.20 Mbit/s
Testing upload speed................................................................................................
Upload: 94.07 Mbit/s
Share results: http://www.speedtest.net/result/7113299920.png


Vumatel Aerial in Morningside.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X