Repeat disconnects -NOT my ISP.

[Kreylyn]

So for the last 4 days I've had random, multiple, sporadic, and repetitive disconnects. It's frustrating to say the least. Today I've not even been able to fully finish a single fight because of them.

I know it's NOT my ISP or my systems.

It's been happening at different locations, on different systems, on different installs, on multiple characters. (I play at work and home).

Work is a dedicated high speed guaranteed always up service.

Today I got to repetitively running the tracerts to track it down... managed to catch it right at a disconnect.

Log is below... Bold is the disconnect tracert as it was happening.

Just typing this up has been 2 more disconnects today.

HELP!

Microsoft Windows [Version 6.1.7601]Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 5 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 7 ms 7 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 4 ms 9 ms 5 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 13 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 12 ms 11 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 9 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 25 ms 24 ms 25 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 32 ms 32 ms 31 ms xe-2-0-2.nyc39.ip4.gtt.net [141.136.111.106]
13 31 ms 31 ms 31 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 39 ms 32 ms 41 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 33 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 33 ms * 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 9 ms 1 ms <1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 9 ms 9 ms 9 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 4 ms 9 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 10 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 10 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 11 ms 12 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 24 ms 25 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 31 ms 31 ms xe-2-0-2.nyc39.ip4.gtt.net [141.136.111.106]
13 32 ms 31 ms 31 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 35 ms 36 ms 32 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 33 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 32 ms 33 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 33 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 35 ms 31 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 3 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms <1 ms 3 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 4 ms 4 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 5 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 10 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 10 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 11 ms 12 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 9 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 25 ms 25 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 35 ms 32 ms xe-2-0-2.nyc39.ip4.gtt.net [141.136.111.106]
13 30 ms 31 ms 31 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 33 ms 32 ms 32 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 32 ms * 33 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 * 32 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 31 ms 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 35 ms 35 ms 32 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms <1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 3 ms 7 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 6 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 11 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 13 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 51 ms 32 ms 30 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 39 ms 31 ms 31 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 30 ms 30 ms 30 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 35 ms 32 ms 41 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 32 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 32 ms * 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 35 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms <1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 <1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 7 ms 4 ms 9 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 5 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 13 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 10 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 13 ms 11 ms 12 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 59 ms 9 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 25 ms 48 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 31 ms 32 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 30 ms 31 ms 30 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 32 ms 32 ms 32 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 32 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 32 ms * * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 32 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 2 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 4 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 9 ms 7 ms 9 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 7 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 10 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 10 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 14 ms 12 ms 10 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 11 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 26 ms 25 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 32 ms * 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 35 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 32 ms 32 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 3 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 5 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 10 ms 7 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 7 ms 7 ms 8 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 16 ms 16 ms 13 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 11 ms 12 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 11 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 27 ms 32 ms 25 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 32 ms 31 ms 31 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 30 ms 30 ms 30 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 39 ms 32 ms 41 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 33 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 32 ms 35 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 32 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert 108.61.129.170

Tracing route to 170.rogean.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 2 ms <1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 4 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 3 ms 7 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 8 ms 10 ms 9 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 10 ms 18 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 10 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 12 ms 11 ms 12 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 34 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 31 ms 32 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 30 ms 32 ms 32 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 40 ms 32 ms 41 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * * 33 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 * 32 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 31 ms 33 ms 31 ms 170.rogean.com [108.61.129.170]

Trace complete.

__________________________________________________ _

Krey

