Pinging 198.20.198.110 with 32 bytes of data: Reply from 198.20.198.110: bytes=32 time=64ms TTL=241 Reply from 198.20.198.110: bytes=32 time=52ms TTL=241 Reply from 198.20.198.110: bytes=32 time=48ms TTL=241 Reply from 198.20.198.110: bytes=32 time=57ms TTL=241 Ping statistics for 198.20.198.110: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 64ms, Average = 55ms
Tracing route to 198.20.198.110 over a maximum of 30 hops 1 1 ms 1 ms <1 ms Linksys23624 [192.168.1.1] 2 21 ms 23 ms 34 ms 96.120.88.65 3 13 ms 19 ms 15 ms be-10019-rur01.sanjose.ca.sfba.comcast.net [68.85.190.53] 4 13 ms 29 ms 12 ms be-231-rar01.santaclara.ca.sfba.comcast.net [162.151.78.249] 5 13 ms 11 ms 16 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73] 6 13 ms 15 ms 16 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14] 7 11 ms 10 ms 15 ms 96-87-8-2-static.hfc.comcastbusiness.net [96.87.8.2] 8 25 ms 13 ms 14 ms sjo-b21-link.telia.net [62.115.115.217] 9 20 ms 13 ms 16 ms akamai-ic-317106-sjo-b21.c.telia.net [62.115.146.109] 10 10 ms 12 ms 13 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194] 11 * * * Request timed out. 12 14 ms 15 ms 19 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] 13 * * * Request timed out. 14 55 ms 51 ms 55 ms 198.20.192.3 15 50 ms 49 ms 48 ms 198.20.198.110 Trace complete.
MLGProPlayer wrote: »I have 1 Gbit internet.
I average 120 ping in ESO, lol.
Cries in Australian.
Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.
Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.
Tracing route to 198.20.198.110 over a maximum of 30 hops 1 1 ms 1 ms <1 ms Linksys23624 [192.168.1.1] 2 21 ms 23 ms 34 ms 96.120.88.65 3 13 ms 19 ms 15 ms be-10019-rur01.sanjose.ca.sfba.comcast.net [68.85.190.53] 4 13 ms 29 ms 12 ms be-231-rar01.santaclara.ca.sfba.comcast.net [162.151.78.249] 5 13 ms 11 ms 16 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73] 6 13 ms 15 ms 16 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14] 7 11 ms 10 ms 15 ms 96-87-8-2-static.hfc.comcastbusiness.net [96.87.8.2] 8 25 ms 13 ms 14 ms sjo-b21-link.telia.net [62.115.115.217] 9 20 ms 13 ms 16 ms akamai-ic-317106-sjo-b21.c.telia.net [62.115.146.109] 10 10 ms 12 ms 13 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194] 11 * * * Request timed out. 12 14 ms 15 ms 19 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] 13 * * * Request timed out. 14 55 ms 51 ms 55 ms 198.20.192.3 15 50 ms 49 ms 48 ms 198.20.198.110 Trace complete.
Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.Tracing route to 198.20.198.110 over a maximum of 30 hops 1 1 ms 1 ms <1 ms Linksys23624 [192.168.1.1] 2 21 ms 23 ms 34 ms 96.120.88.65 3 13 ms 19 ms 15 ms be-10019-rur01.sanjose.ca.sfba.comcast.net [68.85.190.53] 4 13 ms 29 ms 12 ms be-231-rar01.santaclara.ca.sfba.comcast.net [162.151.78.249] 5 13 ms 11 ms 16 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73] 6 13 ms 15 ms 16 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14] 7 11 ms 10 ms 15 ms 96-87-8-2-static.hfc.comcastbusiness.net [96.87.8.2] 8 25 ms 13 ms 14 ms sjo-b21-link.telia.net [62.115.115.217] 9 20 ms 13 ms 16 ms akamai-ic-317106-sjo-b21.c.telia.net [62.115.146.109] 10 10 ms 12 ms 13 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194] 11 * * * Request timed out. 12 14 ms 15 ms 19 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] 13 * * * Request timed out. 14 55 ms 51 ms 55 ms 198.20.192.3 15 50 ms 49 ms 48 ms 198.20.198.110 Trace complete.
Interesting that TWO time out.
Siohwenoeht wrote: »Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.Tracing route to 198.20.198.110 over a maximum of 30 hops 1 1 ms 1 ms <1 ms Linksys23624 [192.168.1.1] 2 21 ms 23 ms 34 ms 96.120.88.65 3 13 ms 19 ms 15 ms be-10019-rur01.sanjose.ca.sfba.comcast.net [68.85.190.53] 4 13 ms 29 ms 12 ms be-231-rar01.santaclara.ca.sfba.comcast.net [162.151.78.249] 5 13 ms 11 ms 16 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73] 6 13 ms 15 ms 16 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14] 7 11 ms 10 ms 15 ms 96-87-8-2-static.hfc.comcastbusiness.net [96.87.8.2] 8 25 ms 13 ms 14 ms sjo-b21-link.telia.net [62.115.115.217] 9 20 ms 13 ms 16 ms akamai-ic-317106-sjo-b21.c.telia.net [62.115.146.109] 10 10 ms 12 ms 13 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194] 11 * * * Request timed out. 12 14 ms 15 ms 19 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] 13 * * * Request timed out. 14 55 ms 51 ms 55 ms 198.20.192.3 15 50 ms 49 ms 48 ms 198.20.198.110 Trace complete.
Interesting that TWO time out.
It is. I'm surprised that it sent you to Cali, but I guess Texas is geographically closer to there than Massachusetts. San Jose and Santa Clara are two of Akamai's west coast locations.
.Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.
It's worse for us Oceanic players, actually. It's well known that Akamai sends Oceanic traffic up into Asia and through the Singapore scrubbing center, before sending to the ESO servers. They started doing so just after the Singapore center opened up, which was around October-ish last year, which was around the time our ping basically doubled.
There was a 10 page thread in the tech support section filled with everybody's traces from all over the Oceanic region (multiple Aussie states, NZ, Asia), and they all showed more or less the same thing. There's a 30+ page thread about this in the general section, and of course there's no actual response from Zenimax.
I can use a VPN such as Mudfish to bypass Akamai's routing and force Akamai to deal with my traffic as if it was US traffic, but I refuse to support this game while I'm having to pay for a VPN to just have playable ping
195.122.154.1Siohwenoeht wrote: »Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.Tracing route to 198.20.198.110 over a maximum of 30 hops 1 1 ms 1 ms <1 ms Linksys23624 [192.168.1.1] 2 21 ms 23 ms 34 ms 96.120.88.65 3 13 ms 19 ms 15 ms be-10019-rur01.sanjose.ca.sfba.comcast.net [68.85.190.53] 4 13 ms 29 ms 12 ms be-231-rar01.santaclara.ca.sfba.comcast.net [162.151.78.249] 5 13 ms 11 ms 16 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73] 6 13 ms 15 ms 16 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14] 7 11 ms 10 ms 15 ms 96-87-8-2-static.hfc.comcastbusiness.net [96.87.8.2] 8 25 ms 13 ms 14 ms sjo-b21-link.telia.net [62.115.115.217] 9 20 ms 13 ms 16 ms akamai-ic-317106-sjo-b21.c.telia.net [62.115.146.109] 10 10 ms 12 ms 13 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200.184.194] 11 * * * Request timed out. 12 14 ms 15 ms 19 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197] 13 * * * Request timed out. 14 55 ms 51 ms 55 ms 198.20.192.3 15 50 ms 49 ms 48 ms 198.20.198.110 Trace complete.
Interesting that TWO time out.
It is. I'm surprised that it sent you to Cali, but I guess Texas is geographically closer to there than Massachusetts. San Jose and Santa Clara are two of Akamai's west coast locations.
I'm located in The Bay Area, but it doesn't seem to help ):
Tracing route to 198.20.198.110 over a maximum of 30 hops 1 2 ms 2 ms 1 ms router.charter.net [192.168.1.1] 2 15 ms 12 ms 13 ms 10.117.118.5 3 15 ms 18 ms 13 ms 72-31-238-225.net.bhntampa.com [72.31.238.225] 4 12 ms 11 ms 17 ms 72-31-238-242.net.bhntampa.com [72.31.238.242] 5 16 ms 13 ms 16 ms 72-31-238-216.net.bhntampa.com [72.31.238.216] 6 42 ms 40 ms 37 ms 10.bu-ether15.atlngamq46w-bcr01.tbone.rr.com [66.109.6.222] 7 37 ms 39 ms 38 ms bu-ether18.atlngamq46-bcr00.tbone.rr.com [66.109.6.40] 8 37 ms 39 ms 39 ms 107.14.19.19 9 30 ms 33 ms 32 ms ix-ae-14-0.tcore1.a56-atlanta.as6453.net [64.86.113.37] 10 48 ms 41 ms 47 ms if-ae-43-2.tcore2.a56-atlanta.as6453.net [64.86.113.150] 11 47 ms 194 ms 46 ms if-ae-21-2.tcore1.aeq-ashburn.as6453.net [66.198.154.24] 12 46 ms 46 ms 48 ms 66.198.154.66 13 54 ms 52 ms 55 ms po111.bs-b.sech-iad.netarch.akamai.com [209.200.144.202] 14 * * * Request timed out. 15 53 ms 58 ms 68 ms ae121.access-a.sech-iad.netarch.akamai.com [209.200.144.205]
Betty_Booms wrote: »Was 280 ms a couple of weeks ago. Now 410 ms +. I dont pvp anymore as a result.
.Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.
It's worse for us Oceanic players, actually. It's well known that Akamai sends Oceanic traffic up into Asia and through the Singapore scrubbing center, before sending to the ESO servers. They started doing so just after the Singapore center opened up, which was around October-ish last year, which was around the time our ping basically doubled.
There was a 10 page thread in the tech support section filled with everybody's traces from all over the Oceanic region (multiple Aussie states, NZ, Asia), and they all showed more or less the same thing. There's a 30+ page thread about this in the general section, and of course there's no actual response from Zenimax.
I can use a VPN such as Mudfish to bypass Akamai's routing and force Akamai to deal with my traffic as if it was US traffic, but I refuse to support this game while I'm having to pay for a VPN to just have playable ping
Zenimax made a big mistake by trusting megaserver technology when it was clearly not ready yet. What they should have done was the WoW shift, everyones on servers, but sharded. This way you can play with anyone, go to any phase if you have a friend etc.... I don't know. Megaservers are nice, but this is the cost.
100 Mbit internet. Generally not lower than about 96, usually it's in 98-104 range, unless I'm in Cyrodiil, then it usually doesn't drop below 110. Even with that, the delays in actions often feel like lot higher ping than is displayed. Located in Europe so that ping is to be expected I guess.
.Siohwenoeht wrote: »Have you run a trace of the routing? I'd bet you're shipped to Boston before being sent to the ESO physical servers. All traffic for ESO travels through Akamai first.
It's worse for us Oceanic players, actually. It's well known that Akamai sends Oceanic traffic up into Asia and through the Singapore scrubbing center, before sending to the ESO servers. They started doing so just after the Singapore center opened up, which was around October-ish last year, which was around the time our ping basically doubled.
There was a 10 page thread in the tech support section filled with everybody's traces from all over the Oceanic region (multiple Aussie states, NZ, Asia), and they all showed more or less the same thing. There's a 30+ page thread about this in the general section, and of course there's no actual response from Zenimax.
I can use a VPN such as Mudfish to bypass Akamai's routing and force Akamai to deal with my traffic as if it was US traffic, but I refuse to support this game while I'm having to pay for a VPN to just have playable ping
Zenimax made a big mistake by trusting megaserver technology when it was clearly not ready yet. What they should have done was the WoW shift, everyones on servers, but sharded. This way you can play with anyone, go to any phase if you have a friend etc.... I don't know. Megaservers are nice, but this is the cost.
Unfortunately, I think it's just too late to do something like this. Too much work and resources would be needed to redesign the server infrastructure around that sort of system, on top of actually setting up regional servers around the globe. Then consider the fact that the game would be offline for at least a year or two, which could very possibly kill the game.
To be honest, 250-300 doesn't bother me. It can get annoying, rolling just out of an AoE and still being hit, but it's playable.
What's not *** playable is 350+, which is what I get if I don't have a VPN up, specifically because of Akamai's *** routing. Drop Akamai so our ping is back to the 250-300 it usually is, work on improving servers so it goes back to the 200-250 it was when I started playing (just before 1T), and I'm good.
<snip>
In-game /latency shows 100+ So what is /latency calculating? Is it accurate? Is this how bad the client is for client to server relation?
TRACER (NA)
<snip>