Cool Ideas Fibre ISP - Feedback

[CRE4MPIE]

Can you post an MTR for me?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 3 | 37 | 36 | 0 | 0 | 0 | 0 |
| 154.0.0.113 - 3 | 37 | 36 | 0 | 2 | 4 | 2 |
| 154.0.4.193 - 3 | 37 | 36 | 0 | 1 | 3 | 2 |
| 154.0.2.33 - 3 | 37 | 36 | 0 | 2 | 6 | 1 |
| 154.0.2.114 - 3 | 37 | 36 | 0 | 2 | 26 | 2 |
| 154.0.4.46 - 3 | 37 | 36 | 0 | 4 | 42 | 3 |
| 154.0.1.106 - 3 | 37 | 36 | 0 | 174 | 205 | 164 |
| v1000.core1.lon3.he.net - 7 | 33 | 31 | 0 | 174 | 179 | 168 |
| 10ge3-1.core1.lon1.he.net - 0 | 36 | 36 | 165 | 177 | 200 | 165 |
| rt-lonap-b.thdo.bbc.co.uk - 0 | 36 | 36 | 165 | 175 | 203 | 165 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| ae0.er01.telhc.bbc.co.uk - 0 | 36 | 36 | 165 | 175 | 200 | 166 |
| 132.185.255.148 - 0 | 36 | 36 | 165 | 176 | 202 | 166 |
| bbc-vip113.telhc.bbc.co.uk - 0 | 36 | 36 | 165 | 175 | 204 | 165 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

[PBCool]

thanks.
is there maybe a different network i can get onto? MFN has not been great from the get go in my area.

Openserve a possibility?

 

[Furbz]

Ping has started…

PING 185.60.112.157 (185.60.112.157): 56 data bytes
64 bytes from 185.60.112.157: icmp_seq=0 ttl=245 time=257.093 ms
64 bytes from 185.60.112.157: icmp_seq=1 ttl=245 time=248.894 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=245 time=187.008 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=245 time=174.756 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=245 time=178.362 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=245 time=188.367 ms
64 bytes from 185.60.112.157: icmp_seq=6 ttl=245 time=187.604 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 185.60.112.157: icmp_seq=9 ttl=245 time=174.989 ms
64 bytes from 185.60.112.157: icmp_seq=10 ttl=245 time=176.338 ms
64 bytes from 185.60.112.157: icmp_seq=11 ttl=245 time=174.445 ms
64 bytes from 185.60.112.157: icmp_seq=12 ttl=245 time=175.687 ms




Ping has started…

PING www.bbc.net.uk (212.58.244.71): 56 data bytes
64 bytes from 212.58.244.71: icmp_seq=0 ttl=53 time=180.578 ms
64 bytes from 212.58.244.71: icmp_seq=1 ttl=53 time=192.610 ms
64 bytes from 212.58.244.71: icmp_seq=2 ttl=53 time=179.961 ms
64 bytes from 212.58.244.71: icmp_seq=3 ttl=53 time=179.605 ms
64 bytes from 212.58.244.71: icmp_seq=4 ttl=53 time=179.294 ms
64 bytes from 212.58.244.71: icmp_seq=5 ttl=53 time=181.013 ms
64 bytes from 212.58.244.71: icmp_seq=6 ttl=53 time=183.123 ms
64 bytes from 212.58.244.71: icmp_seq=7 ttl=53 time=169.012 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 212.58.244.71: icmp_seq=10 ttl=53 time=181.865 ms
64 bytes from 212.58.244.71: icmp_seq=11 ttl=53 time=182.424 ms
64 bytes from 212.58.244.71: icmp_seq=12 ttl=53 time=179.065 ms
64 bytes from 212.58.244.71: icmp_seq=13 ttl=53 time=181.668 ms
64 bytes from 212.58.244.71: icmp_seq=14 ttl=53 time=179.376 ms
64 bytes from 212.58.244.71: icmp_seq=15 ttl=53 time=173.115 ms
64 bytes from 212.58.244.71: icmp_seq=16 ttl=53 time=167.581 ms
64 bytes from 212.58.244.71: icmp_seq=17 ttl=53 time=168.718 ms
64 bytes from 212.58.244.71: icmp_seq=18 ttl=53 time=169.510 ms
64 bytes from 212.58.244.71: icmp_seq=19 ttl=53 time=180.753 ms
64 bytes from 212.58.244.71: icmp_seq=20 ttl=53 time=180.783 ms
64 bytes from 212.58.244.71: icmp_seq=21 ttl=53 time=179.860 ms

 

[PBCool]

Ping has started…

