Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
Neet said:
sorry, should have clarified, not related to tik speedtest for that post, but the image does explain. This is with download client I'm currently using for a game.
Click to expand...
Game downloads aren't as simple, often they get cached locally on Akamai and sometimes they don't have you had a look what the source IP is each time?
 
Neet said:
With windows; View attachment 492376

with a VM running RouterOS:View attachment 492380
Click to expand...

2 <1 ms <1 ms <1 ms 154.0.14.25
3 <1 ms <1 ms <1 ms uo1-cust.coolideas.co.za [154.0.3.97]
4 1 ms <1 ms <1 ms 154.0.2.173
5 1 ms <1 ms <1 ms 154.0.2.114
6 1 ms <1 ms <1 ms 154.0.1.206
7 1 ms <1 ms 1 ms uoe-cust.coolideas.co.za [154.0.3.110]
8 159 ms 159 ms 159 ms 154.0.1.222
9 176 ms 161 ms 162 ms v1000.core1.lon3.he.net [216.66.80.169]
10 163 ms 193 ms 186 ms 100ge14-1.core1.lon2.he.net [184.105.64.237]
11 235 ms 226 ms 229 ms 100ge4-1.core1.nyc4.he.net [72.52.92.166]
12 232 ms 232 ms 232 ms comcast-7922-as7922.10gigabitethernet7.switch1.nyc7.he.net [209.51.181.14]
13 239 ms 238 ms 236 ms be-10390-cr02.newyork.ny.ibone.comcast.net [68.86.83.89]
14 250 ms 251 ms 251 ms be-10305-cr02.350ecermak.il.ibone.comcast.net [68.86.85.202]
15 270 ms 272 ms 271 ms be-10517-cr02.denver.co.ibone.comcast.net [68.86.85.170]
16 276 ms 276 ms 276 ms be-11721-cr02.1601milehigh.co.ibone.comcast.net [68.86.86.78]
17 311 ms 311 ms 312 ms be-11021-cr02.sunnyvale.ca.ibone.comcast.net [68.86.86.65]
18 307 ms 307 ms 307 ms be-11025-cr01.9greatoaks.ca.ibone.comcast.net [68.86.87.158]
19 311 ms 311 ms 314 ms ae-79-ar01.sacramento.ca.ccal.comcast.net [68.86.93.26]
20 325 ms 325 ms 325 ms ae-2-rur02.sacramento.ca.ccal.comcast.net [162.151.18.134]
21 321 ms 321 ms 321 ms ae-3-sur03.sacramento.ca.ccal.comcast.net [68.87.212.6]
22 312 ms 312 ms 312 ms ae-1-sur02.sacramento.ca.ccal.comcast.net [68.87.200.66]
23 329 ms 328 ms 329 ms 50-235-23-218-static.hfc.comcastbusiness.net [50.235.23.218]

Trace complete.

Your server is quite far away, west coast Sacramento. The TCP window would need to scale for a long period of time for a single thread.
 
Some frustrating packetloss on the coolideas network. Capetown vumatel coolideas.

The packetloss seems to occur from coolideas peering onwards. It was much worse an hour ago then went away and now it is slowly creeping up with higher and higher packetloss making any reliable streaming jittery and buffering every couple of seconds.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 803 | 803 | 0 | 0 | 8 | 0 |
| 155.93.251.1 - 1 | 799 | 798 | 1 | 4 | 188 | 1 |
| c3h-backbone.coolideas.co.za - 0 | 803 | 803 | 0 | 1 | 20 | 1 |
| cd-backbone.coolideas.co.za - 3 | 732 | 715 | 1 | 2 | 17 | 11 |
| c6t-backbone.coolideas.co.za - 5 | 690 | 662 | 20 | 22 | 42 | 30 |
| c3x-backbone.coolideas.co.za - 4 | 707 | 684 | 20 | 22 | 35 | 29 |
| google.ixp.joburg - 3 | 715 | 694 | 21 | 23 | 180 | 29 |
| 72.14.239.129 - 4 | 695 | 669 | 21 | 22 | 68 | 30 |
| jnb01s08-in-f14.1e100.net - 4 | 710 | 687 | 21 | 22 | 180 | 31 |
|________________________________________________|______|______|______|______|______|______|
 
John Tempus said:
Some frustrating packetloss on the coolideas network. Capetown vumatel coolideas.

