Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
@PBCool Since 11PM last night my ONT is showing a solid red light on the alarm which according to the manual means there is a major problem? This is on Vumatel Aerial in Radiokop, Roodepoort
 
Thanks PBCool but that doesn't make me feel any better, that's two month of unusable internet in the evenings and weekends yet I'm paying Cool Ideas R1000 per month, shouldn't the customers in North Riding all get refunded? And sometime this month doesn't help me, April just started and I pay you guys, not Evotel....
 
Arno4Jackie said:
@PBCool Since 11PM last night my ONT is showing a solid red light on the alarm which according to the manual means there is a major problem? This is on Vumatel Aerial in Radiokop, Roodepoort
Click to expand...
Could mean a few things, just log the line fault with us.
 
Zodiak said:
Thanks PBCool but that doesn't make me feel any better, that's two month of unusable internet in the evenings and weekends yet I'm paying Cool Ideas R1000 per month, shouldn't the customers in North Riding all get refunded? And sometime this month doesn't help me, April just started and I pay you guys, not Evotel....
Click to expand...
I can understand as much and we are busy dealing with Evotel on this, we also have to pay Evotel in full regardless of this.
 
DJZassie said:
Not peak time atm, so will get back to you on that one :)
Click to expand...

So last night was MILES better than the previous evenings! Still one or two hicups where i would lose throughput for a few minutes, but muuuuuch better than the usual constant lack of throughput!
 
Connection is restored \o/. Cool Ideas got me back up and running within 5 minutes once Vumatel patched the line. :)
 
DJZassie said:
So last night was MILES better than the previous evenings! Still one or two hicups where i would lose throughput for a few minutes, but muuuuuch better than the usual constant lack of throughput!
Click to expand...

Glad to hear it, we are applying for a direct connect in CT as well.
 
PBcool, Any ideas why we would be getting this failure: (We cannot get the website rcp.axxess.co.za on CI Fibre if we failover to Telkom LTE then it works fine? - It was working perfectly up till 2 days ago.)
See all trace routes below. Sorry for this post here, your call center was unable to assist us.

Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert rcp.axxess.co.za

Tracing route to rcp.axxess.co.za [196.30.251.180]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 4 ms 2 ms 3 ms 155.93.141.1
3 4 ms 3 ms 2 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 4 ms 4 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 2 ms c3u-backbone.coolideas.co.za [154.0.1.138]
6 171 ms 176 ms 171 ms 197.96.214.112
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\WINDOWS\system32>tracert ccp.axxess.co.za

Tracing route to ccp.axxess.co.za [196.30.251.179]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 7 ms 4 ms 5 ms 155.93.141.1
3 3 ms 3 ms 3 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 4 ms 3 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 5 ms c36-backbone.coolideas.co.za [154.0.2.114]
6 171 ms 171 ms 172 ms 197.96.214.112
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 ^C
C:\WINDOWS\system32>ping 197.96.214.112

Pinging 197.96.214.112 with 32 bytes of data:
Reply from 197.96.214.112: bytes=32 time=175ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244

Ping statistics for 197.96.214.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 175ms, Average = 172ms

C:\WINDOWS\system32>ping -a 197.96.214.112

Pinging 197.96.214.112 with 32 bytes of data:
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=170ms TTL=244
Reply from 197.96.214.112: bytes=32 time=174ms TTL=244
Reply from 197.96.214.112: bytes=32 time=170ms TTL=244

Ping statistics for 197.96.214.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 174ms, Average = 171ms


C:\WINDOWS\system32>tracert 197.96.214.112

Tracing route to 197.96.214.112 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.254
2 6 ms 2 ms 3 ms 155.93.141.1
3 6 ms 4 ms 5 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 3 ms 3 ms 4 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 3 ms c3u-backbone.coolideas.co.za [154.0.1.138]
6 171 ms 172 ms 172 ms 197.96.214.112

Trace complete.

C:\WINDOWS\system32>tracert axxess.co.za

