Reporting Latency Related Issue (NA Data Center)

[synnap]

Name of your Internet Service Provider (ISP)
Time Warner Cable (TWC)

Ticket or reference number from your ISP.
They refuse to open a ticket; says the problem isn't on their end.

State/Country
Kentucky, USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.)
Started around 1/11/16. Happens throughout the day, in normal world and dungeons.

Frequency (How often does the issue occur?)
Once every 5-10 minutes.

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

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

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


I am not paying for a VPN service to bypass the Montreal Level3 server that's having SO MANY issues. That's simply not an option. Please investigate and contact Level3 and have them investigate it.

[Downdrop]

A new day, and with it, brings new daily 7pm lags. Not sure how many pings, traceroutes, and complaints I can make. This problem is certainly not my fault and it's not going away.

Traceroute performed on 02/01/16 at 7:00pm

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    16 ms     7 ms     8 ms  96.120.36.173
  4     9 ms     7 ms     8 ms  xe-11-2-2-sur01.gardens.fl.pompano.comcast.net [68.85.83.241]
  5    10 ms     9 ms    10 ms  xe-4-1-3-0-ar02.stuart.fl.pompano.comcast.net [162.151.42.173]
  6    15 ms    13 ms    13 ms  hu-0-9-0-1-ar01.northdade.fl.pompano.comcast.net [69.139.182.37]
  7     *       13 ms    23 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    50 ms    49 ms    50 ms  ae-101-101.ebr1.Washington12.Level3.net [4.69.204.229]
 13    55 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    49 ms    51 ms    49 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
 17    49 ms    50 ms    49 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

 18    50 ms    50 ms    49 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 19    72 ms    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.

Ping performed on 02/01/16 at approx 7:06pm

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

Ping statistics for 199.91.189.39:
    Packets: Sent = 5, Received = 4, Lost = 1 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 71ms, Maximum = 83ms, Average = 74ms

The next thing I'm going to start wondering is who I need to contact for refunds.

EDIT: Time is in eastern standard.

[Adegx]

Name of your Internet Service Provider (ISP) Comcast
Ticket or reference number from your ISP.
State/Country MS/USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) 6 pm CST - 8 cst
Frequency (How often does the issue occur?) Nightly
Content (Which content were you playing in-game when the issue occurred?) All
Which in-game World were you playing on when the issue occurred? Admantoise



5 19 ms 24 ms 25 ms te-0-4-0-4-ar02.winchester.tn.malt.comcast.net [162.151.82.165]
6 24 ms 23 ms 22 ms te-0-3-0-1-ar02.dannythomas.tn.malt.comcast.net [162.151.82.17]
7 37 ms 38 ms 38 ms be-22258-cr02.dallas.tx.ibone.comcast.net [68.86.93.93]
8 * * * Request timed out.
9 197 ms 213 ms 220 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
10 226 ms 217 ms 235 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
11 60 ms 72 ms 62 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 79 ms 79 ms 85 ms 192.34.76.10
13 86 ms 79 ms 79 ms 199.91.189.242
14 82 ms 80 ms * 199.91.189.30
15 * 78 ms 83 ms 199.91.189.30

[Desire]

And again another day of lagging started at exactly 6pm cst.....prob wont stop till 11pm as always....

And another question why are we hopping twice at the level 3 hub in Montreal both with the same IP?

ISP= Comcast...see previous post for all other data..

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 31 ms 9 ms 96.120.24.209
3 15 ms 12 ms 10 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 12 ms 42 ms 18 ms 10g-8-2-sr01.elkhart.in.sbend.comcast.net [68.87.235.137]
5 * * * Request timed out.
6 205 ms 213 ms 237 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 103 ms 222 ms 202 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 33 ms 33 ms 39 ms 4.59.178.62
9 59 ms 48 ms 46 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 47 ms 41 ms 39 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 49 ms 54 ms 41 ms 174.142.115.218
12 46 ms 40 ms 40 ms 184.107.107.176

Trace complete.

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 10 ms 45 ms 10 ms 96.120.24.209
3 19 ms 10 ms 8 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 17 ms 16 ms 14 ms te-2-7-0-4-ar01.area4.il.chicago.comcast.net [68.87.230.41]
5 * * * Request timed out.
6 209 ms 241 ms 234 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 110 ms 49 ms 135 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 34 ms 35 ms 34 ms 4.59.178.62
9 63 ms 47 ms 46 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 40 ms 41 ms 57 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 60 ms 65 ms 44 ms 174.142.115.218
12 44 ms 43 ms 45 ms 184.107.107.176

Trace complete.