The packetloss seems to occur from coolideas peering onwards. It was much worse an hour ago then went away and now it is slowly creeping up with higher and higher packetloss making any reliable streaming jittery and buffering every couple of seconds.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 803 | 803 | 0 | 0 | 8 | 0 |
| 155.93.251.1 - 1 | 799 | 798 | 1 | 4 | 188 | 1 |
| c3h-backbone.coolideas.co.za - 0 | 803 | 803 | 0 | 1 | 20 | 1 |
| cd-backbone.coolideas.co.za - 3 | 732 | 715 | 1 | 2 | 17 | 11 |
| c6t-backbone.coolideas.co.za - 5 | 690 | 662 | 20 | 22 | 42 | 30 |
| c3x-backbone.coolideas.co.za - 4 | 707 | 684 | 20 | 22 | 35 | 29 |
| google.ixp.joburg - 3 | 715 | 694 | 21 | 23 | 180 | 29 |
| 72.14.239.129 - 4 | 695 | 669 | 21 | 22 | 68 | 30 |
| jnb01s08-in-f14.1e100.net - 4 | 710 | 687 | 21 | 22 | 180 | 31 |
|________________________________________________|______|______|______|______|______|______|
Click to expand...
Remember Vumatel Cape Town has a congestion issue on their router and the upgrade is happening on the 30th?
 
Also having issues in Cape Town Northerns Subs. Vumatel in Uitzicht. New installation.

Problem only started a few hours ago.

1. Speedtest is not as crisps as it normall is.

To VOX Telecoms it's normally 100Mbps+ up/down with 1ms ping:

Now it looks like this:


2. Fast.com use to show close to 100Mbps

Now it's this:

cisp1.png

3. On Teamspeak my ping is normally 19ms with a jitter of 0.something, now it's 80ms to 99ms with jitter ranging all over the place from 4 to 9.9.

4. IPTV Streaming YouTube and similar use to work with out issues. Now it buffers and in some cases just disconnects.

Other tests:

Ping to google .co.za

PS C:\WINDOWS\system32> ping google.co.za -t

Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=89ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=91ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=86ms TTL=56
Reply from 216.58.223.3: bytes=32 time=93ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=111ms TTL=56
Reply from 216.58.223.3: bytes=32 time=96ms TTL=56
Reply from 216.58.223.3: bytes=32 time=90ms TTL=56
Reply from 216.58.223.3: bytes=32 time=242ms TTL=56

Ping statistics for 216.58.223.3:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 242ms, Average = 104ms

Tracert to google.co.za

PS C:\WINDOWS\system32> tracert google.co.za

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

1 <1 ms <1 ms <1 ms DSL-AC55U [172.26.24.4]
2 30 ms 31 ms 30 ms 155.93.***.*
3 67 ms 72 ms 83 ms c3h-backbone.coolideas.co.za [154.0.1.125]
4 76 ms 72 ms 75 ms cd-backbone.coolideas.co.za [154.0.1.13]
5 103 ms 106 ms 106 ms c6t-backbone.coolideas.co.za [154.0.1.245]
6 109 ms 117 ms 102 ms c3x-backbone.coolideas.co.za [154.0.1.141]
7 98 ms 99 ms 102 ms google.ixp.joburg [196.60.8.166]
8 106 ms 107 ms 103 ms 72.14.237.239
9 113 ms 108 ms 97 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

All the above test was done via 1Gbps ethernet connection. I gave rebooted the Fibre box and router numerous times, but it didn't help.

Looks like there is a 30ms delay early in the tracert and just escalates from there.

@PBCool, anything else I can do?
 

Attachments

  • cisp2.png
    cisp2.png
    45.3 KB · Views: 186
Hunted said:
Also having issues in Cape Town Northerns Subs. Vumatel in Uitzicht. New installation.

Problem only started a few hours ago.

1. Speedtest is not as crisps as it normall is.

To VOX Telecoms it's normally 100Mbps+ up/down with 1ms ping:

Now it looks like this:


2. Fast.com use to show close to 100Mbps

Now it's this:

View attachment 492508

3. On Teamspeak my ping is normally 19ms with a jitter of 0.something, now it's 80ms to 99ms with jitter ranging all over the place from 4 to 9.9.

4. IPTV Streaming YouTube and similar use to work with out issues. Now it buffers and in some cases just disconnects.

Other tests:

Ping to google .co.za

PS C:\WINDOWS\system32> ping google.co.za -t

Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=89ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=91ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=86ms TTL=56
Reply from 216.58.223.3: bytes=32 time=93ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=111ms TTL=56
Reply from 216.58.223.3: bytes=32 time=96ms TTL=56
Reply from 216.58.223.3: bytes=32 time=90ms TTL=56
Reply from 216.58.223.3: bytes=32 time=242ms TTL=56

Ping statistics for 216.58.223.3:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 242ms, Average = 104ms

Tracert to google.co.za

PS C:\WINDOWS\system32> tracert google.co.za

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

