The Gold Road Chapter – which includes the Scribing system – and Update 42 is now available to test on the PTS! You can read the latest patch notes here: https://forums.elderscrollsonline.com/en/discussion/656454/
Maintenance for the week of April 29:
• PC/Mac: No maintenance – April 29
• PC/Mac: No maintenance – April 29
Oceanic Lag now 300-400 ms even with a vpn - was 250-300??
-
OldManJim✭✭✭✭✭I'd like to express gratitude to Jorge ( @not4us ) for taking the time and having the patience to do this.
Thanks Jorge, I really hope this leads somewhere...
Agreed. Thanks Jorge.
Hopefully this will make ZOS actually pay attention to the issue now.PAWS (Positively Against Wrip-off Stuff) - Say No to Crown Crates!1 -
Zer0_CooL✭✭✭✭✭
✭Maybe ZOS tries to increase the lag purposely even higher, in order to prevent night capping in cyrodiyl.0 -
not4us✭✭✭Thank you all for your support and encouragement, it really motivates me to keep going on this pursuit!
Although I don't feel like I'm doing anything anybody wouldn't do in this situation.
The thing is I deal with support people like this on a regular basis and been doing that for years to know how to navigate around them to get to a solution but sometimes it's a matter of luck and managing to find the right person with the right attitude.
Hopefully this will get somewhere...7 -
mrpaxman✭✭✭I wish i could share my entire ticket with customer support in this thread. I can only describe it is "unimaginely bad". Every ticket is like that. I am literally lost for words on where to possible even try start. I'll just touch on a few things.
They sent me a packet loss test and wrote 100% fail at the top when the test actually shows 100% of packets made it. The issue is on my end. 220ms is really bad latency and i have a problem. My system is being over taxed. Heck this was just a ticket to ask why a new graphics card did not increase my FPS at all in ESO only. I literally could write about 30 pages of just as bad things from support. In the end they just tell us they are customer support and those fixes are not to do with them. Go to the forums and others may be able to help.
I fell very sorry for all those dealing with support for the roller coaster ride likely to begin after midnight every night for many people in this thread. If there were anything to tell us players then it would have been done publicly at least once a very long time a go. This issue has been affecting players for almost 12 months. Nearly 1 year happy birthday Akamai lag. Not a single reason why it won't stay forever or any other reasonable time frame. Many realised this last year. I had it good and it only lasted 3 months the first time for me. History shows that we are likely to get added issues instead of having this one removed.
Edit:
1 more point i thought i should share is. The person at support is always some one new between each message and goes in complete circles. Future support people start using incorrect info from previous people and combine all that in to an ever growing snowball effect ending up with an entire list of false things wrong and no progress made at all.Edited by mrpaxman on August 23, 2019 9:59AMVictory or Valhalla!
PC NA3 -
Frostystuff✭✭Ping 400 today in vma with a vpn. Things not were indicated almost impossible to time blocks or dodges, unplayable.0
-
alright seriously its still really bad for me, is this going to get a fix? i swapped too ff 14 and have been playing that instead. would like to come back at some point though...0
-
not4us✭✭✭The merry go round has started.
And the worst part is this time is the same person that looked at the ticket previously (although doubt he actually read the ticket).
The Elder Scrolls Online Team message: 08/23/2019 10:41 AM
Greetings,
Brian here again with The Elder Scrolls Online Support.
Thank you for the follow up reply. Just as before, I would recommend testing on a completely different network and see if the same issue continues. Should the game play normally on another ISP/network this means that something with in your ISP or home network is the cause behind your issue. In this situation we recommend contacting your ISP for assistance.
Thank you for your understanding.
Warm regards,
Brian
The Elder Scrolls Online Support
And my reply:
Customer message: 08/23/2019 06:44 PM
Hi again Brian,
You seem to not have fully read my previous response.
I'll just copy and paste part of it here:
"As I have mentioned before in this ticket, I have tested this over several different connections (fibre, cable, ADSL, 4G) and different ISPs with the same results of pings on the high 300ms / mid 400ms ".
Please stop telling me the problem is my ISP, this is happening over different IPSs, different type of Internet connections AND different computers.
In other ways, the game doesn't play normally from any computer/ISP/ Internet connection from Australia.
Again, please stop trying to place the issue on my end, it's not.
It's widely documented and tested that ALL traffic to ESO servers in North America coming from Australia and New Zealand goes over Hong Kong. If you look at a World Map you'll realize that's not the best route to follow and that introduces an extra 100-200 ms of latency that makes the game unplayable for everyone here.
You can see that from the TraceRoute I send you and the multiple trace routes that people have posted in your forums.
I thought that had been cleared up in the ticket earlier but you are asking me to go over the same things again when I have already done them and told you the results.
Please read through the ticket. THE ISSUE IS WITH THE AKAMAI SERVICE EMPLOYED BY ZENIMAX ONLINE TO PROTECT AGAINST DDOS.
The problem is on YOUR end, not the customer's end.
Once you acknowledge that we can move forward and find a solution which will help the thousands of players in Oceania.
Cheers,
Jorge12 -
ArcaneBlue✭✭✭I have decided to take a long break from this game and high ping is one of the reasons... exitlag works alright for me, it reduces my ping by 100 or so but why do I have to pay for a 3rd party service just to be able to play at all, not to maximise the performance? that, coupled with a few other issues I have with this game (certain changes introduced with elsweyr) and RL reasons, I think it's time for me to take a big break from this game again.
my BF still pvps and if he wants me to help him farm gear I'd do it but I won't be actively playing for a long while...
I really just want SOME explanation from Z's side, as to why the latency got increased by 100-150 all of a sudden about 3-4 weeks ago. shame, really#teamEmeric5 -
CiliPadi✭✭✭✭The merry go round has started.
And the worst part is this time is the same person that looked at the ticket previously (although doubt he actually read the ticket).
The Elder Scrolls Online Team message: 08/23/2019 10:41 AM
Greetings,
Brian here again with The Elder Scrolls Online Support.
Thank you for the follow up reply. Just as before, I would recommend testing on a completely different network and see if the same issue continues. Should the game play normally on another ISP/network this means that something with in your ISP or home network is the cause behind your issue. In this situation we recommend contacting your ISP for assistance.
Thank you for your understanding.
Warm regards,
Brian
The Elder Scrolls Online Support
What a joke, are we suppose to change ISPs and test for ZOS? LMAO. Pathetic.0 -
Bhaal5✭✭✭✭✭
✭The merry go round has started.
And the worst part is this time is the same person that looked at the ticket previously (although doubt he actually read the ticket).
The Elder Scrolls Online Team message: 08/23/2019 10:41 AM
Greetings,
Brian here again with The Elder Scrolls Online Support.
Thank you for the follow up reply. Just as before, I would recommend testing on a completely different network and see if the same issue continues. Should the game play normally on another ISP/network this means that something with in your ISP or home network is the cause behind your issue. In this situation we recommend contacting your ISP for assistance.
Thank you for your understanding.
Warm regards,
Brian
The Elder Scrolls Online Support
What a joke, are we suppose to change ISPs and test for ZOS? LMAO. Pathetic.
The only time they would care is if you were in America.. That seems to be the only solution to eso.. Mudfish isnt really an option.
Vote with your wallets ladies and gents... Better games out there with better and more active ocx populations. Zos doesnt care about you, so why give them thanks with money?3 -
not4us✭✭✭Round and round we go...
The Elder Scrolls Online Team message: 08/24/2019 11:35 AM
Greetings,
Brian here again with The Elder Scrolls Online Support.
Rest assured that your earlier replies and understood. Please bear in mind that this issue has been investigated previously and no routing issues were found within our systems (including our network) to cause this type of thing to occur. Additionally upon investigation it was found that the cause could be traced back to certain ISPs experiencing an issue within their network.
Customer whom I've previously worked with in the past (also located in Australia) were not able to reproduce their latency issues when using a WiFi hotspot as they were using a completely different network.
That said and just as before, I would recommend testing on a completely different network and see if the same issue continues. Should the game play normally on another ISP/network this means that something with in your ISP or home network is the cause behind your issue. In this situation we recommend contacting your ISP for assistance.
Warm regards,
Brian
The Elder Scrolls Online Support
Customer message: 08/25/2019 05:49 AM
Hi Brian,
You said you read my earlier replies and understood them and then you ask me to try connecting from a different network... did you REALLY read my reply? Because in it I WROTE TWICE that I have tried from a different network(s) and the problem persists.
At the end of this message I’m sending different traceroutes from different ISPs in Australia for you to get the picture.
And again, if you read my replies, I explained that there are no routing issues on your side, or mine, the issue is with your DDOS Scrubbing Service AKAMAI, which sits in the middle and routes all Oceanic traffic to the ESO NA servers through Hong Kong or The Netherlands. Is this so hard to understand?
The solution you offer again and again points to the issue being on my end and it’s getting infuriating to be honest.
Have a look at the result of these traceroutes below (you can do traceroutes to your servers from Australia yourself using Looking Glass here https://www.ausnog.net/tools/lg)
Note how all the traces, at some point (usually around hop 11/12) go to "po110.bs-b.sech-osa.netarch.akamai.com [23.57.105.245"]? That’s on The Netherlands and it’s an AKAMAI IP, the company ZOS contracts to do DDOS protection. THAT IS WHERE THE PROBLEM IS.
Doing the traceroutes from your end won’t help. You need to do the traceroutes from Oceania.
Just look at these results and try to tell me that the problem is my ISP or my connection once again…
From Telstra:
Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.1.1.1
2 * * * Request timed out.
3 8 ms 9 ms 19 ms 58.160.249.129
4 10 ms 12 ms 13 ms bundle-ether4.ken-edge901.sydney.telstra.net [203.50.12.104]
5 11 ms 18 ms 12 ms bundle-ether13.ken-core10.sydney.telstra.net [203.50.11.94]
6 16 ms 13 ms 12 ms bundle-ether1.oxf-gw10.sydney.telstra.net [203.50.6.97]
7 12 ms 12 ms 12 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
8 157 ms 155 ms 157 ms i-84.eqnx-core02.telstraglobal.net [202.84.247.37]
9 205 ms 206 ms 207 ms i-93.joua01.telstraglobal.net [202.84.140.214]
10 207 ms 208 ms 207 ms 210.176.33.42
11 210 ms 210 ms 212 ms po110.bs-b.sech-osa.netarch.akamai.com [23.57.105.245]
12 * * * Request timed out.
13 219 ms 212 ms 220 ms ae121.access-a.sech-osa.netarch.akamai.com [23.57.105.251]
14 * * * Request timed out.
15 * * * Request timed out.
16 345 ms 347 ms 346 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
17 346 ms 346 ms 347 ms 198.20.192.3
18 347 ms 346 ms 345 ms 198.20.198.110
Trace complete.
From AARNET:
traceroute to 198.20.198.110 (198.20.198.110), 30 hops max, 40 byte packets
1 ge-1-0-0.bb1.a.syd.aarnet.net.au (202.158.196.129) 0.519 ms 0.337 ms 0.373 ms
2 ae9.pe2.brwy.nsw.aarnet.net.au (113.197.15.56) 0.584 ms 0.581 ms 0.535 ms
3 et-3-1-0.pe1.brwy.nsw.aarnet.net.au (113.197.15.146) 1.114 ms 1.149 ms 1.258 ms
4 et-2_0_5.bdr1.sing.sin.aarnet.net.au (113.197.15.233) 92.140 ms 92.140 ms 92.128 ms
5 xe-0-0-6-2.a01.sngpsi03.sg.bb.gin.ntt.net (116.51.27.145) 193.920 ms 193.921 ms 193.906 ms
6 ae-13.r00.sngpsi07.sg.bb.gin.ntt.net (129.250.7.82) 201.352 ms ae-8.r01.sngpsi07.sg.bb.gin.ntt.net (129.250.7.84) 202.487 ms 202.449 ms
7 ae-1.r20.sngpsi07.sg.bb.gin.ntt.net (129.250.3.83) 200.761 ms ae-2.r20.sngpsi07.sg.bb.gin.ntt.net (129.250.3.101) 194.221 ms 194.264 ms
8 ae-9.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.7.67) 214.938 ms 214.020 ms 214.012 ms
9 ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92) 202.048 ms 202.695 ms 202.638 ms
10 ae-2.a00.chwahk02.hk.bb.gin.ntt.net (129.250.6.121) 202.654 ms 3201.508 ms 3200.440 ms
11 203.131.250.178 (203.131.250.178) 202.825 ms 203.131.250.182 (203.131.250.182) 207.985 ms 203.131.250.178 (203.131.250.178) 202.830 ms
12 po110.bs-b.sech-hkg2.netarch.akamai.com (72.52.2.184) 208.301 ms po111.bs-b.sech-hkg2.netarch.akamai.com (72.52.2.186) 208.244 ms 208.304 ms
13 a72-52-1-169.deploy.static.akamaitechnologies.com (72.52.1.169) 201.474 ms 203.227 ms 200.108 ms
14 ae121.access-a.sech-hkg2.netarch.akamai.com (72.52.2.189) 208.143 ms 206.695 ms 208.118 ms
15 93.191.173.93 (93.191.173.93) 208.864 ms 209.259 ms 209.131 ms
16 * * *
17 198.20.192.4 (198.20.192.4) 243.663 ms 243.047 ms 198.20.192.3 (198.20.192.3) 240.564 ms
18 198.20.198.110 (198.20.198.110) 244.511 ms 242.297 ms 244.415 ms
From AAPT Sydney:
Tracing the route to 198.20.198.110
1 gi9-9.sglebdist02.nw.aapt.net.au (202.10.15.154) [MPLS: Label 458 Exp 0] 148 msec
gi9-9.sglebdist01.nw.aapt.net.au (202.10.15.152) [MPLS: Label 533 Exp 0] 0 msec
gi9-9.sglebdist02.nw.aapt.net.au (202.10.15.154) [MPLS: Label 458 Exp 0] 4 msec
2 bu8.sglebbrdr11.aapt.net.au (202.10.14.27) 0 msec
bu9.sglebbrdr11.aapt.net.au (202.10.14.29) 0 msec
bu8.sglebbrdr11.aapt.net.au (202.10.14.27) 0 msec
3 TenGigE0-3-0-19.chw-edge901.sydney.telstra.net (139.130.209.229) [AS 1221] 4 msec 0 msec 0 msec
4 bundle-ether13.chw-core10.sydney.telstra.net (203.50.11.98) [AS 1221] 4 msec 0 msec 4 msec
5 bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93) [AS 1221] 4 msec 0 msec 4 msec
6 bundle-ether2.oxf-gw10.sydney.telstra.net (203.50.6.94) [AS 1221] 4 msec 0 msec 4 msec
7 bundle-ether1.sydo-core04.sydney.reach.com (203.50.13.94) [AS 1221] 0 msec 4 msec 0 msec
8 i-84.eqnx-core02.telstraglobal.net (202.84.247.37) [AS 4637] 176 msec 176 msec 176 msec
9 i-93.joua01.telstraglobal.net (202.84.140.214) [AS 4637] 288 msec 284 msec 288 msec
10 210.176.33.42 [AS 4637] 188 msec 188 msec 192 msec
11 po110.bs-a.sech-osa.netarch.akamai.com (23.57.105.243) [AS 32787] 188 msec
po110.bs-b.sech-osa.netarch.akamai.com (23.57.105.245) [AS 32787] 188 msec 188 msec
From UUEcomm Victoria:
traceroute to 198.20.198.110 (198.20.198.110), 30 hops max, 60 byte packets
1 203.94.134.241 (203.94.134.241) 0.263 ms 0.280 ms 0.296 ms
2 115.186.193.137 (115.186.193.137) 1.651 ms 1.667 ms 1.644 ms
3 3818.gi0.br1.cit190.uecomm.net.au (218.185.31.202) 2.158 ms 2.531 ms 2.725 ms
4 119.225.18.69 (119.225.18.69) 2.383 ms 2.384 ms 2.366 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 59.154.18.10 (59.154.18.10) 16.425 ms 59.154.18.6 (59.154.18.6) 15.398 ms 59.154.18.10 (59.154.18.10) 16.397 ms
10 203.208.177.189 (203.208.177.189) 131.735 ms 130.067 ms 130.035 ms
11 xe-11-3-2-xcr1.hkg.cw.net (195.2.22.149) 133.941 ms 131.589 ms 130.097 ms
12 ae0-xcr1.hke.cw.net (195.2.10.98) 130.744 ms 130.712 ms 131.312 ms
13 ae20-xcr1.sng.cw.net (195.2.8.17) 166.654 ms 167.246 ms 165.492 ms
14 195.89.111.210 (195.89.111.210) 128.266 ms 128.320 ms 126.015 ms
15 po110.bs-b.sech-sin.netarch.akamai.com (23.57.106.245) 128.741 ms po110.bs-a.sech-sin.netarch.akamai.com (23.57.106.243) 127.940 ms po110.bs-b.sech-sin.netarch.akamai.com (23.57.106.245) 126.106 ms
Hope it's clear this time.
Jorge7 -
jcm2606✭✭✭✭✭
✭✭@not4us Might be worth looking into how Aussie Broadband is forcing their traffic to skip the Hong Kong / Netherlands / Singapore scrubber, and dumping traffic straight into the US. Bring that up, as when an entire ISP is having to skip Akamai, you know Akamai is the problem, and not the ISP.2 -
lokulin✭✭✭✭✭Logged in on Launtel at my parents place and was getting a solid 290 while standing around in Wayrest. Weirdly tho it went back to 360+ while doing Cradle of Shadows. Still a full 100ms better than on my Internode connection. Both are FttH/FttP 100/40 connections. The difference seems to be the routing once again as Launtel seems to go straight to Tokyo. ZOS have you opened a ticket with Akami yet?Tracing route to 198.20.200.153 over a maximum of 30 hops 1 5 ms 4 ms 4 ms 100.65.48.1 2 28 ms 28 ms 28 ms jupiter.launtel.net.au [45.248.51.209] 3 29 ms 28 ms 28 ms hercules.launtel.net.au [45.248.51.217] 4 30 ms 30 ms 30 ms 103.75.6.201 5 28 ms 28 ms 28 ms ix-xe-0-3-1-0.thar1.1mh-sydney.as6453.net [120.29.219.101] 6 129 ms 129 ms 129 ms if-ae-2-2.tcore1.0pp-sydney.as6453.net [120.29.195.98] 7 130 ms 129 ms 129 ms if-ae-5-2.thar1.pv4-piti.as6453.net [120.29.219.82] 8 129 ms 130 ms 129 ms if-ae-21-2.tcore2.tv2-tokyo.as6453.net [180.87.181.132] 9 129 ms 131 ms 130 ms 180.87.181.42 10 129 ms 132 ms 128 ms po110.bs-b.sech-tyo.netarch.akamai.com [72.52.56.200] 11 132 ms 128 ms 129 ms a72-52-1-177.deploy.static.akamaitechnologies.com [72.52.1.177] 12 130 ms 129 ms 129 ms ae121.access-a.sech-tyo.netarch.akamai.com [72.52.56.205] 13 208 ms 207 ms 208 ms 93.191.173.29 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out.
Tracing route to 198.20.200.25 over a maximum of 30 hops 1 4 ms 4 ms 6 ms 100.65.48.1 2 28 ms 30 ms 29 ms jupiter.launtel.net.au [45.248.51.209] 3 28 ms 29 ms 28 ms hercules.launtel.net.au [45.248.51.217] 4 29 ms 29 ms 29 ms 103.75.6.201 5 29 ms 28 ms 29 ms ix-xe-0-3-1-0.thar1.1mh-sydney.as6453.net [120.29.219.101] 6 130 ms 128 ms 128 ms if-ae-2-2.tcore1.0pp-sydney.as6453.net [120.29.195.98] 7 133 ms 129 ms 129 ms if-ae-5-2.thar1.pv4-piti.as6453.net [120.29.219.82] 8 128 ms 144 ms 129 ms if-ae-21-2.tcore2.tv2-tokyo.as6453.net [180.87.181.132] 9 132 ms 131 ms 129 ms 180.87.181.42 10 130 ms 128 ms 128 ms po110.bs-a.sech-tyo.netarch.akamai.com [72.52.56.192] 11 129 ms 129 ms 129 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155] 12 129 ms 130 ms 129 ms ae120.access-a.sech-tyo.netarch.akamai.com [72.52.56.197] 13 208 ms 207 ms 209 ms 93.191.173.29 14 241 ms 247 ms 245 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88] 15 241 ms 244 ms 241 ms 198.20.192.4 16 245 ms 246 ms 245 ms 198.20.200.25
Edited by lokulin on August 25, 2019 11:32AMI've hidden your signature.1 -
Square252✭✭✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.Edited by Square252 on August 25, 2019 11:36AM0 -
LordGavus✭✭✭✭✭
✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.
Hooray, the chosen one is here to save us!
The network god is here to deliver us from poor latency!
90 ping for everyone in Australia!3 -
Square252✭✭✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.
Hooray, the chosen one is here to save us!
The network god is here to deliver us from poor latency!
90 ping for everyone in Australia!
That is basically the reason everyone ignores you
But yeah, use your vpn to add layers over layers of additional points of failure to keep whining.0 -
SaucyMcSauceface✭✭✭✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.
Are you in Australia? cause just pinging the US itself takes longer than 60ms from here... Seems unlikely that you have magically managed to beat the laws of physics9 -
lokulin✭✭✭✭✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.
Crap, I better hand my first class honours degree in computing back and while I'm at it rethink my 20 years experience as a systems engineer as it was all obviously a lie. smhEdited by lokulin on August 25, 2019 1:07PMI've hidden your signature.6 -
LordGavus✭✭✭✭✭
✭Since everyone here is basically just blaming ZoS; i got a solid 50 to 60 FPS and a ping of 60 to 90 outside of cyro.
What i did? Redid my home network. Ubiquity USG + Switch + good cabling. Never had any dc, not even in cyro, since then. I didn't even configure qos.
But yea, keep blaming ZoS since it's easier than learn basic networking when playing online games. Basically no real-time application (be it VoIP or an MMORPG) works with of-the-shelve-hardware.
As for the nice tracert's you guys posted: They work on ICMP, which is basically a throttled protocol everywhere. The game runs on TCP/UDP. Whole different thing.
Hooray, the chosen one is here to save us!
The network god is here to deliver us from poor latency!
90 ping for everyone in Australia!
That is basically the reason everyone ignores you
But yeah, use your vpn to add layers over layers of additional points of failure to keep whining.
Yeah cool, except i can partially fix the poor zos/akamai routing with a vpn. Reducing my latency from 450 to 300.
Sure its an addtional step, but it still improves it.
Your comments have been discussed in this thread before, several times, please read before continuing. Cheers.0
This discussion has been closed.