Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
You can find information about his on the Official Hunt discord channel if you search for it. It has been discussed much.
Some players report having success with a VPN, using it to change their data's route.
Crytek support is a good idea as well, but will take its time. I recommend both.
@OP;
Using a VPN might indeed work.
Apart from that, sent Crytek a support ticket (though I doubt they will/"can" do anything about it).
It's a Leaseweb/ISP problem & Crytek knows that.
Those ISPs claim it's Cryteks/Leasewebs fault, while Crytek/Leaseweb blames it on the ISPs.
Should read the discord.
I conducted some new tests from my own VPN gateways in Amsterdam (AMS) and Saint-Petersburg (SPB), and here's what I observed:
AMS:
SPB:
As you can see, the same hosting provider is used, but there's a significant difference in latency. It's almost certain that the problem lies within the Leaseweb infrastructure, especially in their routing policies. I'm quite surprised that they haven't fixed this issue since October 26, 2023.
I've already opened a trouble ticket with Crytek, but there's been no response. So, I decided to bring up this problem here. -_-
But yeah, you're right.
Those ISPs claim it's Cryteks/Leasewebs fault, while Crytek/Leaseweb blames it on the ISPs.
(Edited my other post to make it more clear).
Then why do you suppose they said they were going set up new infrastructure options next year in those specific effected ISP markets?
It looks like they can do something about it to me. It just wasn't easy (like they said in the beginning lol) What do you think of that?
I mean they could've made some more pressure, or change the server provider or whatever.
Apparently they wanna fix this issue soon-ish (by setting up some new infrastructures (like Duncan mentioned)) but honestly took them way too long - in my opinion.
I'm holding out on hope on it as ive been having issues for years. Soley with Hunt Showdown only.
They could have gotten out of the contract I imagine with Leaseweb due to technical issues, but Crytek look to be the only bigger name gaming company that use Leaseweb so sure Leaseweb give them a good deal for being a long-term customer.
I really hope that they do sort out the issues, they are obviously known as they even mentioned it in the Road Map as mentioned
I love the game but my experience of it is simply ruined at "random" times being plauged with network issues that are absolutely nothing to do with my home LAN.
Funny, but it looks like Crytek support literally doesn't know how networks work. 😄
Here is the response:
"""
Hi Maksim Alov,
Thanks for your report.
From this traceroute, it sounds like you are being routed through private network for more hops than normal, in fact until hop 6 they are seemingly all private IPs.
Could you please contact your ISP, and ask them if they can assist you with this?
We hope for your patience and understanding.
Best Regards,
Blakki73
"""
I've worked in a senior network engineer position for about ten years, and this really amuses me. 😄 Sometimes, it's better to remain silent than to provide answers like that.
Correct me if I am wrong or if I did misunderstood something (because I only have a limited understanding if it comes to such things, hence I am no expert) BUT lets just pretend those first 6 hops "are seemingly all private IPs", it shouldn't really matter (as in that's not the cause of the issue), because those first 6 hops all have a very low ms/response-time.
Therefore, to me, their response makes no sense at all.
Thanks for the heads up though.
It doesn't matter how many hops an IP packet takes inside an ISP network because you might not know which technologies your ISP uses within the network. It can involve L3 circuits (which can result in more hops) or MPLS/QinQ, or something similar that leads to fewer hops because it operates at the L2 network level, and you don't see each hop. But, as I mentioned, the number of hops within a single city doesn't significantly affect latency. The difference in hops between ISPs is what matters because it involves BGP peering between carriers and can affect the routing.
In my case, the latency inside my ISP network is between 1-8ms. When a packet reaches Europe, the latency starts at around 130ms, which is acceptable for connectivity between the UAE and the EU due to the geographical distance. However, as we can see next, inside one hosting provider between two hops (31.31.34.27 and 212.95.37.81), there is a significant difference. It seems like a problem within the LeaseWeb hosting provider. It could be a routing policy issue, or LeaseWeb, with its different data centers worldwide, might be routing IP packets incorrectly. It's possible that my packet is being routed from the EU to Asia or the US, but I can't say for sure; this is just a guess
Ouch, you’re going to upset Duncan ;)
But yeah, I’ve worked support jobs and if i didn’t understand something I’d ask for a expert opinion (escalation)… the fact Crytek support are just trying to let it slide off their backs and deflect the blame to isps with a scripted answer has always seemed deliberate… they know the problem is servers but won’t do anything (tinfoil hat time :))
Thanks for clearing that up @XoXJlywKo
Seems like it.
It's a shame really.
Shouldn't you be the one telling us?