1 <1 ms <1 ms <1 ms DSL-AC55U [172.26.24.4]
2 30 ms 31 ms 30 ms 155.93.***.*
3 67 ms 72 ms 83 ms c3h-backbone.coolideas.co.za [154.0.1.125]
4 76 ms 72 ms 75 ms cd-backbone.coolideas.co.za [154.0.1.13]
5 103 ms 106 ms 106 ms c6t-backbone.coolideas.co.za [154.0.1.245]
6 109 ms 117 ms 102 ms c3x-backbone.coolideas.co.za [154.0.1.141]
7 98 ms 99 ms 102 ms google.ixp.joburg [196.60.8.166]
8 106 ms 107 ms 103 ms 72.14.237.239
9 113 ms 108 ms 97 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

All the above test was done via 1Gbps ethernet connection. I gave rebooted the Fibre box and router numerous times, but it didn't help.

Looks like there is a 30ms delay early in the tracert and just escalates from there.

@PBCool, anything else I can do?
Click to expand...
Nope unfortunately not, as mentioned Vumatels router gets congested at peak times Sunday being the busiest time of the network is the most impacted. They are upgrading it on the 30th.
 
PBCool said:
Nope unfortunately not, as mentioned Vumatels router gets congested at peak times Sunday being the busiest time of the network is the most impacted. They are upgrading it on the 30th.
Click to expand...

Cape Town just can't catch a break... first the water, now the internet. Maybe the electricity is next.
 
PBCool said:
Nope unfortunately not, as mentioned Vumatels router gets congested at peak times Sunday being the busiest time of the network is the most impacted. They are upgrading it on the 30th.
Click to expand...

sigh .. will see how things looks like tomorrow then.. Haven't experienced this yet in the 4 weeks I have been on Fiber. My 2 cents added nether the less.
 
Hunted said:
Also having issues in Cape Town Northerns Subs. Vumatel in Uitzicht. New installation.

Problem only started a few hours ago.

1. Speedtest is not as crisps as it normall is.

To VOX Telecoms it's normally 100Mbps+ up/down with 1ms ping:

Now it looks like this:


2. Fast.com use to show close to 100Mbps

Now it's this:

View attachment 492508

3. On Teamspeak my ping is normally 19ms with a jitter of 0.something, now it's 80ms to 99ms with jitter ranging all over the place from 4 to 9.9.

4. IPTV Streaming YouTube and similar use to work with out issues. Now it buffers and in some cases just disconnects.

Other tests:

Ping to google .co.za

PS C:\WINDOWS\system32> ping google.co.za -t

Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=89ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=91ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=86ms TTL=56
Reply from 216.58.223.3: bytes=32 time=93ms TTL=56
Reply from 216.58.223.3: bytes=32 time=87ms TTL=56
Reply from 216.58.223.3: bytes=32 time=101ms TTL=56
Reply from 216.58.223.3: bytes=32 time=97ms TTL=56
Reply from 216.58.223.3: bytes=32 time=111ms TTL=56
Reply from 216.58.223.3: bytes=32 time=96ms TTL=56
Reply from 216.58.223.3: bytes=32 time=90ms TTL=56
Reply from 216.58.223.3: bytes=32 time=242ms TTL=56

Ping statistics for 216.58.223.3:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 242ms, Average = 104ms

Tracert to google.co.za

PS C:\WINDOWS\system32> tracert google.co.za

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

1 <1 ms <1 ms <1 ms DSL-AC55U [172.26.24.4]
2 30 ms 31 ms 30 ms 155.93.***.*
3 67 ms 72 ms 83 ms c3h-backbone.coolideas.co.za [154.0.1.125]
4 76 ms 72 ms 75 ms cd-backbone.coolideas.co.za [154.0.1.13]
5 103 ms 106 ms 106 ms c6t-backbone.coolideas.co.za [154.0.1.245]
6 109 ms 117 ms 102 ms c3x-backbone.coolideas.co.za [154.0.1.141]
7 98 ms 99 ms 102 ms google.ixp.joburg [196.60.8.166]
8 106 ms 107 ms 103 ms 72.14.237.239
9 113 ms 108 ms 97 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

All the above test was done via 1Gbps ethernet connection. I gave rebooted the Fibre box and router numerous times, but it didn't help.

Looks like there is a 30ms delay early in the tracert and just escalates from there.

@PBCool, anything else I can do?
Click to expand...

I'm in Uitzicht too, different ISP and exactly the same thing. So not a CoolIdeas issue, but a VumaTel issue.

As noted the 30th they (Vumatel ) will be doing an upgrade to the router.
 
Next time people give OS a hard time for using GPON, remember that not even Vuma Trenched is immune to piss poor planning.

CISP going like a rabbit on blue chip cocaine in JHB :p
 
Waylander said:
Next time people give OS a hard time for using GPON, remember that not even Vuma Trenched is immune to piss poor planning.

CISP going like a rabbit on blue chip cocaine in JHB :p
Click to expand...