PING 185.60.112.157 (185.60.112.157): 56 data bytes
64 bytes from 185.60.112.157: icmp_seq=0 ttl=245 time=257.093 ms
64 bytes from 185.60.112.157: icmp_seq=1 ttl=245 time=248.894 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=245 time=187.008 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=245 time=174.756 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=245 time=178.362 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=245 time=188.367 ms
64 bytes from 185.60.112.157: icmp_seq=6 ttl=245 time=187.604 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 185.60.112.157: icmp_seq=9 ttl=245 time=174.989 ms
64 bytes from 185.60.112.157: icmp_seq=10 ttl=245 time=176.338 ms
64 bytes from 185.60.112.157: icmp_seq=11 ttl=245 time=174.445 ms
64 bytes from 185.60.112.157: icmp_seq=12 ttl=245 time=175.687 ms




Ping has started…

PING www.bbc.net.uk (212.58.244.71): 56 data bytes
64 bytes from 212.58.244.71: icmp_seq=0 ttl=53 time=180.578 ms
64 bytes from 212.58.244.71: icmp_seq=1 ttl=53 time=192.610 ms
64 bytes from 212.58.244.71: icmp_seq=2 ttl=53 time=179.961 ms
64 bytes from 212.58.244.71: icmp_seq=3 ttl=53 time=179.605 ms
64 bytes from 212.58.244.71: icmp_seq=4 ttl=53 time=179.294 ms
64 bytes from 212.58.244.71: icmp_seq=5 ttl=53 time=181.013 ms
64 bytes from 212.58.244.71: icmp_seq=6 ttl=53 time=183.123 ms
64 bytes from 212.58.244.71: icmp_seq=7 ttl=53 time=169.012 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 212.58.244.71: icmp_seq=10 ttl=53 time=181.865 ms
64 bytes from 212.58.244.71: icmp_seq=11 ttl=53 time=182.424 ms
64 bytes from 212.58.244.71: icmp_seq=12 ttl=53 time=179.065 ms
64 bytes from 212.58.244.71: icmp_seq=13 ttl=53 time=181.668 ms
64 bytes from 212.58.244.71: icmp_seq=14 ttl=53 time=179.376 ms
64 bytes from 212.58.244.71: icmp_seq=15 ttl=53 time=173.115 ms
64 bytes from 212.58.244.71: icmp_seq=16 ttl=53 time=167.581 ms
64 bytes from 212.58.244.71: icmp_seq=17 ttl=53 time=168.718 ms
64 bytes from 212.58.244.71: icmp_seq=18 ttl=53 time=169.510 ms
64 bytes from 212.58.244.71: icmp_seq=19 ttl=53 time=180.753 ms
64 bytes from 212.58.244.71: icmp_seq=20 ttl=53 time=180.783 ms
64 bytes from 212.58.244.71: icmp_seq=21 ttl=53 time=179.860 ms

You will notice more issues on higher latency links when there is congestion due to the retransmit time.

 

[Furbz]

You will notice more issues on higher latency links when there is congestion due to the retransmit time.

local midrand based speedtests are turning up 5-15mbps download speeds.
then sometime i get a perfect 25/25.

Ping has started…

PING www.cisp.co.za (154.0.13.95): 56 data bytes
64 bytes from 154.0.13.95: icmp_seq=0 ttl=58 time=39.418 ms
64 bytes from 154.0.13.95: icmp_seq=1 ttl=58 time=45.071 ms
64 bytes from 154.0.13.95: icmp_seq=2 ttl=58 time=42.686 ms
64 bytes from 154.0.13.95: icmp_seq=3 ttl=58 time=44.927 ms
64 bytes from 154.0.13.95: icmp_seq=4 ttl=58 time=40.075 ms
64 bytes from 154.0.13.95: icmp_seq=5 ttl=58 time=33.001 ms
64 bytes from 154.0.13.95: icmp_seq=6 ttl=58 time=5.498 ms
64 bytes from 154.0.13.95: icmp_seq=7 ttl=58 time=5.922 ms
64 bytes from 154.0.13.95: icmp_seq=8 ttl=58 time=5.439 ms
64 bytes from 154.0.13.95: icmp_seq=9 ttl=58 time=6.698 ms
64 bytes from 154.0.13.95: icmp_seq=10 ttl=58 time=6.039 ms
64 bytes from 154.0.13.95: icmp_seq=11 ttl=58 time=5.870 ms
64 bytes from 154.0.13.95: icmp_seq=12 ttl=58 time=5.943 ms
64 bytes from 154.0.13.95: icmp_seq=13 ttl=58 time=4.473 ms
64 bytes from 154.0.13.95: icmp_seq=14 ttl=58 time=5.402 ms
64 bytes from 154.0.13.95: icmp_seq=15 ttl=58 time=18.328 ms
64 bytes from 154.0.13.95: icmp_seq=16 ttl=58 time=5.040 ms
64 bytes from 154.0.13.95: icmp_seq=17 ttl=58 time=16.764 ms
64 bytes from 154.0.13.95: icmp_seq=18 ttl=58 time=11.689 ms
64 bytes from 154.0.13.95: icmp_seq=19 ttl=58 time=5.482 ms
64 bytes from 154.0.13.95: icmp_seq=20 ttl=58 time=8.238 ms
64 bytes from 154.0.13.95: icmp_seq=21 ttl=58 time=5.311 ms
64 bytes from 154.0.13.95: icmp_seq=22 ttl=58 time=5.515 ms
64 bytes from 154.0.13.95: icmp_seq=23 ttl=58 time=4.967 ms
64 bytes from 154.0.13.95: icmp_seq=24 ttl=58 time=5.542 ms
64 bytes from 154.0.13.95: icmp_seq=25 ttl=58 time=5.595 ms
64 bytes from 154.0.13.95: icmp_seq=26 ttl=58 time=9.211 ms
64 bytes from 154.0.13.95: icmp_seq=27 ttl=58 time=7.353 ms
64 bytes from 154.0.13.95: icmp_seq=28 ttl=58 time=5.314 ms

 