[Kreylyn]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms <1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 12 ms 6 ms 5 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 6 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 9 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 12 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 25 ms 25 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 31 ms 31 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 32 ms 30 ms 37 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 37 ms 32 ms 40 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 32 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 32 ms * * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 35 ms 32 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 <1 ms <1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 13 ms 8 ms 3 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 6 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 12 ms 15 ms 20 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 * 10 ms 11 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 46 ms 25 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 31 ms 35 ms 32 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 30 ms 30 ms 31 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 32 ms 43 ms 32 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 33 ms 33 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 * 32 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 33 ms 31 ms 33 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 35 ms 35 ms 31 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 3 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 4 ms 4 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 4 ms 8 ms 9 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 8 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 14 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 10 ms 12 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 9 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 25 ms 25 ms 25 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 32 ms 33 ms 31 ms xe-4-1-3.nyc39.ip4.gtt.net [141.136.108.153]
13 31 ms 33 ms 31 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 32 ms 32 ms 37 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 * 33 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 38 ms 32 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 31 ms 33 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms <1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 5 ms 4 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 10 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 10 ms 14 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 10 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 10 ms 17 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 9 ms 9 ms 9 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 51 ms 25 ms 28 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * 33 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 33 ms 35 ms 32 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>


_________________________________________

Boots me to char select after 5-10 sec delay most times. Once in a while it drops all the way back to log in screen.

20+ disconnects so far in 6 hours of attempted play.

Krey

[Solon]

Happeneing to me too -- its super annoying

[Solon]

