TheGrandBizarre wrote: »Hi ZOS,
This is a quick tracert I did this evening. If you could go ahead and have a chat to your ddos scrubbing contractor about why my data is being routed through the Netherlands that would be greaaaaat.
Given that your terms of service allow you to reject any liability or culpability relating to game connection, latency, stability etc, I feel my only recourse is to use macros in my end game content (pvp) in order to have any semblance of a playable game. I.e. to equalise the latency difference between US and other players. Also, just to make sure abilities will actually fire.
Also, any attempt to edit this post by a member of ZOS staff, implicitly acknowledges the issues pacific/oceanic players have with the game.
So it's a big *** you to ZOS management.
So long, and thanks for all the fish.
Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1 (ADELAIDE, AUSTRALIA)
2 1 ms 2 ms 1 ms 10.20.22.34
3 1 ms 2 ms 1 ms adl-apt-pir-crt1-be200.tpgi.com.au [203.219.182.65] (TPG VIC, AUSTRALIA)
4 2 ms 2 ms 2 ms adl-adc-lon-crt1-be10.tpgi.com.au [203.219.107.18] (TPG NSW, AUSTRALIA)
5 2 ms 3 ms 1 ms adl-adc-lon-wgw1-be-200.tpgi.com.au [203.219.199.67] (TPG VIC, AUSTRALIA)
6 2 ms 2 ms 2 ms be300.akingbrdr11.aapt.net.au [203.219.199.154] (TPG VIC, AUSTRALIA)
7 2 ms 2 ms 2 ms Bundle-Ether12.way-edge902.adelaide.telstra.net [139.130.121.165] (TPG VIC, AUSTRALIA)
8 4 ms 3 ms 4 ms bundle-ether10.way-core10.adelaide.telstra.net [203.50.11.152] (TESLTRA, AUSTRALIA)
9 17 ms 17 ms 16 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231] (TESLTRA, AUSTRALIA)
10 30 ms 31 ms 28 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124] (TESLTRA, AUSTRALIA)
11 27 ms 27 ms 27 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93] (TESLTRA, AUSTRALIA)
12 29 ms 29 ms 30 ms bundle-ether2.oxf-gw10.sydney.telstra.net [203.50.6.94] (TESLTRA, AUSTRALIA)
13 27 ms 27 ms 27 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94] (TESLTRA, AUSTRALIA)
14 185 ms 182 ms 181 ms i-84.eqnx-core02.telstraglobal.net [202.84.247.37] (TELSTRA, HONG KONG)
15 294 ms 293 ms 293 ms 202.84.140.214 (TELSTRA, HONG KONG)
16 284 ms 284 ms 284 ms 210.176.33.42 (TESLTRA, AUSTRALIA)
17 285 ms 286 ms 287 ms po110.bs-a.sech-osa.netarch.akamai.com [23.57.105.243] (AKAMAI TECH, NETHERLANDS)
18 291 ms 291 ms 290 ms a72-52-1-191.deploy.static.akamaitechnologies.com [72.52.1.191] (AKAMAI TECH, USA)
19 291 ms 291 ms 292 ms ae120.access-a.sech-osa.netarch.akamai.com [23.57.105.249] (AKAMAI TECH, NETHERLANDS)
20 296 ms 291 ms 292 ms 93.191.172.27 (AKAMAI TECH, EUROPE)
21 292 ms 292 ms 290 ms 93.191.173.29 (AKAMAI TECH, NETHERLANDS)
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Everyone continuing to play and pay for a vpn is supporting zenimax and there bad policy/coding and networking choices to be honest.
Its no wonder they dont respond.. Because people will put up with mediocre with a vpn.
It's hilarious it's been this long now and still no responseTheGrandBizarre wrote: »Hi ZOS,
This is a quick tracert I did this evening. If you could go ahead and have a chat to your ddos scrubbing contractor about why my data is being routed through the Netherlands that would be greaaaaat.
Given that your terms of service allow you to reject any liability or culpability relating to game connection, latency, stability etc, I feel my only recourse is to use macros in my end game content (pvp) in order to have any semblance of a playable game. I.e. to equalise the latency difference between US and other players. Also, just to make sure abilities will actually fire.
Also, any attempt to edit this post by a member of ZOS staff, implicitly acknowledges the issues pacific/oceanic players have with the game.
So it's a big *** you to ZOS management.
So long, and thanks for all the fish.
Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1 (ADELAIDE, AUSTRALIA)
2 1 ms 2 ms 1 ms 10.20.22.34
3 1 ms 2 ms 1 ms adl-apt-pir-crt1-be200.tpgi.com.au [203.219.182.65] (TPG VIC, AUSTRALIA)
4 2 ms 2 ms 2 ms adl-adc-lon-crt1-be10.tpgi.com.au [203.219.107.18] (TPG NSW, AUSTRALIA)
5 2 ms 3 ms 1 ms adl-adc-lon-wgw1-be-200.tpgi.com.au [203.219.199.67] (TPG VIC, AUSTRALIA)
6 2 ms 2 ms 2 ms be300.akingbrdr11.aapt.net.au [203.219.199.154] (TPG VIC, AUSTRALIA)
7 2 ms 2 ms 2 ms Bundle-Ether12.way-edge902.adelaide.telstra.net [139.130.121.165] (TPG VIC, AUSTRALIA)
8 4 ms 3 ms 4 ms bundle-ether10.way-core10.adelaide.telstra.net [203.50.11.152] (TESLTRA, AUSTRALIA)
9 17 ms 17 ms 16 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231] (TESLTRA, AUSTRALIA)
10 30 ms 31 ms 28 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124] (TESLTRA, AUSTRALIA)
11 27 ms 27 ms 27 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93] (TESLTRA, AUSTRALIA)
12 29 ms 29 ms 30 ms bundle-ether2.oxf-gw10.sydney.telstra.net [203.50.6.94] (TESLTRA, AUSTRALIA)
13 27 ms 27 ms 27 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94] (TESLTRA, AUSTRALIA)
14 185 ms 182 ms 181 ms i-84.eqnx-core02.telstraglobal.net [202.84.247.37] (TELSTRA, HONG KONG)
15 294 ms 293 ms 293 ms 202.84.140.214 (TELSTRA, HONG KONG)
16 284 ms 284 ms 284 ms 210.176.33.42 (TESLTRA, AUSTRALIA)
17 285 ms 286 ms 287 ms po110.bs-a.sech-osa.netarch.akamai.com [23.57.105.243] (AKAMAI TECH, NETHERLANDS)
18 291 ms 291 ms 290 ms a72-52-1-191.deploy.static.akamaitechnologies.com [72.52.1.191] (AKAMAI TECH, USA)
19 291 ms 291 ms 292 ms ae120.access-a.sech-osa.netarch.akamai.com [23.57.105.249] (AKAMAI TECH, NETHERLANDS)
20 296 ms 291 ms 292 ms 93.191.172.27 (AKAMAI TECH, EUROPE)
21 292 ms 292 ms 290 ms 93.191.173.29 (AKAMAI TECH, NETHERLANDS)
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
I resubscribed to get double VMA drops. Worst mistake ever. Ping is 100 more than it was last year during the Orsinium Event. Wasted my time and real life money.
I'm glad I've got Vermintide 2 and Borderlands 3 upcoming. The only reason my foot is still in the eso door is because of my friends of 4 years.
Why can't ZOS simply ditch Akamai and use whatever the other MMORPG's on the market use against DDoS protection?
Why can't ZOS simply ditch Akamai and use whatever the other MMORPG's on the market use against DDoS protection?
They're probably in an extended contract with Akamai, which would cost money to get out of. I think it's more a matter of whether they think the downsides of Akamai are worth the money they'd need to spend dropping Akamai.
SaucyMcSauceface wrote: »Why can't ZOS simply ditch Akamai and use whatever the other MMORPG's on the market use against DDoS protection?
They're probably in an extended contract with Akamai, which would cost money to get out of. I think it's more a matter of whether they think the downsides of Akamai are worth the money they'd need to spend dropping Akamai.
But they wont even acknowledge that. @ZOS_GinaBruno it would be really nice if you or someone could reply with something, even if it just says, "we are locked into an extended contract". The lack of a reason given is a little insulting based on how many comments this thread has.
TheGrandBizarre wrote: »Hi ZOS,
This is a quick tracert I did this evening. If you could go ahead and have a chat to your ddos scrubbing contractor about why my data is being routed through the Netherlands that would be greaaaaat.