Neuro
Active Member
- Joined
- Apr 15, 2011
- Messages
- 88
Back up now...Has frogfoot died again? Been offline for the last 10 minutes....
Frogfoot trenches Fish Hoek, Cape town
Back up now...Has frogfoot died again? Been offline for the last 10 minutes....
Frogfoot trenches Fish Hoek, Cape town
Quite a bit of buffering on Twitch tonight, international from CPT looking a lil flaky?
View attachment 1316746
Yeah noticed that too, seems to be the case for the past couple of days. Feels more solid/like there is less buffering when there aren't bouts of CPT -> UK packet lossI noticed Twitch content is being served from London instead of France, first time i've seen this in a while (video-edge-c6cf5c.lhr04.abs.hls.ttvnw.net).
I wonder if the FranceIX peering is down
RE: #COOL-20220324-899811Yeah we need the ICMP to trend your line. Got the details from Jacques will add it to our system.
Right, yeah not so easy then. You can vpn from mobile devices.
It must be Valorant specific since I don't get the same horrible experience in Apex...RE: #COOL-20220324-899811
Valorant packet loss
How's it looking here? Is this ever going to be fixed? I seem to be getting the silent treatment now from Gumani and PB.
Just be honest with me. Is it going to be fixed or not?
It's been 3 months of this problem now.
I've been very patient and done all the tests and config stuff you asked for over months.
Is it too much to ask for stable routing that everyone else gets?
Others with the same problem: @Overblaze @DYreX146 @Seeyou @CrypticZA
Thanks for any help
Yes, we killed our FranceIX peering in order to see if the loss issue is related to a potentially assymetrical return path.I noticed Twitch content is being served from London instead of France, first time i've seen this in a while (video-edge-c6cf5c.lhr04.abs.hls.ttvnw.net).
I wonder if the FranceIX peering is down
We have disconnected FranceIX in order to ensure that we don't have any assymetric routing (as per my previous comment). The ticket is with our core engineers, unfortunately debugging this issue is something that takes time, and we can only make major peering changes after hours so as not to affect the whole network.RE: #COOL-20220324-899811
Valorant packet loss
How's it looking here? Is this ever going to be fixed? I seem to be getting the silent treatment now from Gumani and PB.
Just be honest with me. Is it going to be fixed or not?
It's been 3 months of this problem now.
I've been very patient and done all the tests and config stuff you asked for over months.
Is it too much to ask for stable routing that everyone else gets?
Others with the same problem: @Overblaze @DYreX146 @Seeyou @CrypticZA
Thanks for any help
Have experienced the same in Apex. Mostly fine, but short periods of massive packet loss.For me, my Valorant ping has dropped noticeably by a solid 20ms(From 190 to 170 average, rarely but sometimes low 160) this week, which makes me happy to see. This is the lowest I've experienced with CI for Durban.
Game is actually somewhat more playable and you don't feel like you're headbutting a wall all the time.
The packet loss has definitely at least for me, become more stable, but still appears in bouts. There are occasional instances where packet loss raises massively for a few seconds, but the overall packet loss is much less. I'd rather have a period of major packet loss that lasts about 15 seconds, rather than it being lesser but constant across a game.
For me, it's not perfect but definitely an improvement.
Thanks for the feedback, we'll see if we can possibly get direct peering goingFor me, my Valorant ping has dropped noticeably by a solid 20ms(From 190 to 170 average, rarely but sometimes low 160) this week, which makes me happy to see. This is the lowest I've experienced with CI for Durban.
Game is actually somewhat more playable and you don't feel like you're headbutting a wall all the time.
The packet loss has definitely at least for me, become more stable, but still appears in bouts. There are occasional instances where packet loss raises massively for a few seconds, but the overall packet loss is much less. I'd rather have a period of major packet loss that lasts about 15 seconds, rather than it being lesser but constant across a game.
For me, it's not perfect but definitely an improvement.
No silent treatment apologies, we will do some emulations on our side and possibly drop peering with riot in UK. Its not a simple fix unfortunately.RE: #COOL-20220324-899811
Valorant packet loss
How's it looking here? Is this ever going to be fixed? I seem to be getting the silent treatment now from Gumani and PB.
Just be honest with me. Is it going to be fixed or not?
It's been 3 months of this problem now.
I've been very patient and done all the tests and config stuff you asked for over months.
Is it too much to ask for stable routing that everyone else gets?
Others with the same problem: @Overblaze @DYreX146 @Seeyou @CrypticZA
Thanks for any help
Just email the connect department connect@coolideas.co.za and they will provide the process and cost to do so.@PBCool How does it work if I want to get Octotel out here to physically move my fibre line? The previous owners of the house had the CPE put in the stupidest place and I want it moved to a more appropriate place.
There would likely have to be some discussion with somebody on which is the best way to get it to the location I want before any contractors came to do anything.
I also noticed on some days ping to EU servers increases to 180+ from KZN, although it hasn't happened in a while though. TBH it could have been related to the IXP issue that I pointed out a few weeks back. If I notice it again I'll post it in the thread.For me, my Valorant ping has dropped noticeably by a solid 20ms(From 190 to 170 average, rarely but sometimes low 160) this week, which makes me happy to see. This is the lowest I've experienced with CI for Durban.
Game is actually somewhat more playable and you don't feel like you're headbutting a wall all the time.
The packet loss has definitely at least for me, become more stable, but still appears in bouts. There are occasional instances where packet loss raises massively for a few seconds, but the overall packet loss is much less. I'd rather have a period of major packet loss that lasts about 15 seconds, rather than it being lesser but constant across a game.
For me, it's not perfect but definitely an improvement.
Question I have is, is this a Riot problem or an AWS since comments have been made about Apex which is AWS and I have had issues with WARP packet loss which I assumed was just Cloudflares network (they use a mix of Seacom and Workonline), this peers locally in Cape Town.No silent treatment apologies, we will do some emulations on our side and possibly drop peering with riot in UK. Its not a simple fix unfortunately.
I don’t think AWS is very happy these days. Try https://testmy.net/latency?addr=amazon.comQuestion I have is, is this a Riot problem or an AWS since comments have been made about Apex which is AWS and I have had issues with WARP packet loss which I assumed was just Cloudflares network (they use a mix of Seacom and Workonline), this peers locally in Cape Town.
I am playing Apex at the moment and spiking like crazy on the AWS server
If AWS is having issues it will affect everyone.I don’t think AWS is very happy these days. Try https://testmy.net/latency?addr=amazon.com
On that I sometimes get local 30ms with 200ms spikes, most of the day I get 1000ms average. Very unstable. Enough to make me shop around for a new ISP like herethey might not be a fix-all, but proper feedback is worth a lot
Well we aren't actually sure as yet hence why we will need to setup some tests in Cape Town.Question I have is, is this a Riot problem or an AWS since comments have been made about Apex which is AWS and I have had issues with WARP packet loss which I assumed was just Cloudflares network (they use a mix of Seacom and Workonline), this peers locally in Cape Town.
I am playing Apex at the moment and spiking like crazy on the AWS server