[PBCool]

local midrand based speedtests are turning up 5-15mbps download speeds.
then sometime i get a perfect 25/25.

Ping has started…

PING www.cisp.co.za (154.0.13.95): 56 data bytes
64 bytes from 154.0.13.95: icmp_seq=0 ttl=58 time=39.418 ms
64 bytes from 154.0.13.95: icmp_seq=1 ttl=58 time=45.071 ms
64 bytes from 154.0.13.95: icmp_seq=2 ttl=58 time=42.686 ms
64 bytes from 154.0.13.95: icmp_seq=3 ttl=58 time=44.927 ms
64 bytes from 154.0.13.95: icmp_seq=4 ttl=58 time=40.075 ms
64 bytes from 154.0.13.95: icmp_seq=5 ttl=58 time=33.001 ms
64 bytes from 154.0.13.95: icmp_seq=6 ttl=58 time=5.498 ms
64 bytes from 154.0.13.95: icmp_seq=7 ttl=58 time=5.922 ms
64 bytes from 154.0.13.95: icmp_seq=8 ttl=58 time=5.439 ms
64 bytes from 154.0.13.95: icmp_seq=9 ttl=58 time=6.698 ms
64 bytes from 154.0.13.95: icmp_seq=10 ttl=58 time=6.039 ms
64 bytes from 154.0.13.95: icmp_seq=11 ttl=58 time=5.870 ms
64 bytes from 154.0.13.95: icmp_seq=12 ttl=58 time=5.943 ms
64 bytes from 154.0.13.95: icmp_seq=13 ttl=58 time=4.473 ms
64 bytes from 154.0.13.95: icmp_seq=14 ttl=58 time=5.402 ms
64 bytes from 154.0.13.95: icmp_seq=15 ttl=58 time=18.328 ms
64 bytes from 154.0.13.95: icmp_seq=16 ttl=58 time=5.040 ms
64 bytes from 154.0.13.95: icmp_seq=17 ttl=58 time=16.764 ms
64 bytes from 154.0.13.95: icmp_seq=18 ttl=58 time=11.689 ms
64 bytes from 154.0.13.95: icmp_seq=19 ttl=58 time=5.482 ms
64 bytes from 154.0.13.95: icmp_seq=20 ttl=58 time=8.238 ms
64 bytes from 154.0.13.95: icmp_seq=21 ttl=58 time=5.311 ms
64 bytes from 154.0.13.95: icmp_seq=22 ttl=58 time=5.515 ms
64 bytes from 154.0.13.95: icmp_seq=23 ttl=58 time=4.967 ms
64 bytes from 154.0.13.95: icmp_seq=24 ttl=58 time=5.542 ms
64 bytes from 154.0.13.95: icmp_seq=25 ttl=58 time=5.595 ms
64 bytes from 154.0.13.95: icmp_seq=26 ttl=58 time=9.211 ms
64 bytes from 154.0.13.95: icmp_seq=27 ttl=58 time=7.353 ms
64 bytes from 154.0.13.95: icmp_seq=28 ttl=58 time=5.314 ms

Yeap exactly

 

[duanesf]

Any clarity on the issue? I eventually just packed up as gaming was too frustrating with that much packet loss and latency issues

 

[zolly]

Any clarity on the issue? I eventually just packed up as gaming was too frustrating with that much packet loss and latency issues

I have had gaming issues since Thursday/Friday, but we're still testing our side as to what might be causing the random jitter/lag spikes on our line. They don't make games unplayable, but happen often enough to be frustrating.