This is happening to me too. I can't play becasue of it. Someone please help! I'm going crazzy.. Need my EQ fix =(

[Solon]

having same issues

[Camdenbrown]

I want to punch my monitor this has been happening so much!

[Veltira]

Agreed on all aspects, the game ran great my first few weeks here but now I get disconnected quite frequently (and sent to the login screen after a time). I play with three other fellows and we voice chat nightly, only one other is having the same issue and we both live in Tennessee. I mention this because every person in this thread is from Tennessee or North Carolina it looks like by the locations under your names. Is this a regional issue perhaps because its confined to these two states and it started for us all at the same time some 4 or 5 days ago? Can anyone else from this area confirm they are having the same issues?

[mintmaster]

This is most likely the same problem that was happening back in early December. There were a number of posts just like this including mine of random Link Deaths of players who use Charter Cable and Time Warner Cable in NC, SC, GA, TN, AL, and FL(I am in Alabama). It was very frustrating and was only affecting EQ not websurfing etc.

Someone with a lot more expertise than me posted at that time that in those States Charter cable often pauses for 10 to 20 seconds at a time. With newer programs this just causes a slightly noticeable lag or a page which stalls out and has to be reloaded. But older programs like classic EQ boot you out when they detect that the ISP has paused for more than 10 or 15 sec.

The problem appeared to have cleared up for me back in mid December but has come back with a vengeance about 10 days ago. First an LD about every 2 hours, but the past 2 days I have been going LD about every 10 minutes. I have contacted Charter twice and they say my cable is working fine and it must be my router or modem. But I explain to them that my daughter is online on Charter as well on the same EQ program and goes LD at the exact same time....and she lives 5 miles away. I also have a new router since Christmas and the LDs were happening on both the old and new router.

I have had Charter for over 15 years and it is typical that they will never take responsibility for problems. I am not a tech person and what I have noted above is just a rehash of what was posted here in December. I hope and wish that someone has more pull with Charter than I do because unless they take responsibility and make some changes to their antiquated equipment P99 has become unplayable for me. In fact I am really getting tired of the pauses in Charter service on other programs and repeatedly having to reload webpages. The only alternative I have is a dedicated Hotspot I purchased back in the summer which I may have to start using and just cancel Charter service.

Any other feedback would be VERY appreciated because i am absolutely frustrated at this point

[Kreylyn]

Perhaps someone more knowledgeable than me can explain if it IS charter's issue, why the only delays/timeouts for the trace routes I do come back for GTT.net and mostly NYC area nodes.

In the last 5 mins .... (personal IP addy removed jus cause...)

3 9 ms 8 ms 8 ms dtr01wvvlnc-tge-0-0-1-2.wvvl.nc.charter.com [96.
34.67.105]
4 10 ms 8 ms 8 ms crr01ahvlnc-bue-21.ahvl.nc.charter.com [96.34.92
.52]
5 13 ms 14 ms 17 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
6 13 ms 20 ms 13 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
7 20 ms 22 ms 15 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
8 19 ms 22 ms 22 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
9 19 ms 20 ms 18 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
10 19 ms 23 ms 20 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
11 22 ms 20 ms 17 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
12 25 ms 28 ms 26 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
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 * 44 ms 46 ms 170.rogean.com [108.61.129.170]

Trace complete.

Krey

[Forza]

devs, i appreciate your work you do in these servers, but please for the love of god look into this. it's been a persistent problem for SO long now and it's worse than ever.

[Forza]

I must have died 100 times because of disconnects in the past week and it's a joke ... Will i get a gm rez? Nah. Is this "classic", or intended? Nah. I know, i'm just some nerd that is crying over elf simulator, but jesus man it's not only me and it's driving me up the wall when i decide to sit down and play this game. Damnit.

[Shatford]

I live in Canada with a totally different ISP and I am suffering from the exact same problem you're all describing.

I go LD every 2 hours on the nose. It is not my ISP, my modem, or my computer.

I am no computer expert, but I think it has to do with dynamically-assigned IP addresses. If you run MSCONFIG on windows XP run dialogue, then go to the TOOLS tab, and launch IPCONFIG (make sure you enable Advanced Options check box), I see when my IP lease was obtained. For example we'll say it January 31st, 2015 at 6:04pm EST. Now, if I log onto EQ and play, I go LD at exactly 8:04pm EST.

I figure my IP renews its lease every 2.0 hours, and EQ reads this as an interrupt and LDs me. It's handy to know that every 2.0 hours I will disconnect, so I make sure I'm not in combat while soloing. However, I have not changed anything to my set up in a long time, so this is not a client-side issue.

So obviously something has changed server-side to the EQ game server. Again, I am by no means a computer guy, but perhaps there's a way to loosen up the server's parameter's for what constitutes a disconnect?

[Veltira]

It has been worse than usual tonight, completely unplayable as I disconnect constantly. Let's get some ideas going on what could be causing this.

[Sirviver]

This is most likely the same problem that was happening back in early December. There were a number of posts just like this including mine of random Link Deaths of players who use Charter Cable and Time Warner Cable in NC, SC, GA, TN, AL, and FL(I am in Alabama). It was very frustrating and was only affecting EQ not websurfing etc.

Someone with a lot more expertise than me posted at that time that in those States Charter cable often pauses for 10 to 20 seconds at a time. With newer programs this just causes a slightly noticeable lag or a page which stalls out and has to be reloaded. But older programs like classic EQ boot you out when they detect that the ISP has paused for more than 10 or 15 sec.

The problem appeared to have cleared up for me back in mid December but has come back with a vengeance about 10 days ago. First an LD about every 2 hours, but the past 2 days I have been going LD about every 10 minutes. I have contacted Charter twice and they say my cable is working fine and it must be my router or modem. But I explain to them that my daughter is online on Charter as well on the same EQ program and goes LD at the exact same time....and she lives 5 miles away. I also have a new router since Christmas and the LDs were happening on both the old and new router.

I have had Charter for over 15 years and it is typical that they will never take responsibility for problems. I am not a tech person and what I have noted above is just a rehash of what was posted here in December. I hope and wish that someone has more pull with Charter than I do because unless they take responsibility and make some changes to their antiquated equipment P99 has become unplayable for me. In fact I am really getting tired of the pauses in Charter service on other programs and repeatedly having to reload webpages. The only alternative I have is a dedicated Hotspot I purchased back in the summer which I may have to start using and just cancel Charter service.

Any other feedback would be VERY appreciated because i am absolutely frustrated at this point
I am in this same boat.

AND it affects my ability to browse www.project1999.com at the same time during the DC.

[Kreylyn]

I am in this same boat.

AND it affects my ability to browse www.project1999.com at the same time during the DC.

project1999.com URL and the game are on the same server IP according to my trace routes.

Refreshing P99 website and getting a connection error has actually started to clue me in that I was going to be crashing in the game shortly after too.

Logged in this morning, less than 4 mins in... Had just put up my 2nd auction in EC tunnel when LD... /sigh....


Krey

[Solon]

I have died countless times to this stupid issue. Is there anyone looking into this or should I just give up my on my EverQuest dreams?

[gnotshr]

I am having the same issues.

[magisterco]

Someone mentioned in another thread related to this to try using a VPN.

Today i have been dcing roughly every 8 to 15 mins.

Set up a VPN, so far not a blip for 1hr 32mins.

I know its not long enough to consider it being a fix (1.5 hours is not that long), but its the longest ive been online without a dc this week.

[Thulack]

Someone mentioned in another thread related to this to try using a VPN.

Today i have been dcing roughly every 8 to 15 mins.

Set up a VPN, so far not a blip for 1hr 32mins.

I know its not long enough to consider it being a fix (1.5 hours is not that long), but its the longest ive been online without a dc this week.

Its probably because the VPN is routing better then your ISP is therefore again proving that its a IP issue and not a p99 issue.

[magisterco]

Its probably because the VPN is routing better then your ISP is therefore again proving that its a IP issue and not a p99 issue.

I am not trying to blame here, just trying to help get a fix.

[magisterco]

Someone mentioned in another thread related to this to try using a VPN.

Today i have been dcing roughly every 8 to 15 mins.

Set up a VPN, so far not a blip for 1hr 32mins.

I know its not long enough to consider it being a fix (1.5 hours is not that long), but its the longest ive been online without a dc this week.

Just Dc'd again, going to try rerouting

[Veltira]

Its probably because the VPN is routing better then your ISP is therefore again proving that its a IP issue and not a p99 issue.

I would agree with you if it weren't for the fact that when these disconnects happen its SPECIFICALLY P99 servers, website, etc. We don't lose connection to the internet, our connection to the server is disrupted. You are basically just telling us to deal with it and trust that the ISP will magically fix our problem. They won't, it's up to us to solve this issue. If it were you that could not stay connected this would be a much bigger issue, right?

Now that all the finger pointing for fault is done can we maybe brainstorm other ideas on why this is happening or better yet ideas on how to fix it please? There seems to be a post like this every few months where a select group of players for a region get disconnects. If it is indeed the ISP what are some things we could do to get around this problem? Is the VPN idea still holding up?

[gnotshr]

After going LD about every five minutes this morning, I decided to try a google search for a Free VPN; I downloaded and installed one. I played for over an hour with out any disconnects before I logged off. It seems to be an effective work around.

With that said, most of the Free VPNs I found limit the amount of data usage before you have to pay.

[TreegreatesT]

are you guys just getting a client lockup? ive been having the issue where EQ just freezes and becomes unresponsive the only thing i can do is X out of the window.

[Thulack]

I would agree with you if it weren't for the fact that when these disconnects happen its SPECIFICALLY P99 servers, website, etc. We don't lose connection to the internet, our connection to the server is disrupted. You are basically just telling us to deal with it and trust that the ISP will magically fix our problem. They won't, it's up to us to solve this issue. If it were you that could not stay connected this would be a much bigger issue, right?

Now that all the finger pointing for fault is done can we maybe brainstorm other ideas on why this is happening or better yet ideas on how to fix it please? There seems to be a post like this every few months where a select group of players for a region get disconnects. If it is indeed the ISP what are some things we could do to get around this problem? Is the VPN idea still holding up?

Correct it happens only to p99 it could be a routing issues on your ISP end connecting to p99. It doesnt necessarily mean its on p99's end.

[Veltira]

Correct it happens only to p99 it could be a routing issues on your ISP end connecting to p99. It doesnt necessarily mean its on p99's end.

Did you just come here to say this over and over? We've moved on to ways to correct the issue and you still want to argue about who's fault it is. We don't care who's fault it is, we are not and were never blaming P99; we just want to find a way to play like the rest of you.

Meanwhile the VPN answer is working, I've personally tried it and can confirm that i got no dosconnects for the first hour, then i had to go to work. If there's interest I can put together a small guide (or find one relevant) explaining the steps necessary to work around this issue until it either resolves itself or we find a better solution. Thanks to Gnotshr for confirming the VPN workaround.

[magisterco]

I can only 1 of my three my posts.. TESTING..

[Kreylyn]

So just to verify that something more than just complaining is being done... I attempted to contact charter to get their assistance in resolving the issues.

After doing the "troubleshooting" steps for connectivity (even though I was explicit about the issue) I got disconnected 3 times before getting back to the chat person.

Ended up with the same guy.

Our conversation after I explained it was still not resolved was pretty much this...

__________________________________________________ _____________

Charter Customer Representative [Alfrederick]: Please give me a minute or two to run further tests.

You: the issue occurs at another location on a different account with a different computer with a direct connection to the charter provided router too.

Charter Customer Representative [Alfrederick]: Thank you for patiently waiting.

Charter Customer Representative [Alfrederick]: Mr. *****, I did check your connection once more after you powercycle it and I can't still check any issues with it. I understand that you can access it without issues using a non-Charter connection and the issue persists on other Charter network as well. The said information brings me the possibility that the said site might be the one having issues with Charter connections. The reason why this case is possible is because Charter doesn't block ports/routes on any websites.

Charter Customer Representative [Alfrederick]: Like you mentioned, the issue persists on Charter connections. That's why I suggest that you try to contact the site administrator to see if they are having issues with Charter network connection to see if they can check and fix the issue on their end instead.

You: Does charter not specify the nodes that are used in making a connection to any IP address?

Charter Customer Representative [Alfrederick]: Charter doesn't block ports or nodes in making a connection to any IP addresses.

Charter Customer Representative [Alfrederick]: That's why it would be best if you will give the site adminitrator of the said website a call so you can bring this issue to their attention.

Charter Customer Representative [Alfrederick]: There might be an issue with the site communicating using Charter connections that could cause the issue and they can certainly check that for you.

You: but YOUR the isp that is having the issue in routing... I can use any other ISP and not have this issue.

You: Is there not an advanced tech support agent who has the ability to monitor a trace route to verify the nodes your system is choosing is working correctly?

Charter Customer Representative [Alfrederick]: I understand that. Since Charter, the ISP that you are using, is not blocking any ports or nodes, you need to check with the site administrator if they are having issues or if they are blocking Charter connections since only Charter connections are experiencing this issue. If there is an issue with Charter connection, multiple sites will be affected. Since it is only one particular site and Charter doesn't block or open ports or nodes, it would be best to give the site administrator a call so we can check both ends of the issue.

Charter Customer Representative [Alfrederick]: I regret to inform you as well that we don't have a Tier 2 support, a higher technicial support agent, that can check the nodes since Charter doesn't block or open ports or nodes.

You: The site admin has stated they are not aware of any issues on their end.

You: I keep getting pointed back to charter... since it's only charter that has the issue

You: specifically the node route charter forces me to use to connect to the specific IP address. Bypassing your forced route by using a VPN resolved the issue.

You: Tracing route to 170.rogean.com [108.61.129.170] *deleted the long line of text, it's already posted here.) is an example of the traceroute from another location near by.

Charter Customer Representative [Alfrederick]: Mr. *****, I perfectly understand what you have done to bypass the issue.

Charter Customer Representative [Alfrederick]: Here's what we can do. We can send a ticket instead so we can check the said issue that you are having on one website only.

Charter Customer Representative [Alfrederick]: This will take within 24 to 48 hours to get results.

Charter Customer Representative [Alfrederick]: It would be best to check with the site administrators again within the said time frame so they can be aware that Charter doesn't block or open any ports or nodes on our connection.

You: Yes, I would like for Charter to contact GTT.net to verify why charter is having issues with information on their network.

Charter Customer Representative [Alfrederick]: I regret to inform you that we won't contact them. What we will check is our connection.

Charter Customer Representative [Alfrederick]: It would be best that you contact them once more while we are checking our connection and let them know that we don't block or open nodes for a specific IP address so they can check if there is an issue with the nodes that you are using with Charter connection to connect to their site.

Charter Customer Representative [Alfrederick]: Okay, Mr. ******. If that is the case, we will still check our connection within 24 to 48 hours.

You: to verify, you will check that the connection is constant with no short term interuptions over a period of time?

Charter Customer Representative [Alfrederick]: What we will do is to send a ticket to check everything on our end to make sure that there is no issue with our Internet connection.

Charter Customer Representative [Alfrederick]: You can also visit www.charter.com/customers/supportgeneral.aspx or www.charter.com/faqs for general information and Frequently Asked Questions about Charter services.

Charter Customer Representative [Alfrederick]: As a recap, I was able to assist you with your project1999.com issue by checking your connection. As a reminder, we will send notifications regarding your Charter account to ******@charter.net. Is there anything else that I can assist you with?

__________________________________________________ _____

And a disconnect again as I was typing this... /sigh

So to verify... can a site admin at least chime in that this IS being looked at on the hosting side?

Krey

[Veltira]

Great job Kreylyn! Hopefully this will help our cause!

[Kiithsa]

I have had success with CyberGhost 5 VPN software for the past 1.5hours. Have to goto bed will do further testing tomorrow after work but seems to be working.

[Sirviver]

Outstanding work, Krey. Thank you, for all of us.

Don't forget the unusual nature of this thing - we don't stop receiving, only sending, which apparently manifests as a DDoS-like DC, and after about 15, seconds, forced a boot.

[Sirviver]

Also, I wonder if the rest of EQEmu is being affected.

[Sirviver]

I have had success with CyberGhost 5 VPN software for the past 1.5hours. Have to goto bed will do further testing tomorrow after work but seems to be working.
I am going to give CyberGhost a try also, but I am unsure of how to set it up. Can you lend a hand?

[Kiithsa]

It was easy to set-up, just install and press the connect button. Done.

[Kreylyn]

Also, I wonder if the rest of EQEmu is being affected.

I logged into "The Hidden Forest"... no issues even though P99 disconnected me 3 times while both instances were running.

I believe the individual servers are hosted by the owners, and EQEMU is just a central connecting point.

I'll see if I can find other IPs of some sort that share the same hosting company as P99, and see what I get at the time of disconnects with a tracert.

Krey

[Veltira]

Cyberghost worked to eliminate the issue, although being on a VPN is a bit if a hassle its much better than the disconnects. I hope others find this helpful.

[Kreylyn]

Issue appears to be getting worse.

Disconnects are more frequent and lasting for longer durations.

__________________________________________________ _________________

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 4 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 8 ms 7 ms 10 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 7 ms 8 ms 13 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 21 ms 14 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 9 ms 9 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 25 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 34 ms 35 ms 35 ms xe-3-0-3.nyc39.ip4.gtt.net [141.136.108.145]
13 30 ms 30 ms 30 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 32 ms 32 ms 36 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 32 ms * 32 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 * 32 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 31 ms 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 31 ms 32 ms 35 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms 1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 4 ms 3 ms 5 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 8 ms 7 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 12 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 10 ms 9 ms 10 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 9 ms 9 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 8 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 24 ms 53 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
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.

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms 1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 1 ms 1 ms <1 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 3 ms 3 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 6 ms 15 ms 17 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 6 ms 7 ms 8 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 15 ms 11 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 9 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 12 ms 10 ms 9 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 12 ms 8 ms 8 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 24 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 31 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-159-134-161.static.snfr.nc.charter.com [24.15
9.134.161]
2 1 ms <1 ms 1 ms dtr01ahvlnc-tge-0-7-0-5.ahvl.nc.charter.com [96.
34.65.246]
3 10 ms 6 ms 8 ms crr01ahvlnc-bue-20.ahvl.nc.charter.com [96.34.93
.250]
4 3 ms 5 ms 11 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
5 7 ms 4 ms 7 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
6 9 ms 6 ms 7 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
7 15 ms 15 ms 15 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
8 9 ms 10 ms 9 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
9 10 ms 10 ms 10 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
10 9 ms 8 ms 9 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
11 24 ms 25 ms 24 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
12 34 ms 34 ms 34 ms xe-3-0-3.nyc39.ip4.gtt.net [141.136.108.145]
13 30 ms 33 ms 30 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
14 37 ms 32 ms 46 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
15 32 ms * 32 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 * * 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 32 ms 32 ms 32 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 32 ms 35 ms 32 ms 170.rogean.com [108.61.129.170]

Trace complete.

C:\Users\Management>

__________________________________________________ _______________

This was over a period of about 3 mins starting around aprox 10:45am est.

Krey

[Shatford]

I am using an ISP called Distributel in Canada. I am getting the same issues you are all getting. It is not specific to a single ISP.

[CreamyCowboy]

I haven't played for a few weeks but I just created a character last night on red and I have been getting disconnected like crazy.

I see chat still, pet killing etc but I can't consider targets, or cast spells, then all of the sudden I get the disconnected screen.

No issues with web browsers or anything .. I get dc'd to character select and can hop right back into the game but I can't go for more than probably 15-30 minutes without another disconnect.

Edit:

As I as posting this, it was "connecting to p99 .. " then timed out lol. Other webpages reloaded and worked fine while this page timed out.

ReEdit:

Still having issues after resetting router / modem. Can't even get logged in now. It seems when I'm getting disconnected from the game, this website also freezes up and times out.

[Leamam]

Cyberghost seems to have fixed the issue for me

[SunDrake]

Glad I found this thread. Another Charter user who has been experiencing these issues for the past few days. Will use VPN for now, but keeping an eye on any fixes.

[Sirviver]

It was easy to set-up, just install and press the connect button. Done.
Thank you very much. My connection is definitely strong now.

[Kreylyn]

So... Log in at 7:15am today, no disconnects all morning. Almost 5 hours now.

No response to my ticket inquiry yet...

/hopeful

Krey

[Shatford]

I tried the CyberGhost VPN and it was super laggy. I normally have a latency of 60ms, but with the VPN I was clocking in at 450-500ms. It was playable, but it still did not resolve my issues.

I've exhausted all possibilities and I'm doing a whipe, fresh OS install followed by a fresh EQ download and install. I am praying that works.

I am convinced that the DDoS attacks on p99's servers caused the admins to increase network security, but by doing so, they've caused problems for 10% of all users who had the game working with familiar regularity, then all of the sudden are in the same boat as all of us with the constant LD's. It's a catch 22.

[Kreylyn]

Not a single disconnect from either location all day.

/still hopeful

Krey

[TheBlackSheep]

Chances are Charter isn't going to tell you anything, unfortunately. It's not Charter's routers that are the problem. It's GTT's. It was dying after it jumped from a Charter router in Atlanta to:

ae10-69.cr1-nyc3.ip4.gtt.net

That's a Global Telecom router in NYC. The issue is with GTT's routing. It has to go through GTT's routers in NYC before it can get to the data center the server is hosted in, in New Jersey. Currently it seems there are still some issues on that router. It hasn't dropped any packets, but it has a higher latency than Rogean's server.

Glad you guys got it sorted out. Hopefully GTT will get their act together.

[Kreylyn]

Chances are Charter isn't going to tell you anything, unfortunately. It's not Charter's routers that are the problem. It's GTT's. It was dying after it jumped from a Charter router in Atlanta to:

ae10-69.cr1-nyc3.ip4.gtt.net

That's a Global Telecom router in NYC. The issue is with GTT's routing. It has to go through GTT's routers in NYC before it can get to the data center the server is hosted in, in New Jersey. Currently it seems there are still some issues on that router. It hasn't dropped any packets, but it has a higher latency than Rogean's server.

Glad you guys got it sorted out. Hopefully GTT will get their act together.

I agree with your points.

Additionally though, charter's systems tell it's users what dynamic route to take to get from point A to point z. They can see a problem with another's hub point, and temp/perm remove it from the options of hubs.

That was /is my hope of what happened. OR they contacted GTT and said fix yo sheet.

KRey

[TheBlackSheep]

I agree with your points.

Additionally though, charter's systems tell it's users what dynamic route to take to get from point A to point z. They can see a problem with another's hub point, and temp/perm remove it from the options of hubs.

That was /is my hope of what happened. OR they contacted GTT and said fix yo sheet.

KRey

Chances are GTT already knew about it. All these guys have NOCs that monitor everything. There is a lot of automation now. Its probably been in a dispatch queue for a couple of days with a low priority, since it isn't completely down.