Tracing route to axxess.co.za [197.96.139.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 5 ms 3 ms 3 ms 155.93.141.1
3 3 ms 2 ms 2 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 8 ms 3 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 4 ms 3 ms 2 ms c36-backbone.coolideas.co.za [154.0.2.114]
6 173 ms 171 ms 170 ms 197.96.214.112
7 171 ms 171 ms 171 ms 168.209.1.165
8 171 ms 171 ms 171 ms 168.209.0.186
9 170 ms 170 ms 171 ms 197.96.94.126
10 161 ms 161 ms 162 ms 197.96.139.133

Trace complete.
 
David said:
PBcool, Any ideas why we would be getting this failure: (We cannot get the website rcp.axxess.co.za on CI Fibre if we failover to Telkom LTE then it works fine? - It was working perfectly up till 2 days ago.)
See all trace routes below. Sorry for this post here, your call center was unable to assist us.

Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert rcp.axxess.co.za

Tracing route to rcp.axxess.co.za [196.30.251.180]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 4 ms 2 ms 3 ms 155.93.141.1
3 4 ms 3 ms 2 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 4 ms 4 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 2 ms c3u-backbone.coolideas.co.za [154.0.1.138]
6 171 ms 176 ms 171 ms 197.96.214.112
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\WINDOWS\system32>tracert ccp.axxess.co.za

Tracing route to ccp.axxess.co.za [196.30.251.179]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 7 ms 4 ms 5 ms 155.93.141.1
3 3 ms 3 ms 3 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 4 ms 3 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 5 ms c36-backbone.coolideas.co.za [154.0.2.114]
6 171 ms 171 ms 172 ms 197.96.214.112
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 ^C
C:\WINDOWS\system32>ping 197.96.214.112

Pinging 197.96.214.112 with 32 bytes of data:
Reply from 197.96.214.112: bytes=32 time=175ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244

Ping statistics for 197.96.214.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 175ms, Average = 172ms

C:\WINDOWS\system32>ping -a 197.96.214.112

Pinging 197.96.214.112 with 32 bytes of data:
Reply from 197.96.214.112: bytes=32 time=171ms TTL=244
Reply from 197.96.214.112: bytes=32 time=170ms TTL=244
Reply from 197.96.214.112: bytes=32 time=174ms TTL=244
Reply from 197.96.214.112: bytes=32 time=170ms TTL=244

Ping statistics for 197.96.214.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 174ms, Average = 171ms


C:\WINDOWS\system32>tracert 197.96.214.112

Tracing route to 197.96.214.112 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.254
2 6 ms 2 ms 3 ms 155.93.141.1
3 6 ms 4 ms 5 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 3 ms 3 ms 4 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 3 ms 3 ms 3 ms c3u-backbone.coolideas.co.za [154.0.1.138]
6 171 ms 172 ms 172 ms 197.96.214.112

Trace complete.

C:\WINDOWS\system32>tracert axxess.co.za

Tracing route to axxess.co.za [197.96.139.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 5 ms 3 ms 3 ms 155.93.141.1
3 3 ms 2 ms 2 ms c4x-backbone.coolideas.co.za [154.0.1.177]
4 8 ms 3 ms 3 ms cx-backbone.coolideas.co.za [154.0.2.33]
5 4 ms 3 ms 2 ms c36-backbone.coolideas.co.za [154.0.2.114]
6 173 ms 171 ms 170 ms 197.96.214.112
7 171 ms 171 ms 171 ms 168.209.1.165
8 171 ms 171 ms 171 ms 168.209.0.186
9 170 ms 170 ms 171 ms 197.96.94.126
10 161 ms 161 ms 162 ms 197.96.139.133

Trace complete.
Click to expand...

Try again, drop me a PM might be easier :)
 
Question for the folks on VUMA CISP that are gaming from CT. What are your pings to EU servers like? Getting between 170 and 180 on VDSL when using an IS based account so as long as its similar I'll be happy camper.

Fibre getting installed on Monday and I'd love to come to CISP - most active and knowledgeable forum rep on this site at present. Counts for a LOT!
 
Orihalcon said:
Question for the folks on VUMA CISP that are gaming from CT. What are your pings to EU servers like? Getting between 170 and 180 on VDSL when using an IS based account so as long as its similar I'll be happy camper.

Fibre getting installed on Monday and I'd love to come to CISP - most active and knowledgeable forum rep on this site at present. Counts for a LOT!
Click to expand...
I don't game on eu servers , but should be at least 10 ms lower, but more stable, as on variance will be lower.
 
Orihalcon said:
Question for the folks on VUMA CISP that are gaming from CT. What are your pings to EU servers like? Getting between 170 and 180 on VDSL when using an IS based account so as long as its similar I'll be happy camper.

Fibre getting installed on Monday and I'd love to come to CISP - most active and knowledgeable forum rep on this site at present. Counts for a LOT!
Click to expand...

Give a few IP's then I will ping them for you.
To EU in general is around 140+ ms
 
Hell that's amazing. Even better than the Telkom fibre I was on 2 years ago.

I'll grab some IP's tonight. Usually play Titanfall to servers in either London or Germany and Paladins which is EU region.

Thank you!
 
Orihalcon said:
Hell that's amazing. Even better than the Telkom fibre I was on 2 years ago.

I'll grab some IP's tonight. Usually play Titanfall to servers in either London or Germany and Paladins which is EU region.

Thank you!
Click to expand...

This is a speedtest to Vodafone London UK
 

Thank you jannier. Even better since your location is just to the north of me. I'm in Brackenfell South. So I'm glad there are no area issues like some others are experiencing.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X