Reporting Latency Related Issue (NA Data Center)

[Sub-Xero]

•Name of your Internet Service Provider (ISP): Comcast
•Ticket or reference number from your ISP: Unable to obtain one.
•State/Country: WA, USA
•Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.: This started happening consistently for me about three weeks ago. It happens every, single evening around the same time(s). It generally starts around 3-4PM PST and ends around 730-8PM PST.
•Frequency (How often does the issue occur?): Every evening/night.
•Content (Which content were you playing in-game when the issue occurred?): Any and all content.
•Which in-game World were you playing on when the issue occurred?: Gilgamesh.
•Traceroute records: Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 11 ms 11 ms te-0-0-0-4-sur01.tumwater.wa.seattle.comcast.net [68.86.113.97]
4 23 ms 13 ms 13 ms be-44-ar01.burien.wa.seattle.comcast.net [69.139.164.18]
5 14 ms 16 ms 12 ms 4.68.71.77
6 84 ms 84 ms 83 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]
7 83 ms 83 ms 86 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
8 * * * Request timed out.
9 83 ms 83 ms 82 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
10 272 ms 213 ms 214 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
11 84 ms 92 ms 84 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 128 ms 96 ms 96 ms 192.34.76.10
13 97 ms 106 ms 96 ms 199.91.189.242

Every hop after that is "request timed out."

[Desire]

now getting dc'd every few min PLEASE fix this is stupid!

see previous post for info

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 7 ms 3 ms 5 ms 192.168.1.1
2 21 ms 33 ms 19 ms 96.120.24.209
3 20 ms 11 ms 8 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 18 ms 15 ms 19 ms te-2-7-0-7-ar01.area4.il.chicago.comcast.net [68.86.196.201]
5 * * * Request timed out.
6 200 ms 213 ms 218 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 178 ms 116 ms 210 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 34 ms 33 ms 38 ms 4.59.178.62
9 50 ms 54 ms 47 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 43 ms 41 ms 42 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 61 ms 49 ms 41 ms 174.142.115.218
12 42 ms 41 ms 41 ms 184.107.107.176

Trace complete.


Tracing route to 184.107.107.176 over a maximum of 30 hops

1 2 ms <1 ms 1 ms 192.168.1.1
2 18 ms 17 ms 11 ms 96.120.24.209
3 16 ms 10 ms 17 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 12 ms 14 ms 28 ms te-8-2-ur01.griffith.in.chicago.comcast.net [69.139.201.69]
5 * * * Request timed out.
6 33 ms 32 ms 40 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 33 ms 35 ms 37 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 32 ms 34 ms 33 ms 4.59.178.62
9 * * 47 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 57 ms 41 ms 40 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 40 ms 40 ms 42 ms 174.142.115.218
12 41 ms 42 ms 42 ms 184.107.107.176

Trace complete.

[Skaw]

•Name of your Internet Service Provider (ISP): Mediacom Cable Internet AND T-Mobile Mobile Broadband.
•Ticket or reference number from your ISP: Not a local issue. Whenever issues arise it's always in Canada, close to the data center.
•State/Country: Deleware, USA
•Date/Time: Feb 1st, 2016, 9:15 PM Eastern
•Frequency (How often does the issue occur?): Nightly for the most part of the last 3 or 4 months, usually between 6:30 PM and 10:30 PM.
•Content (Which content were you playing in-game when the issue occurred?): All content.
•Which in-game World were you playing on when the issue occurred?: Lamia
•Traceroute records:


Several 90002 disconnects tonight, first time it's been bad enough to make the game completely unplayable rather than just a huge inconvenience.

[Starbirth]

Name of your Internet Service Provider (ISP) Comcast
Ticket or reference number from your ISP. They say nothing is wrong on their end.
State/Country CA/USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) 4-11 pm
Frequency (How often does the issue occur?) Every night
Content (Which content were you playing in-game when the issue occurred?) It's everywhere
Which in-game World were you playing on when the issue occurred? Cactuar

Traceroute records

1 <1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 10 ms 17 ms 96.120.14.145
3 12 ms 23 ms 9 ms xe-4-3-2-sur03.sacramento.ca.ccal.comcast.net [69.139.197.253]
4 14 ms 10 ms 8 ms ae-2-ar01.sacramento.ca.ccal.comcast.net [162.151.18.133]
5 * * 15 ms lag-7.ear1.Sacramento.Level3.net [4.68.71.29]
6 253 ms 170 ms 101 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 87 ms 94 ms 86 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 88 ms 104 ms 97 ms 4.59.178.62
9 96 ms 104 ms 94 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 112 ms 89 ms 97 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 100 ms 90 ms 90 ms 174.142.115.218
12 90 ms 91 ms 91 ms 184.107.107.176

Trace complete.


This has to get fixed from SE's end because there is nothing more I can do.

[Filter41]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP.: ?
State/Country: IL USA
Date/Time: Every Night, Every Day
Frequency: Constant
Content: Everything.
Which in-game World were you playing on when the issue occurred? Balmungg
Traceroute records: Level3 packet loss in montreal every time.

[Phracia]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: >.>; lvl 1 support is a joke
State/Country: Pennsylvania
Date/Time: This problem occurs nightly anywhere between 7pm to 12am eastern.
Frequency: Nightly! Lag spikes occur roughly every 10-30 seconds, with the occasional smooth spots of a few minutes.
Content: This issue occurs in all content! Overworld, instanced dungeons, inn, you name it!
World: Leviathan
Traceroute records:

Okay! Here's where I get to have fun. So I traced the route off the server's IP that I ripped from the resource manager and pinged a silly number of packets off the server to get a feel for the frequency of packet loss. Seeing no more than 25 consecutive packets without loss at its best, I decided 50 packets was a fair enough number to ping off of each IP tracing my hops back till I found one without issue. The first ip in the series to lose packets was one that I keep seeing crop up time and again; 192.34.76.10 . Now I'm not sure whether this is a server that SE's NA datacenter has anything to do with, or if it might perhaps be a poor neglected local node of lvl3's. Without any real networking expertise and nothing besides the ip to identify the hop, I've got no clue what it is. It does seem a likely origin to at least a bunch of problems, however! Here are a bunch of links to cropped screenshots of command prompt trace routing and pinging fun! (Wish I could have spoil hid a bunch of the images, but I can't figure out how to make spoilers work >.>)

Route Trace!
11th Hop Ping
10th Hop Ping
9th Hop Ping
8th Hop Ping
6th and 7th Hop Ping
5th Hop Ping
4th Hop Ping

I have not included any closer than 4th hop as evidence because it would be kind of obnoxious to keep personal stuffs personal that close. Rest assured the trend remains the same of all clear till 192.34.76.10. lvl3's network shows some high latency pings, but I suspect this might be a case of decreased ping priority as a subsequent hop shows all clear.

Anyway! Hope this helps in getting things sorted, though I suspect there are many more with more experience and greater depth of understanding working on this problem than myself, so I'm unsure just how big a help this would be. Good luck and cheers!