Reporting Latency Related Issue (NA Data Center)

[Otomis]

Comcast
Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP. Contacted ISP several times it is not on their end or mine.
State/Country: IN, USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) Past few weeks.
Frequency (How often does the issue occur?) Everyday, Prime time EST 5pm-11pm.
Content (Which content were you playing in-game when the issue occurred?) Entire game is laggy, but dungeons or savage are horrid.
Which in-game World were you playing on when the issue occurred? Siren
Traceroute records:

[IMG][/IMG]

When Running a PING Test I would occasionally get a "Timed Out" message.
The game is not enjoyable at this rate. I hope something is figured out soon or I am done.

[MoruteAshera]

• ISP: Xfinity Comcast
• Ticket #: Did not get one this time. There have been three techs out to the place for the last two months, one modem swapped out by them and forwarded/reset everything on their end and mine multiple times. They say that it is not their lines or their services causing it and boy do those technician charges add up.
• State/Country: Washington State
• Date/Time: 01-25-16 / 01-28-16 @ 6pm-9pm PST.
• Frequency: Spikes between 1 GDC to 3 minute freezes.
• Content: Roulettes (lvl 50, 60, expert), Void Ark, Thordan EX, Savage Alexander 1-4
• Server: Primal
• World: Behemoth
• Traceroute:
  

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 3 ms 2 ms 1 ms 10.0.0.1
  2 * * * Request timed out.
  3 18 ms 14 ms 17 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 21 ms 17 ms 16 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 35 ms 19 ms 19 ms 4.68.71.73
  6 86 ms 91 ms 91 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 90 ms 92 ms 99 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 88 ms 89 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 134 ms 124 ms 192.34.76.10
  10 126 ms 124 ms 124 ms 199.91.189.242
  11 120 ms 121 ms 128 ms 199.91.189.40
  
  Trace complete.

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 2 ms 5 ms 4 ms 10.0.0.1
  2 * * * Request timed out.
  3 16 ms 13 ms 16 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 20 ms 19 ms 34 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 33 ms 19 ms 29 ms 4.68.71.73
  6 86 ms 85 ms 89 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 119 ms 98 ms 89 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 87 ms 89 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 189 ms 128 ms 192.34.76.10
  10 125 ms 119 ms 123 ms 199.91.189.242
  11 121 ms 135 ms 130 ms 199.91.189.40
  
  Trace complete.

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 7 ms 4 ms 4 ms 10.0.0.1
  2 * * * Request timed out.
  3 18 ms 19 ms 45 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 17 ms 20 ms 24 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 23 ms 14 ms 19 ms 4.68.71.73
  6 85 ms 87 ms 85 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 86 ms 95 ms 88 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 87 ms 89 ms 89 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 124 ms 124 ms 192.34.76.10
  10 122 ms 123 ms 139 ms 199.91.189.242
  11 123 ms 124 ms 124 ms 199.91.189.40
  
  Trace complete.

[NolLacnala]

• Name of your Internet Service Provider: Comcast
• Ticket or reference number from your ISP: NA
• State/Country: Sacramento, CA USA
• Date/Time: Shortly after Heavensward, somewhere from patch 3.05 to 3.1
• Frequency: Every day from 4pm to 7pm PST
• Content: All, most noticeable in Alexander Savage
• Which in-game World were you playing on when the issue occurred?: Cactuar
• Traceroute records: To Cactuar, see below

tracert 199.91.189.23

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 21 ms 9 ms 96.120.14.97
4 10 ms 9 ms 8 ms xe-11-2-1-sur02.yubacity.ca.ccal.comcast.net [68.87.203.217]
5 16 ms 17 ms 17 ms ae-15-ar01.fresno.ca.ccal.comcast.net [162.151.40.61]
6 22 ms 22 ms 21 ms ae-20.edge2.SanJose.Level3.net [4.68.71.25]
7 92 ms 92 ms 92 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

8 96 ms 92 ms 93 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

9 93 ms 93 ms 92 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 133 ms 101 ms 107 ms 192.34.76.10
11 101 ms 102 ms 102 ms 199.91.189.242
12 101 ms 101 ms 101 ms 199.91.189.23

