I do have a ticket open with support on this as well
for Elder Scrolls Online (http://www.elderscrollsonline.com)
Question Reference # 180920-003202
akamai.com the bottle neck appears to be at YOUR
network! Some of the information in here may not
be relevant for you akamai.com but please read
the full email this was also sent in a ticket on
Elder Scrolls Online as well.
Ok so there seems to be a constant latency to the
Elder Scrolls online North America servers.
I am getting a latency a lot of time in excess of
Now so you know I am a trained network admin myself
and I know the issue is NOT on my side here.
I am on a wired connection and on a machine powerful
enough to handle this game.
Intel i7-2500 3.40 Ghz 16 GB of RAM running
Windows 10 Pro (64 bit)
So I know the issue is not here on my side because
I know my network and everything is updated including
my router and please don't tell me to open up ports
I have already tried it. It does not solve the issue.
So I first used Wireshark to find out the IP for
the server which I was on it appears to be
184.108.40.206 which of course comes back to Zenimax
as the owner as expected.https://whois.arin.net/rest/net/NET-198-20-192-0-1/pft?s=220.127.116.11
So since the latency can be caused anywhere along
a hop that may be congested so I started to do several
traceroute to 18.104.22.168 (22.214.171.124), 30 hops max, 60 byte packets
1 router.lan.darkshado.ca (192.168.0.1) 0.445 ms 0.541 ms 1.029 ms
2 rc1we-be107-1.ed.shawcable.net (126.96.36.199) 9.895 ms 9.907 ms 11.333 ms
3 rc3no-be6.cg.shawcable.net (188.8.131.52) 13.619 ms 14.279 ms 14.324 ms
4 rc2wt-be100.wa.shawcable.net (184.108.40.206) 29.925 ms 29.882 ms 29.833 ms
5 rc1wt-be18-1.wa.shawcable.net (220.127.116.11) 30.010 ms 29.878 ms rc4sj-be60.cl.shawcable.net (18.104.22.168) 50.815 ms
6 rc3sj-be60.cl.shawcable.net (22.214.171.124) 49.131 ms 47.988 ms 47.940 ms
7 akamai.prolexic.com (126.96.36.199) 53.334 ms 47.109 ms 46.701 ms
8 po110.bs-a.sech-sjc.netarch.akamai.com (188.8.131.52) 48.783 ms po110.bs-b.sech-sjc.netarch.akamai.com (184.108.40.206) 48.713 ms po110.bs-a.sech-sjc.netarch.akamai.com (220.127.116.11) 48.742 ms
9 ae120.access-a.sech-sjc.netarch.akamai.com (18.104.22.168) 266.280 ms ae121.access-a.sech-sjc.netarch.akamai.com (22.214.171.124) 265.902 ms 266.602 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 ae120.access-a.sech-sjc.netarch.akamai.com (126.96.36.199) 233.638 ms !X * *
well that really isn't good 265 MS just one hop inside of akamai's network
so it hits the routers on the border and the times are great at about 48 ms
Now where ever that piece of equipment is, is severely congested and that appears
to be where the latency issue is coming from.
The stars don't bother me at all because I know that you can setup a piece of
equipment to not answer ICMP requests which is more than likely what
akamai.com is doing since they are an anti-ddos type service.
But what does bother me is the huge jump in the latency time once it gets past
border switches on akamai.com it takes a huge jump from 48 ms to 265 ms
at IP 188.8.131.52 and as I said it is constant I did multiple traceroutes
and it seems like it bottlenecks in the same place every time.
Akamai is a anti-ddos service and I understand why they use them but
thier equipment should be able to handle the load the game servers
will put on it and it appears that it isn't right now.
Now this was done on September 20 2018 at about 4:00 PM MST (GMT-0700)
Come on can some one at the support please get in contact with akamai.com
and have them resolve this issue please.
Looks like I am not the only one this is just one example of many that
you can find about a high latency.https://forums.elderscrollsonline.com/en/discussion/435522/disconnections-rubber-banding-high-latency-spikes-and-my-tech-support-ticket-180910-002528
Also I have tried disabling any security software I have which is
Kaspersky 184.108.40.2065(i) and that does NOT fix the issue the issue
clearly is NOT on my end at all and this isn't a connection
issue here on my side.
I will also email this to the Network Operations Center ("NOC") at
akamai.com to see if they can take a look into the issue.
Oh so a bit of an update at the request of Akamai.com they wanted me to do a tracetcp which I did
on September 21 2018 about 11:50 AM MST (GMT-0700)
Tracing route to 220.127.116.11 on port 80
Over a maximum of 30 hops.
1 1 ms 1 ms 1 ms 192.168.0.1 [router.lan.darkshado.ca]
2 25 ms 11 ms 10 ms 18.104.22.168 [rc1we-be107-1.ed.shawcable.net]
3 16 ms 17 ms 14 ms 22.214.171.124 [rc3no-be6.cg.shawcable.net]
4 31 ms 28 ms 29 ms 126.96.36.199 [rc2wt-be100.wa.shawcable.net]
5 50 ms 52 ms 30 ms 188.8.131.52 [rc1wt-be18-1.wa.shawcable.net]
6 49 ms 50 ms 54 ms 184.108.40.206 [rc3sj-tge0-0-0-0.cl.shawcable.net]
7 48 ms 48 ms 49 ms 220.127.116.11 [akamai.prolexic.com]
8 49 ms 48 ms 48 ms 18.104.22.168 [po110.bs-a.sech-sjc.netarch.akamai.com]
9 259 ms * * 22.214.171.124 [ae121.access-a.sech-sjc.netarch.akamai.com]
10 * * * Request timed out.
11 * 76 ms 77 ms 126.96.36.199
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
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.
Now you can see at hop 8 everything is great which again is the boarder of their
network at akamai.com but once again once it hits the 2nd hop inside of akamai.com
it only answers once and is at 259 ms.
On hop 8 again it is about 48 - 49 MS which is great and then on hop 9
once again it jumps up to 259 ms.
Again this issue is definately inside of akamai.com's network but these guys are idiots
at akamai.com and claim they won't do anything unless one of their customers complain
about the issue. Which would have to be Zenimax.
These guys are complete idiots at akamai.com I have a ticket open with them
as well AKAM-NOCC #B-P-2HW3BOR
If you are getting the same problem be sure to email
nocc-tix -[at]- akamai.com, nocc-shift -[at]- akamai.com, noc -[at]- akamai.com,
support -[at]- akamai.com
Can some one from Zenimax please complain to them about this issue and get this
fixed the people at akamai.com have no clue how to properly run their network and
the bottle neck clearly is within their network but they refuse to do anything because
I am not their direct "customer".
I hate idiot companies like this I have as much or more training in the computer field
that than that idiot that answered the ticket.