I ran winMTR over the weekend and it seems to be originating from the TP LINK router that was supplied by CI (usually the spikes first appear around the fourth hop which is in the UK, but not long after that we also see our ping to our router shoot from 1 to a max of 33 ms, which in my mind, indicates that the router may be having issues).

The less likely cause is that it might also be due to Octotel messing something up when they came to do additional installs in our complex on Thursday, since prior to this we had no issues. Our own higher grade router will be arriving today, so we'll be testing that out to see if it eliminates the issue. If not I'll be following up with [MENTION=394133]PBCool[/MENTION] tomorrow.

 

[duanesf]

When I say unplayable it’s because I am a sore loser and hate being shot in the face a lot because I’m lagging.

I have an ASUS RT-AC87U router and an Ethernet connection - I dont think the issue is domestic in my case.

 

[PBCool]

When I say unplayable it’s because I am a sore loser and hate being shot in the face a lot because I’m lagging.

I have an ASUS RT-AC87U router and an Ethernet connection - I dont think the issue is domestic in my case.

Which fibre network also MFN?

 

[PBCool]

I have had gaming issues since Thursday/Friday, but we're still testing our side as to what might be causing the random jitter/lag spikes on our line. They don't make games unplayable, but happen often enough to be frustrating.

I ran winMTR over the weekend and it seems to be originating from the TP LINK router that was supplied by CI (usually the spikes first appear around the fourth hop which is in the UK, but not long after that we also see our ping to our router shoot from 1 to a max of 33 ms, which in my mind, indicates that the router may be having issues).

The less likely cause is that it might also be due to Octotel messing something up when they came to do additional installs in our complex on Thursday, since prior to this we had no issues. Our own higher grade router will be arriving today, so we'll be testing that out to see if it eliminates the issue. If not I'll be following up with [MENTION=394133]PBCool[/MENTION] tomorrow.

Why not bypass the router and test?

 

[duanesf]

Vumatel. 100/100, Sandton

 

[zolly]

Why not bypass the router and test?

I can't believe I didn't think of that... I'm so used to an ADSL setup... and I had my work laptop at home the whole weekend. Oh well, I'll do some direct testing tonight. And with the new router.

 

[PBCool]

Vumatel. 100/100, Sandton

There was the blip for a few mins, as per the post, did you continue to have issues?

 

[Yster21]

Regarding the issues last night, I don't have any logs but can only comment on what it was like whilst playing WoW.

We had a raid that started at 5pm. From the start at 5pm, my latency was sitting around 230-260ms, as compared to the usual 176ms (176 is the exact value it stays at if all is well). From there, the latency gradually got worse at the evening progressed, sitting around 400ms+ just before the crap hit the fan at 8.10pm. From there, I was sitting at 16,000ms for a long time before it started dropping again.

At no point whatsoever did the connection "normalise". It was still laggy, with seemingly lots of dropped packets.

This was on Vuma Aerial.

 

[duanesf]

I tried playing until 9pm or so and then gave up. It didn’t improve at all.

I did note increasing issues leading up to this weekend. Speed was lower than normal (you guys usually deliver at least a 95/95 but I was getting around 60/80. But the biggest issue was variable latency.

To be honest I thought it could be the BF1 servers but seems others had similar issues

 

[PBCool]

I tried playing until 9pm or so and then gave up. It didn’t improve at all.

I did note increasing issues leading up to this weekend. Speed was lower than normal (you guys usually deliver at least a 95/95 but I was getting around 60/80. But the biggest issue was variable latency.

To be honest I thought it could be the BF1 servers but seems others had similar issues

If you are using a cabled connection and getting those throughputs then something else is wrong. And if it was over wireless that is more than likely a contributor.

 

[PBCool]

Regarding the issues last night, I don't have any logs but can only comment on what it was like whilst playing WoW.

We had a raid that started at 5pm. From the start at 5pm, my latency was sitting around 230-260ms, as compared to the usual 176ms (176 is the exact value it stays at if all is well). From there, the latency gradually got worse at the evening progressed, sitting around 400ms+ just before the crap hit the fan at 8.10pm. From there, I was sitting at 16,000ms for a long time before it started dropping again.

At no point whatsoever did the connection "normalise". It was still laggy, with seemingly lots of dropped packets.

This was on Vuma Aerial.

Thanks for the feedback, please try it again this evening and let me know? We will need to take it up with Vumatel if it continues.

 

[SpiderGear]

Well that's interesting as we have been getting random reports from all over, I will do some further diagnosis on where the streams source from. I doubt it's all from a single cluster.

Any feedback on this? DSTV Now was mostly useless over the weekend. Downloading was really slow..

 

[PBCool]

Any feedback on this? DSTV Now was mostly useless over the weekend. Downloading was really slow..

Are you in JHB or CPT?