One of my posts bumping this to the first page was deleted so somebody is reading this.
ZOS could you at least acknowledge the issue and let us know you're looking into fixing it? Because the game is becoming very, very hard to play and you are going to lose customers without a reliable connection. I can live with 270-300, but over 300 is impossible.
I can live with 270-300, but over 300 is impossible.
n_philipsonrwb17_ESO wrote: »I can live with 270-300, but over 300 is impossible.
Screw that I want my 200 ping back. If free games can do it these guys should easily be able to manage a somewhat decent connection for us oceanic folks. Also its not just the high ping its the horrible spikes which makes the game unplayable so they need to sort out this akamai routing BS.
Sending our game packets through the Netherlands ? Really ?
No reply from anyone at ZoS. This is what i'v been dealing with for the last few weeks now.
https://youtu.be/_L93RS8YCgY"[/url]
It'd be interesting to leaving something like PingPlotter running to check if there are any packet loss or jitter issues between you and either the Akamai node or ESO servers causing the spiking.This issue can happen at any time of day in any zone. Normal pings before this issue arose were 250-270ms a couple of weeks ago "use to be 180ms at launch" now it sits at a constant 330+ms and then the rubberbanding and lag spikes happen randomly.
If your ping went up by yet again on Friday, I read that apparently there's issues with the SMW3 cable. Again. This means traffic to Asia just took a nose-dive while it's rerouted elsewhere. Unfortunately this causes even more issues for us in Aus due to the use of the Akamai node up there for ESO.
Or here's a novel idea - only turn on the Akamai DDOS scrubbing when you're actually under DDOS attack.
The game was FINE before Akamai got involved, and what for me was once a reliable 200ms latency from here in Melbourne first went up to 260-280ms once Akamai got involved, and is now 380-400ms and climbing.
I'm sure the Akamai service provides a valuable "hail mary" save when a DDOS attack happens, but the rest of the time it should not be being used at all. The game was fine for YEARS without it, after all. It's adding 50-100ms latency just from being in the chain at all (it's clearly not designed to handle real-time game server traffic) and with the extra routing Australia and NZ players have to deal with now, it's a joke.
I mean, I literally just DIE my way through delves world bosses and quests now. There's literally no point in following mechanics because the mechanic is already over by the time the server hears from you, so you cop the full force of it anyway. SO I die and die and die and die and am very thankful for all those Crown repair kits so I don't have to lose gold on it (I just wait till my gear's broken, patch up and go back to the dying
Come on, ZOS. You're better than this. Your game's amazing, you're a massive company, and Australia and New Zealand are not *** backwaters - after, all, your game director's here right now!
Fix this problem the ONLY way it can be fixed - turn Akamai OFF.
It'll make the game playable again for Australia and NZ and noticeably improve it for everyone else.
Didn't an Aussie community manager join ESO last year? Why is he silent? Delayed by lag?
Didn't an Aussie community manager join ESO last year? Why is he silent? Delayed by lag?
Yes, they do have a "aussie" community manager, they normally dont speak on issues they cant answer and zos has always had a "head in the sand" approach to most things technical.
This topic has been brought up time and time again, unfortunately they already have your money and the cash flow is still strong from eso+ and crowns... So why spend money on a service when they can do nothing and get the same amount of money? (If the community as a whole stops giving them money in those two areas, you may get results)
Any Australians on NBN go Aussie broadband and thank me later. They do not have contention ratio issues so you won't drop bandwidth at peak times.
Any Australians on NBN go Aussie broadband and thank me later. They do not have contention ratio issues so you won't drop bandwidth at peak times.
What's your current in game latency? Have you experienced a surge in latency over the last few weeks? Any chance you could do a tracert to 198.20.198.110 and post it here?
Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms 8 ms 7 ms xyz
2 10 ms 10 ms 10 ms xyz.yourdc.adl.aussiebb.net [xyz]
3 10 ms 10 ms 10 ms Bundle-Ether15.fli-edge902.adelaide.telstra.net [110.145.209.37]
4 46 ms 11 ms 11 ms bundle-ether9.fli-core1.adelaide.telstra.net [203.50.11.150]
5 19 ms 18 ms 18 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
6 31 ms 31 ms 31 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 30 ms 31 ms 31 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 31 ms 31 ms 31 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 173 ms 171 ms 171 ms 202.84.143.190
10 141 ms 142 ms 141 ms 202.84.140.74
11 143 ms 142 ms 144 ms 202.47.216.245
12 169 ms 169 ms 169 ms 202.47.216.250
13 170 ms 170 ms 170 ms unknown.telstraglobal.net [202.127.69.38]
14 170 ms 170 ms 170 ms po110.bs-a.sech-tyo.netarch.akamai.com [72.52.56.192]
15 169 ms 169 ms 169 ms ae120.access-a.sech-tyo.netarch.akamai.com [72.52.56.197]
16 * * * Request timed out.
17 273 ms 273 ms 273 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
18 273 ms 273 ms 273 ms 198.20.192.4
19 272 ms 272 ms 272 ms 198.20.198.110
Trace complete.
Any Australians on NBN go Aussie broadband and thank me later. They do not have contention ratio issues so you won't drop bandwidth at peak times.
Any Australians on NBN go Aussie broadband and thank me later. They do not have contention ratio issues so you won't drop bandwidth at peak times.
What's your current in game latency? Have you experienced a surge in latency over the last few weeks? Any chance you could do a tracert to 198.20.198.110 and post it here?
I'm also with Aussie, and we also experienced the latency jump by routing to HK Akamai node. Propagate is referring to the '6pm slowdown' Netflix effect that other RSPs may suffer from - this contention causes packet loss and can cause rubberbanding or outright disconnects where the game world appears to just 'freeze'. I may have 360ms in-game latency (without a VPN) but at least it's consistent with very little spiking.
As ABB use Telstra Global for international transit, the traces should be similar to Telstra. Looking now with the SMW3 cable out, we're being instead pushed to a Tokyo Akamai node?Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms 8 ms 7 ms xyz
2 10 ms 10 ms 10 ms xyz.yourdc.adl.aussiebb.net [xyz]
3 10 ms 10 ms 10 ms Bundle-Ether15.fli-edge902.adelaide.telstra.net [110.145.209.37]
4 46 ms 11 ms 11 ms bundle-ether9.fli-core1.adelaide.telstra.net [203.50.11.150]
5 19 ms 18 ms 18 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
6 31 ms 31 ms 31 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 30 ms 31 ms 31 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 31 ms 31 ms 31 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 173 ms 171 ms 171 ms 202.84.143.190
10 141 ms 142 ms 141 ms 202.84.140.74
11 143 ms 142 ms 144 ms 202.47.216.245
12 169 ms 169 ms 169 ms 202.47.216.250
13 170 ms 170 ms 170 ms unknown.telstraglobal.net [202.127.69.38]
14 170 ms 170 ms 170 ms po110.bs-a.sech-tyo.netarch.akamai.com [72.52.56.192]
15 169 ms 169 ms 169 ms ae120.access-a.sech-tyo.netarch.akamai.com [72.52.56.197]
16 * * * Request timed out.
17 273 ms 273 ms 273 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
18 273 ms 273 ms 273 ms 198.20.192.4
19 272 ms 272 ms 272 ms 198.20.198.110
Trace complete.
Any Australians on NBN go Aussie broadband and thank me later. They do not have contention ratio issues so you won't drop bandwidth at peak times.
What's your current in game latency? Have you experienced a surge in latency over the last few weeks? Any chance you could do a tracert to 198.20.198.110 and post it here?
I'm also with Aussie, and we also experienced the latency jump by routing to HK Akamai node. Propagate is referring to the '6pm slowdown' Netflix effect that other RSPs may suffer from - this contention causes packet loss and can cause rubberbanding or outright disconnects where the game world appears to just 'freeze'. I may have 360ms in-game latency (without a VPN) but at least it's consistent with very little spiking.
As ABB use Telstra Global for international transit, the traces should be similar to Telstra. Looking now with the SMW3 cable out, we're being instead pushed to a Tokyo Akamai node?Tracing route to 198.20.198.110 over a maximum of 30 hops
1 <1 ms 8 ms 7 ms xyz
2 10 ms 10 ms 10 ms xyz.yourdc.adl.aussiebb.net [xyz]
3 10 ms 10 ms 10 ms Bundle-Ether15.fli-edge902.adelaide.telstra.net [110.145.209.37]
4 46 ms 11 ms 11 ms bundle-ether9.fli-core1.adelaide.telstra.net [203.50.11.150]
5 19 ms 18 ms 18 ms bundle-ether16.win-core10.melbourne.telstra.net [203.50.6.229]
6 31 ms 31 ms 31 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 30 ms 31 ms 31 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 31 ms 31 ms 31 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 173 ms 171 ms 171 ms 202.84.143.190
10 141 ms 142 ms 141 ms 202.84.140.74
11 143 ms 142 ms 144 ms 202.47.216.245
12 169 ms 169 ms 169 ms 202.47.216.250
13 170 ms 170 ms 170 ms unknown.telstraglobal.net [202.127.69.38]
14 170 ms 170 ms 170 ms po110.bs-a.sech-tyo.netarch.akamai.com [72.52.56.192]
15 169 ms 169 ms 169 ms ae120.access-a.sech-tyo.netarch.akamai.com [72.52.56.197]
16 * * * Request timed out.
17 273 ms 273 ms 273 ms a72-52-29-88.deploy.static.akamaitechnologies.com [72.52.29.88]
18 273 ms 273 ms 273 ms 198.20.192.4
19 272 ms 272 ms 272 ms 198.20.198.110
Trace complete.
Yeah I'm with Leaptel who also use Telstra as their backbone. I find it amusing yours goes adelaide>melbourne>sydney>Japan while us Queenslanders are going Sydney>Melbourne>Adelaide>Perth>HK.
I'll check mine again tonight when I get home from work and see if I'm being sent to japan or hk now.