Trace complete.

ping 68.87.203.217 -n 30

Pinging 68.87.203.217 with 32 bytes of data:
Reply from 68.87.203.217: bytes=32 time=11ms TTL=61
General failure.
Reply from 68.87.203.217: bytes=32 time=11ms TTL=61

Ping statistics for 68.87.203.217:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 19ms, Average = 11ms

ping 162.151.40.61

Pinging 162.151.40.61 with 32 bytes of data:
Reply from 162.151.40.61: bytes=32 time=19ms TTL=60

Ping statistics for 162.151.40.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms

ping 162.151.40.61 -n 20

Pinging 162.151.40.61 with 32 bytes of data:
Reply from 162.151.40.61: bytes=32 time=19ms TTL=60

Ping statistics for 162.151.40.61:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 28ms, Average = 19ms

ping 4.68.71.25 -n 20

Pinging 4.68.71.25 with 32 bytes of data:
Reply from 4.68.71.25: bytes=32 time=23ms TTL=59

Ping statistics for 4.68.71.25:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 33ms, Average = 24ms

ping 4.69.153.86 -n 20

Pinging 4.69.153.86 with 32 bytes of data:
Reply from 4.69.153.86: bytes=32 time=93ms TTL=243
Reply from 4.69.153.86: bytes=32 time=114ms TTL=243
Reply from 4.69.153.86: bytes=32 time=138ms TTL=243
Reply from 4.69.153.86: bytes=32 time=208ms TTL=243
Reply from 4.69.153.86: bytes=32 time=101ms TTL=243
Reply from 4.69.153.86: bytes=32 time=158ms TTL=243
Reply from 4.69.153.86: bytes=32 time=98ms TTL=243

Ping statistics for 4.69.153.86:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 208ms, Average = 108ms

ping 4.59.178.74 -n 20

Pinging 4.59.178.74 with 32 bytes of data:
Reply from 4.59.178.74: bytes=32 time=98ms TTL=243

Ping statistics for 4.59.178.74:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 98ms, Average = 94ms

ping 192.34.76.10 -n 20

Pinging 192.34.76.10 with 32 bytes of data:
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49
General failure.
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49
Request timed out.
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49

Ping statistics for 192.34.76.10:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 149ms, Average = 120ms

ping 199.91.189.242 -n 20

Pinging 199.91.189.242 with 32 bytes of data:
Reply from 199.91.189.242: bytes=32 time=120ms TTL=239
Request timed out.
Reply from 199.91.189.242: bytes=32 time=118ms TTL=239
Request timed out.

Ping statistics for 199.91.189.242:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 120ms, Average = 117ms

ping 199.91.189.23 -n 20

Pinging 199.91.189.23 with 32 bytes of data:
Reply from 199.91.189.23: bytes=32 time=124ms TTL=47
Request timed out.
Reply from 199.91.189.23: bytes=32 time=118ms TTL=47

Ping statistics for 199.91.189.23:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 133ms, Average = 119ms

Seems like it's either a problem at the last hop from L3 or in the datacenter itself, never lagged prior to Heavensward

[Daeney]

Name of your Internet Service Provider (ISP)

Comcast

Ticket or reference number from your ISP.

none

State/Country

Indiana/USA

Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.)

Evenings around 7pm EST

Frequency (How often does the issue occur?)

Most every evening for the last month or so

Content (Which content were you playing in-game when the issue occurred?)

World content (fates) and Instanced content (dungeons)

Which in-game World were you playing on when the issue occurred?

Gilgamesh

Traceroute records (optional) (Learn how to generate traceroute record)

Will add tonight

[Amesiel]

Lag every night around 7:00 PM EST till about 10:00PM EST. Makes the game completely unplayable.

• ISP: Comcast.
• Ticket #: None, they wont give me one.
• State: PA.
• Date/Time: The connection issues have been happening for a while now and it seems like nothing is being done, if anything it's even worse now. I replied to this thread in December of last year, the issues are still around.
• Frequency: Every nights around 7PM lasting for 3 or more hours. (it has been almost 2 months now and no update on the matter)
• Content: All Content. The game just craps out.

