A large yellow rectangle
lordrichter wrote: »<SNIP>
With Akamai, you will probably get a response. Not immediately, but I bet they do respond. They will probably send you an email back telling you to contact ZOS. Then again, they might collect information from you and add it to a pile of work to be looked at.
<SNIP>
We understand your concern. Could you please raise this concern with Akamai's customer whose services your customer is using, they would in turn raise a case with Akamai and have this investigated.
We are unable to accept this request due to compliance policy. As per the policy, we are to take request coming from direct customers of Akamai alone.
If you'd like to investigate more, please bring this up with our customer and they'd take this further with us.
A large yellow rectangle
What I don't understand is how there has been zero communication from ZOS on this.
"We're looking into this"
"Thank you for bringing this to our attention. We will let you know if there are any updates"
"Unfortunately, we are not able to publicly discuss this specific issue. However, we would like to reassure you that we are aware of it"
Not a single peep. That's what makes it so strange.
Lelldorano wrote: »So I just tried out mudfish VPN to see if it would make any difference. Went from a 300+ ping with horrible spikes to 220-250 and no spikes! This is connecting from NZ on spark fibre. You get some free credit when signing up so don't have to pay anything to try it.
The fact a VPN works like this proves that it isn't our fault, right ?
lordrichter wrote: »Lelldorano wrote: »So I just tried out mudfish VPN to see if it would make any difference. Went from a 300+ ping with horrible spikes to 220-250 and no spikes! This is connecting from NZ on spark fibre. You get some free credit when signing up so don't have to pay anything to try it.
The fact a VPN works like this proves that it isn't our fault, right ?
Where is your VPN coming out? Do you know? (trace route)
A large yellow rectangle
Lelldorano wrote: »Tracing route to 198.20.200.155 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.254.106.1
2 174 ms 174 ms 174 ms 10.254.254.1
3 174 ms 174 ms 174 ms 10.255.242.46
4 * * * Request timed out.
5 196 ms 207 ms 187 ms 45.32.142.65
6 * * * Request timed out.
7 176 ms 178 ms 177 ms xe-0-0-14-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.207.197]
8 175 ms 175 ms 176 ms ae-8.r11.snjsca04.us.ce.gin.ntt.net [165.254.191.154]
9 175 ms 175 ms 175 ms po110.bs-b.sech-sjc.netarch.akamai.com [209.200.184.200]
10 175 ms 175 ms 175 ms po587-10.bs-a.sech-ams.netarch.akamai.com [72.52.1.201]
11 175 ms 175 ms 176 ms ae121.access-a.sech-sjc.netarch.akamai.com [209.200.184.205]
12 * * * Request timed out.
13 214 ms 213 ms 213 ms 198.20.192.3
14 214 ms 213 ms 213 ms 198.20.200.155
Trace complete.
Simply put folks, its about contracts ZOS made a contract with Scrubber service provider, potentially at least for a year. And paid loads of money for it. They would cancel/bin it only if the damages caused by this service outweighs the cost of the contract. So I'd say, nothing will be fixed within 12 months since this dDOS protection was implemented.
Those in power only have the illusion they are powerful, however in reality, those in power are only so because we allow them to be.
Those in power only have the illusion they are powerful, however in reality, those in power are only so because we allow them to be.
The sad truth is a majority of players don't even know these forums exist most likely, let alone use them, so even though is this an 8-page topic, it's also taken several months for it to reach that number. In ZOS' eyes that probably means such a tiny percent of players seem to be having a problem so there must be no problem, even if hundreds or even thousands of NZ/AU players are actually experiencing this problem.
First, I'm no expert on the network topology and I don't like the game lag. This is IMHO only.
But this is a hot post and it seems like the pings are misunderstood. Pings are a one time measurement of a special TCP message trip through the network. I have noticed that pings like speed tests can fly through the net and provide no indication that the net is slow. I am told that is because lost packets are a bigger concern and they happen due to arriving too late to be valid. You may have a wonderful ping and loosing 5 in 15 packets which makes your message rate go down and that means lag goes up. Messages may be selectively delayed due to network priorities set by unknown people .
Lag is caused by information not arriving in time.
Pings do not measure successful information rates. At best they may be a theoretical maximum.
I doubt this is a ZOS problem. It's like my complaining to Subaru that Chevron is selling me junk gas. Or me complaining my gas mileage is really low using Mityfine Gas. You may believe that ZOS should be able to buy their way out of this but that may not be true. It could be too expensive. Who do you think will get priority on the net, NFL or ZOS?
Ultimately there's three sources of 'lag' in play here. What you mention is about the bandwidth/congestion of the links between you and the servers. This is where packet loss occurs along the path (and in-game you get the random 999+ spurts, regardless of your in-game location). Sometimes this is your ISP, sometimes it is further along outside the ISP's control.
But all Comcast support can do is send someone to check our internet box (which appears to be working fine). Running a trace to that IP address above results in "response timed out" for every Akamai hop. When my ESO connection is stalling, other internet connections work fine. Issue started out of nowhere 3 weeks ago, worked fine before.10 --- 1/ 1 =100% 0/ 1 = 0% 209.200.184.194