Thank you for the the post @anX1 As @akS replied, there are several ISPs having routing trouble to the particular set of IPs that we have had. We have added another set (but haven’t taken down the old IPs because they still work fine for most folks) which might be better (although YMMV).
Seems pretty clear to me that Kunal Powar is indicating that this could be an issue from AWS side
Ah you might’ve thought that because he used the word “region”. He didn’t mean an AWS region, he meant a geographical region and the ISPs therein.
he was so quick to just conclude that the problem is with my ISP
How do you know he didn’t investigate? Honestly a pretty big issue is your array of assumptions. Please don’t do that, just ask.
Now, to how he concluded that its an ISP issue - we monitor server performance graphs every now and then, he just consulted that. Another hint that this is an ISP issue is that it didn’t affect 100% of the players (if its a server issue, it will affect EVERY PLAYER, not just a specific subset).
I don’t seem to get replies from you guys without making a fuss about it
Please point me to examples. We reply to almost every post, the only exceptions are-
- folks ask for unbans and cooldown removals
- folks who DM staff on Discord
We do store demos with voice, but that’ll just tell me that players are complaining about loss, I don’t need that, its not like I don’t trust that you’re facing a problem - what helps is to know WHY you’re facing the issue (which is a WinMTR trace, for example)
Maybe try a different config or some test instance
We do that once we figure out that it is infact an issue with the server (OS, hardware etc). But if we already know that it is an ISP issue, we rather spend time on fixing things that we can do (which is using new IPs and hope it helps). Even there, note how I said “hope it helps”, there’s no guarantee.
Because it is so important, I’ll repeat again, please don’t assume stuff, it doesn’t help anyone