Cool Ideas Fibre ISP – Feedback Thread 2

semaphore

Honorary Master
Joined
Nov 13, 2007
Messages
10,569
I think most of your issues are down to Edge still using a microwave link for the backhaul.
Not sure what you're talking about in reference to that image, that image is purely showing my cpu usage for the tool im using to graph the network connectivity.

And taking jabs at edge constantly is a bit under handed, considering all the issues are actually stemming from your network stability. When your network is stable my latency is fine. So in retrospect I think all the issues for the last couple of weeks are actually stemming from your end and not edge.
 

Seeyou

Expert Member
Joined
May 1, 2007
Messages
1,518
Since the Vumatel maintenance last week (I'm on Octotel) twitch was running buttery smooth for the first time since.. well basically forever. This morning I noticed I was disconnected, and now have a 155.xxx IP instead of the 102.xxx I've been on for a while. Twitch is now back to the buffering, jerky garbage I'm used to. Did something change overnight?
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
5,866
Not sure what you're talking about in reference to that image, that image is purely showing my cpu usage for the tool im using to graph the network connectivity.

And taking jabs at edge constantly is a bit under handed, considering all the issues are actually stemming from your network stability. When your network is stable my latency is fine. So in retrospect I think all the issues for the last couple of weeks are actually stemming from your end and not edge.
That is not completely true, you are making the assumption any issue on our network would have an effect on your service.

Packet loss on and NLD between Parklands and IS UMH, or backhaul between Parklands and Teraco would also not have an effect because your NNI terminates at Teraco directly.

Yet you have had disconnects and latency spikes when we have no network incidents on our side.

Hence the statement that I believe most of your issues stem from that microwave backhaul.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
5,866
Since the Vumatel maintenance last week (I'm on Octotel) twitch was running buttery smooth for the first time since.. well basically forever. This morning I noticed I was disconnected, and now have a 155.xxx IP instead of the 102.xxx I've been on for a while. Twitch is now back to the buffering, jerky garbage I'm used to. Did something change overnight?
No changes on our side, just a different IP block. Try run an MTR to a Twitch host?
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
5,866
Those of you who have issues at night with their twitch please run this test during the off peak and then peak period to see what the results throw
http://cloudharmony.com/speedtest-for-aws:s3-eu-central-1

Link for the test above and then post so that i can see whats going on.
I dont really have issues with twitch but this test should hopefully shed some light on the issue

Example of a test
View attachment 673127
Well we have a direct connect in place with AWS, but also peer with Twitch in London. So I think some traffic is via AWS and some from the legacy network.
 

milomak

Honorary Master
Joined
May 23, 2007
Messages
12,265
It's an uncapped package. As part of the package, they limit international to 100mbps on the download, but currently they aren't limiting it because they have enough bandwith.
What do you mean they limit to 100Mbps. Nothing on the site suggests that
 

under_sky

Expert Member
Joined
Dec 26, 2013
Messages
1,002
Well we have a direct connect in place with AWS, but also peer with Twitch in London. So I think some traffic is via AWS and some from the legacy network.
justine Tv seem to be the main path people grab from if the DNS directs them towards Fra

This is the current path its pushed to

tracert live.twitch.tv

1 <1 ms <1 ms <1 ms 192.168.5.1
2 * * * Request timed out.
3 5 ms 4 ms 4 ms 154.0.4.209
4 163 ms 162 ms 162 ms 154.0.4.250
5 170 ms 170 ms 170 ms te0-1-0-7-4.1200.ccr21.lon01.atlas.cogentco.com [149.14.250.249]
6 * 161 ms 162 ms be2338.rcr21.b015534-1.lon01.atlas.cogentco.com [130.117.1.14]
7 * twitch.demarc.cogentco.com [149.14.147.18] reports: Destination net unreachable.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
5,866
justine Tv seem to be the main path people grab from if the DNS directs them towards Fra

This is the current path its pushed to

tracert live.twitch.tv

1 2 * * * Request timed out.
3 5 ms 4 ms 4 ms 154.0.4.209
4 163 ms 162 ms 162 ms 154.0.4.250
5 170 ms 170 ms 170 ms te0-1-0-7-4.1200.ccr21.lon01.atlas.cogentco.com [149.14.250.249]
6 * 161 ms 162 ms be2338.rcr21.b015534-1.lon01.atlas.cogentco.com [130.117.1.14]
7 * twitch.demarc.cogentco.com [149.14.147.18] reports: Destination net unreachable.
And that IP belongs to Cogent:

https://bgp.he.net/ip/149.14.147.18
 
Joined
Mar 10, 2015
Messages
21
When vumatel installed our aerial fiber at our house they installed a pole onto our property that's now starting to fail. Who's responsibility would it be to fix it?
 

nelis

Expert Member
Joined
Jul 2, 2006
Messages
2,070
anybody else having issues playing games online. I'm getting disconnected from servers and doesn't matter what game I play. I think it's to do with the connection to outside africa cause for example I play bf5 and get disconnected. My whole origin also disconnects so it's not the game itself but origin. I also tried steam game that only have servers outside africa. When I play apex legends also getting disconnections
 
Joined
Jan 16, 2009
Messages
21
Ping statistics for 37.244.28.102:
Packets: Sent = 33, Received = 27, Lost = 6 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 178ms, Average = 164ms
 
Top