In-Game World: Famfrit.

[Downdrop]

ISP: Comcast Business
Speed: 50 down, 20 up
Server: Diabolos
The lags begin daily @ 7pm eastern standard, lasting until approximately 10:30pm everyday

Traceroute done on 1/28/16 @ 10pm EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    <1 ms    <1 ms    <1 ms  10.1.10.1
  3     8 ms     8 ms     7 ms  96.120.36.173
  4     7 ms     8 ms     8 ms  xe-11-2-2-sur01.gardens.fl.pompano.comcast.net [68.85.83.241]
  5    10 ms    20 ms    10 ms  xe-4-1-3-0-ar02.stuart.fl.pompano.comcast.net [162.151.42.173]
  6    14 ms    13 ms    14 ms  hu-0-9-0-1-ar01.northdade.fl.pompano.comcast.net [69.139.182.37]
  7    25 ms    14 ms    13 ms  ae13.edge2.Miami1.Level3.net [4.68.62.149]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    49 ms    50 ms    50 ms  ae-101-101.ebr1.Washington12.Level3.net [4.69.204.229]
 13    50 ms    49 ms    49 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   131 ms   213 ms   215 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 17    50 ms    50 ms    58 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

 18    50 ms    50 ms    59 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 19    72 ms    71 ms     *     192.34.76.10
 20    72 ms    72 ms    72 ms  199.91.189.242
 21    73 ms    72 ms    72 ms  199.91.189.39

Trace complete.

Traceroute done on 1/29/16 @ 10pm EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    <1 ms    <1 ms    <1 ms  10.1.10.1
  3     9 ms     9 ms     7 ms  96.120.36.173
  4     7 ms     7 ms     7 ms  xe-11-2-2-sur01.gardens.fl.pompano.comcast.net [68.85.83.241]
  5     8 ms     9 ms    11 ms  xe-4-1-3-0-ar02.stuart.fl.pompano.comcast.net [162.151.42.173]
  6    13 ms    13 ms    12 ms  hu-0-9-0-1-ar01.northdade.fl.pompano.comcast.net [69.139.182.37]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    51 ms    51 ms    50 ms  ae-101-101.ebr1.Washington12.Level3.net [4.69.204.229]
 13    51 ms    51 ms    50 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   116 ms    86 ms   129 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 17    49 ms    49 ms    68 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
 18    50 ms    61 ms    50 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 19    72 ms    72 ms    72 ms  192.34.76.10
 20    72 ms    72 ms    72 ms  199.91.189.242
 21    72 ms    71 ms     *     199.91.189.39
 22    71 ms    72 ms    71 ms  199.91.189.39

Trace complete.

Ping done on 1/29/16 at approximately 10:06pm EST

Pinging 199.91.189.39 with 32 bytes of data:
Request timed out.
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Request timed out.
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239

Ping statistics for 199.91.189.39:
    Packets: Sent = 5, Received = 3, Lost = 2 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 72ms, Maximum = 72ms, Average = 72ms

Has been an ongoing problem for a very long time now. Fed up, going to quit.

[Iluvwrenches]

Name of your Internet Service Provider: Rogers Cable
Ticket or reference number from your ISP: None
State/Country: Ontario, Canada
Date/Time: Since day 1 for me, which is about a week ago.
Frequency: Every hour of every day... theres never NOT a time I don't have lag issues.
Content: Its irrelevant what I am doing. I could be questing in West Thanalan or doing a dungeon like Halatii and it will still happen.
Which in-game World were you playing on when the issue occurred: Adamantoise

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms 1 ms 1 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
2 8 ms 15 ms 9 ms 7.11.162.193
3 26 ms 11 ms 12 ms 69.63.242.73
4 130 ms 716 ms * 24.156.157.81
5 28 ms 29 ms 27 ms van58-9-230-26.dynamic.rogerstelecom.net [209.14
8.230.26]
6 930 ms 1637 ms 1331 ms be812.ccr41.iad02.atlas.cogentco.com [154.54.11.
217]
7 290 ms 38 ms 30 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
8 36 ms 35 ms 37 ms be2806.ccr41.jfk02.atlas.cogentco.com [154.54.40
.105]
9 39 ms 39 ms 39 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.
50]
10 44 ms 43 ms 43 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43
.17]
11 52 ms 51 ms 49 ms 38.122.42.34
12 231 ms 203 ms 50 ms 192.34.76.10
13 545 ms 42 ms 43 ms 199.91.189.242
14 43 ms 43 ms 52 ms 199.91.189.74

