Eish, spoke too soon, the problem seems to be back tonight, was better earlier today and now again spiking....
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be subscribing to the new Disney+ R49 streaming package?
Cool Ideas Fibre ISP - Feedback
- Thread starter paulosouthafrica
- Start date
- Status
Eish, spoke too soon, the problem seems to be back tonight, was better earlier today and now again spiking....
Received a welcome mail from Vuma and I see the status has now changed to "Pending ISP Activation".
My application reference is COOL-20180601-108365.
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
Are you back up?
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
Thanks connect will change the status.
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
Is it happening at peak times in General?
Zassie
Senior Member
- Joined
- Dec 10, 2011
- Messages
- 503
- Reaction score
- 272
I'd just like to throw this out here and show some love to Cool Ideas!
Yesterday i did a 12 hours twitch stream using the Cool Ideas Relay Server.
https://i.imgur.com/2tjt8V3.png
In the entire 12 hours there was only 9 minutes of any frame drops! That is absolutely amazing!
Thanks so much [MENTION=394133]PBCool[/MENTION] for sorting us out with that server! You are amazing!
Yesterday i did a 12 hours twitch stream using the Cool Ideas Relay Server.
https://i.imgur.com/2tjt8V3.png
In the entire 12 hours there was only 9 minutes of any frame drops! That is absolutely amazing!
Thanks so much [MENTION=394133]PBCool[/MENTION] for sorting us out with that server! You are amazing!
Ianf1
Expert Member
Hi Pbcool, we still have no internet. I did report this this morning. On following up I am told someone from Vumatel may phone me tomorrow as it is a physical thing. Is this the normal turnaround to expect from Vumatel/cool ideas? I have pmed the ticket number to you.
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
The targetted turnaround is 24-48hrs from Vumatels side. Also depending on workload.
yes it came up around 11
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
Cool it shouldn't happen again.
- Joined
- Jan 11, 2016
- Messages
- 16,421
- Reaction score
- 5,715
Great stuffI'm up with all 200Mbps, thanks
Kloon
Expert Member
Any known international issues? Not getting above 10Mbps to london on speed tests, tried different servers that in past has given me full line speeds. IPTV also buffering constantly, local tests run full, just international. This on a 100Mbps package.
[MENTION=394133]PBCool[/MENTION] - Could you please see what up with my ticket #COOL-20180618-113697
Last thing I heard from support that there are changes to be made, that was more than a week ago.
The issue has not improved in the slightest its actually worse
Last thing I heard from support that there are changes to be made, that was more than a week ago.
The issue has not improved in the slightest its actually worse
I also experienced a bit of packet loss locally as well as poor streaming quality from twitch last night.
I would also would like to know if there were any international issues.
I would also would like to know if there were any international issues.
Kloon
Expert Member
There were definitely some issue last night, redid speed tests this morning and all back to normal. Could perhaps also have been a capacity issue? [MENTION=394133]PBCool[/MENTION] any feedback on this?
I also noticed an an issue with international last night, speed was tanking even on a speedtest
e.g. http://www.speedtest.net/result/7455019465.png
On a different subject, PBCool could you please change the routing for aws ips in cape town so that it doesn't route through joburg? It seems to be routing that way with EU amazon ips, but US ones are still going through the lower latency path.
18.195.234.230, eu-west:
aws.amazon.com, us-east
e.g. http://www.speedtest.net/result/7455019465.png
On a different subject, PBCool could you please change the routing for aws ips in cape town so that it doesn't route through joburg? It seems to be routing that way with EU amazon ips, but US ones are still going through the lower latency path.
18.195.234.230, eu-west:
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 30 | 10 | 7 | 0 | 3 | 22 | 0 |
| 155.93.243.1 - 0 | 10 | 10 | 1 | 1 | 2 | 1 |
| 154.0.1.125 - 0 | 10 | 10 | 1 | 1 | 2 | 1 |
| 154.0.1.13 - 0 | 10 | 10 | 1 | 1 | 7 | 2 |
| 154.0.1.245 - 0 | 10 | 10 | 18 | 24 | 55 | 18 |
| 154.0.3.21 - 0 | 10 | 10 | 19 | 20 | 22 | 19 |
| 197.96.214.112 - 0 | 10 | 10 | 19 | 22 | 28 | 19 |
| 196.26.0.130 - 0 | 10 | 10 | 18 | 21 | 26 | 18 |
| 196-60-9-105.ixp.joburg - 0 | 10 | 10 | 21 | 23 | 30 | 25 |
| No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |
| 52.93.56.133 - 0 | 10 | 10 | 177 | 182 | 208 | 177 |
| 54.239.46.69 - 0 | 10 | 10 | 178 | 185 | 203 | 178 |
| 54.239.43.249 - 0 | 10 | 10 | 175 | 177 | 183 | 175 |
| No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |
| 54.239.107.44 - 0 | 10 | 10 | 177 | 179 | 182 | 179 |
| 54.239.107.33 - 0 | 10 | 10 | 174 | 178 | 198 | 198 |
| 54.239.107.32 - 0 | 10 | 10 | 176 | 181 | 196 | 177 |
| 54.239.107.51 - 0 | 10 | 10 | 176 | 184 | 198 | 176 |
| 52.93.23.126 - 0 | 10 | 10 | 175 | 177 | 181 | 176 |
| No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|aws.amazon.com, us-east
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 9 | 9 | 0 | 0 | 1 | 0 |
| 155.93.243.1 - 0 | 9 | 9 | 0 | 5 | 40 | 1 |
| 154.0.1.125 - 0 | 9 | 9 | 0 | 8 | 19 | 1 |
| 154.0.1.13 - 0 | 9 | 9 | 1 | 3 | 19 | 19 |
| 154.0.3.106 - 12 | 9 | 8 | 141 | 146 | 160 | 141 |
| v1000.core1.lon3.he.net - 0 | 8 | 8 | 141 | 150 | 178 | 142 |
| 100ge14-1.core1.lon2.he.net - 0 | 8 | 8 | 141 | 148 | 163 | 142 |
| 100ge13-2.core1.nyc4.he.net - 0 | 8 | 8 | 208 | 238 | 380 | 228 |
| 100ge16-1.core1.ash1.he.net - 0 | 8 | 8 | 217 | 271 | 359 | 218 |
| equinix02-iad2.amazon.com - 0 | 8 | 8 | 214 | 225 | 243 | 214 |
| 54.239.111.248 - 0 | 8 | 8 | 221 | 238 | 268 | 233 |
| 52.93.26.52 - 0 | 8 | 8 | 214 | 219 | 226 | 223 |
| 52.93.27.229 - 0 | 8 | 8 | 215 | 226 | 271 | 271 |
| 72.21.220.215 - 0 | 8 | 8 | 213 | 217 | 227 | 222 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 179 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 198 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 177 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 176 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 176 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| 52.46.133.33 - 0 | 8 | 8 | 213 | 222 | 233 | 229 |
|________________________________________________|______|______|______|______|______|______|
Last edited:
Tinuva
The Magician
Hmmm.
IS started advertising both AWS CPT and AWS JHB IP ranges according to my tests.
CPT to CPT:
Code:
root@fs1 ~ # mtr 52.46.40.1 --report-wide
Start: Mon Jul 9 09:25:18 2018
HOST: fs1.heaven.ctwug.za.net Loss% Snt Last Avg Best Wrst StDev
1.|-- router.heaven.za.net 0.0% 10 0.3 0.4 0.3 0.4 0.0
2.|-- 155.93.243.1 0.0% 10 1.1 14.3 1.1 131.5 41.2
3.|-- 154.0.1.125 0.0% 10 1.1 1.1 1.0 1.3 0.0
4.|-- 154.0.1.13 0.0% 10 1.3 1.4 1.2 1.6 0.0
5.|-- 154.0.1.61 0.0% 10 20.8 20.6 18.9 23.1 1.8
6.|-- ulx-cust.coolideas.co.za 0.0% 10 23.7 20.9 19.4 23.7 1.3
7.|-- 197.96.214.112 0.0% 10 21.1 20.3 18.9 21.5 0.9
8.|-- 196.26.0.66 0.0% 10 20.8 20.8 18.6 28.7 3.0
9.|-- 168.209.0.68 0.0% 10 21.0 20.1 18.9 21.4 0.8
10.|-- 168.209.2.130 0.0% 10 20.9 20.1 18.7 21.5 0.8
11.|-- 196-10-140-110.ixp.capetown 0.0% 10 20.8 19.9 18.4 21.5 1.0
12.|-- 52.93.57.26 0.0% 10 21.8 21.1 19.0 25.2 1.6
13.|-- 52.93.57.39 0.0% 10 20.9 20.4 18.7 22.0 0.9
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0CPT to JHB:
Code:
root@fs1 ~ # mtr 52.46.24.1 --report-wide
Start: Mon Jul 9 09:25:48 2018
HOST: fs1.heaven.ctwug.za.net Loss% Snt Last Avg Best Wrst StDev
1.|-- router.heaven.za.net 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 155.93.243.1 0.0% 10 1.1 1.2 1.1 1.4 0.0
3.|-- 154.0.1.125 0.0% 10 1.0 1.1 1.0 1.2 0.0
4.|-- 154.0.1.13 0.0% 10 1.3 1.7 1.3 4.7 1.0
5.|-- 154.0.1.61 0.0% 10 20.8 20.7 18.8 21.0 0.5
6.|-- 154.0.4.53 0.0% 10 23.7 22.2 19.1 24.0 1.4
7.|-- 197.96.214.112 0.0% 10 21.5 21.2 18.9 24.0 1.2
8.|-- pr2-pkl-xe-2-2-0.ip.isnet.net 0.0% 10 20.4 20.3 18.3 20.7 0.5
9.|-- 196-60-9-105.ixp.joburg 0.0% 10 25.0 23.2 21.1 25.0 0.7
10.|-- 52.93.56.104 0.0% 10 28.0 24.3 23.5 28.0 1.3
11.|-- 52.93.56.117 0.0% 10 23.5 23.6 21.6 24.5 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0Think a peering session for CPT would be nice now.
Tinuva
The Magician
At least there is this now:
Code:
root@fs1 ~ # mtr server-13-35-58-160.jnb50.r.cloudfront.net --report-wide
Start: Mon Jul 9 09:30:55 2018
HOST: fs1.heaven.ctwug.za.net Loss% Snt Last Avg Best Wrst StDev
1.|-- router.heaven.za.net 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- 155.93.243.1 0.0% 10 1.3 3.3 1.1 19.4 5.7
3.|-- 154.0.1.125 0.0% 10 1.2 1.1 1.1 1.2 0.0
4.|-- 154.0.1.13 0.0% 10 1.4 1.4 1.2 1.5 0.0
5.|-- 154.0.1.61 0.0% 10 21.1 20.1 18.9 21.1 0.9
6.|-- 154.0.4.53 0.0% 10 19.3 19.8 19.1 21.8 0.7
7.|-- 197.96.214.112 0.0% 10 19.2 19.1 18.8 19.2 0.0
8.|-- 196.26.0.130 0.0% 10 18.6 18.6 18.4 18.8 0.0
9.|-- 196-60-9-105.ixp.joburg 0.0% 10 21.2 22.6 20.9 32.0 3.4
10.|-- 52.93.56.104 0.0% 10 21.8 22.9 21.5 29.6 2.3
11.|-- 52.93.56.113 0.0% 10 21.6 21.7 21.3 22.2 0.0
12.|-- 52.93.56.249 0.0% 10 21.7 21.4 21.0 21.7 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- server-13-35-58-160.jnb50.r.cloudfront.net 0.0% 10 21.3 21.4 21.0 22.3 0.0- Status