- Joined
- Jan 11, 2016
- Messages
- 13,304
I think most of your issues are down to Edge still using a microwave link for the backhaul.
I think most of your issues are down to Edge still using a microwave link for the backhaul.
We are changing our layer2 carrier to London.I'm out of the loop here. What is CISP changing from and what to?
It is stable yes.So @PBCool is the link stable or can we expect a total **** storm for the rest of the evening?
I think most of your issues are down to Edge still using a microwave link for the backhaul.
That is not completely true, you are making the assumption any issue on our network would have an effect on your service.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.
No changes on our side, just a different IP block. Try run an MTR to a Twitch host?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?

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.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
What do you mean they limit to 100Mbps. Nothing on the site suggests thatIt'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.
Evidence pleaseIt'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.
justine Tv seem to be the main path people grab from if the DNS directs them towards FraWell 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.
And that IP belongs to Cogent: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.
Evidence please
On the CISP Vumatel signup page
View attachment 673201