Trace complete.

Here is a Ping test:

Pinging 199.91.189.74 with 32 bytes of data:
Reply from 199.91.189.74: bytes=32 time=44ms TTL=49
Reply from 199.91.189.74: bytes=32 time=44ms TTL=49
Reply from 199.91.189.74: bytes=32 time=648ms TTL=49
Reply from 199.91.189.74: bytes=32 time=1379ms TTL=49

Ping statistics for 199.91.189.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 1379ms, Average = 528ms

There is a very clear issue with one of the results from my trace... and no, it isn't my ISP. WoW, Gw2, Gw1, CS:GO and a plethora of other games I have 0 connectivity issues with. I paid $25 on steam for this and I'm currently playing with the included game time. If I can't play without lag, I definitely will not be subscribing.

[Mimilu]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: N/A. They said there was nothing they could do on their end...I don't think the person who helped me even new what I was talking about...
State/Country: Michigan, USA
Date/Time: 1/1/2016
Frequency (How often does the issue occur?): Everyday, almost all the time, just random lag spikes and rubberbanding. Especially when I am in a Dungeon or Trial. Happens way more often from 3pm-10pm EST and it's really effect how frequently I play the game.
Content : EVERYTHING (Dungeons, Trials, Open-World, crafting, even just running in a city or empty map)
Which in-game World were you playing on when the issue occurred?: Exodus -Primal
Traceroute records (optional) (Learn how to generate traceroute record): N/A

[Downdrop]

Another day of horrendous lag.

Tracing route to 199.91.189.39 over a maximum of 30 hops

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2    <1 ms     1 ms     1 ms  10.1.10.1
  3     7 ms     7 ms     7 ms  96.120.36.173
  4     8 ms     7 ms     8 ms  xe-11-2-2-sur01.gardens.fl.pompano.comcast.net [68.85.83.241]
  5     8 ms     9 ms     8 ms  xe-4-1-3-0-ar02.stuart.fl.pompano.comcast.net [162.151.42.173]
  6    13 ms    13 ms    13 ms  hu-0-9-0-1-ar01.northdade.fl.pompano.comcast.net [69.139.182.37]
  7     *       13 ms    14 ms  ae13.edge2.Miami1.Level3.net [4.68.62.149]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    52 ms    49 ms    49 ms  ae-101-101.ebr1.Washington12.Level3.net [4.69.204.229]
 13    52 ms    61 ms    54 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16    50 ms    49 ms    49 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 17    59 ms    49 ms    49 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

 18    49 ms    50 ms    49 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 19    97 ms    72 ms    72 ms  192.34.76.10
 20     *       72 ms     *     199.91.189.242
 21    73 ms    72 ms    72 ms  199.91.189.39

Trace complete.

Pinging 199.91.189.39 with 32 bytes of data:
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Request timed out.
Request timed out.

Ping statistics for 199.91.189.39:
    Packets: Sent = 5, Received = 3, Lost = 2 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 72ms, Maximum = 72ms, Average = 72ms

40% packet loss is completely unacceptable. This game is unplayable. Comcast customers are better off playing literally any other video game available.

EDIT: Ping and traceroutes performed on 01/31/16 @ approx. 7:56pm EST

[jnovah]

How many pages do you need before we can get an update on this being resolved?

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: They claim nothing is wrong.
State/Country: Oregon, USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): It started happening on 11/23/15. Lately it is more and more often. I experience massive packet loss and high ping consistently from 4:00 PM PST until around 11:30 PM PST, although it does pop up sporadically during the day.
Frequency (How often does the issue occur?): Every day without fail
Content (Which content were you playing in-game when the issue occurred?): Doesn't matter, I could just be standing around and experience it.
Which in-game World were you playing on when the issue occurred? Ultros
Traceroute records: n/a