Every network has it's issues at some point in time, it's how those issues are managed and resolved is what defines the company IMO.

In terms of OS running on GPON, There are many contributing factors as to why people perceive OS performance levels as not being as good as Vumatel for example.

One of the other factors being IPC and the management/implementation of it.
 
ghostR said:
One of the other factors being IPC and the management/implementation of it.
Click to expand...

sure that may taint the perception but i'm speaking about the network infra in an objective sense

but then again some isps use netgear hardware :crylaugh:
 
Mornings,

Looks like the pings are back to normal this morning...

Speedtest to Vox is weird though.



Hope the upgrade on the 30th sorts this issues out.
 
Again

PlatinumWealth_mini.png
traceroute to 154.0.1.214 (154.0.1.214), 30 hops max, 60 byte packets
1 155.93.152.1 (155.93.152.1) 0.968 ms 0.943 ms 0.986 ms
2 uo1-cust.coolideas.co.za (154.0.3.97) 0.936 ms 1.040 ms 1.096 ms
3 154.0.2.1 (154.0.2.1) 0.980 ms 1.035 ms 1.082 ms
4 c3p-backbone.coolideas.co.za (154.0.2.133) 1.210 ms 1.212 ms 1.258 ms
5 uoe-cust.coolideas.co.za (154.0.3.110) 1.833 ms 1.835 ms 1.886 ms
6 c5y-backbone.coolideas.co.za (154.0.1.214) 160.113 ms 159.027 ms 159.009 ms
Click to expand...

CISPLondon_mini.png
traceroute to platinumwealth.co.za (104.31.88.216), 30 hops max, 60 byte packets
1 155.93.152.1 (155.93.152.1) 0.878 ms 0.910 ms 0.962 ms
2 uo1-cust.coolideas.co.za (154.0.3.97) 0.796 ms 0.895 ms 0.949 ms
3 c3p-backbone.coolideas.co.za (154.0.2.133) 0.779 ms 0.837 ms 0.836 ms
4 c1-backbone.coolideas.co.za (154.0.2.1) 0.985 ms 0.985 ms 1.035 ms
5 197.96.214.112 (197.96.214.112) 2.013 ms 2.013 ms 2.066 ms
6 168.209.0.68 (168.209.0.68) 17.422 ms 16.668 ms 16.665 ms
7 168.209.2.130 (168.209.2.130) 17.615 ms 17.624 ms 18.062 ms
8 196-10-140-198.ixp.capetown (196.10.140.198) 16.579 ms 16.602 ms 16.603 ms
9 104.31.88.216 (104.31.88.216) 16.424 ms 16.438 ms 16.440 ms
Click to expand...

Amazon_mini.png
traceroute to amazon.com (176.32.103.205), 30 hops max, 60 byte packets
1 155.93.152.1 (155.93.152.1) 0.814 ms 0.799 ms 0.852 ms
2 uo1-cust.coolideas.co.za (154.0.3.97) 0.843 ms 0.844 ms 0.894 ms
3 c1-backbone.coolideas.co.za (154.0.2.1) 0.887 ms 0.944 ms 0.943 ms
4 c3p-backbone.coolideas.co.za (154.0.2.133) 0.992 ms 1.103 ms 1.102 ms
5 uoi-cust.coolideas.co.za (154.0.3.114) 1.722 ms 1.721 ms 1.761 ms
6 c2y-backbone.coolideas.co.za (154.0.1.106) 162.815 ms 161.818 ms 161.827 ms
7 v1000.core1.lon3.he.net (216.66.80.169) 161.023 ms 161.007 ms 161.010 ms
8 100ge14-1.core1.lon2.he.net (184.105.64.237) 159.751 ms 159.785 ms 159.787 ms
9 100ge4-1.core1.nyc4.he.net (72.52.92.166) 227.329 ms 227.340 ms 227.383 ms
10 100ge8-1.core1.nyc6.he.net (184.105.64.178) 234.247 ms 234.458 ms 234.459 ms
11 de-cix.nyc.amazon.com (206.130.10.99) 227.916 ms 227.922 ms 228.061 ms
12 52.93.1.71 (52.93.1.71) 234.227 ms 239.319 ms 239.314 ms
13 52.93.1.54 (52.93.1.54) 229.134 ms 229.229 ms 229.228 ms
14 * * *
15 54.239.109.130 (54.239.109.130) 254.183 ms 254.206 ms 254.208 ms
16 54.239.111.117 (54.239.111.117) 235.963 ms 235.973 ms 236.234 ms
17 205.251.244.236 (205.251.244.236) 234.914 ms 234.959 ms 234.953 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 176.32.103.205 (176.32.103.205) 233.110 ms 233.140 ms 232.664 ms
Click to expand...
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X