Server Delay - Cons/Msgs/Disconnects - Page 2

Oleris · #11 07-31-2014, 04:36 PM

I've re-booted my router several times. I was told that it was potentially throttling by TWC by a GM. I wouldn't be surprised if this was a TWC only issue. I also restarted my modem and it did not fix the issue. Needless to say, I won't be trying to solo the rest of 59.

Bagelstein · #12 08-01-2014, 08:58 AM

I have RCN cable in MA, US, and I have this issue consistently. Long periods of spellcasting delays, conning delays, etc. Rebooted modem and router a few times to see if it was me, but I have no lag issues elsewhere in my online experience.

Is there a port or something I can forward to for p99? Anything I can screw with on router settings maybe? This is making charm kiting impossible...

Edit: Speedtest results: http://www.speedtest.net/my-result/3661629148

Derubael · #13 08-01-2014, 02:24 PM

If you could all post your ISP's and location, that'd be helpful.

I've noticed a bit of lag here and there, but it clears quickly. It's possible there's an issue with the way your connection is being routed to us. Sometimes one of those links slows down and certain people get issues. If any of you are up to it, do a tracert rogean.com from the command prompt and copy/paste your results.

Bagelstein · #14 08-01-2014, 03:54 PM

definitely some weirdness. below is the traceroute from my mac; I can do it from the PC later. not sure why it just dies at the 10th hop.

ISP: RCN
Location: Framingham, MA (30min outside of Boston)

traceroute to rogean.com (108.61.129.165), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.590 ms 0.980 ms 0.857 ms
2 bdl1.frm-ubr1.sbo-frm.ma.cable.rcn.net (10.16.96.1) 5.929 ms 7.002 ms 8.539 ms
3 bvi200.aggr2.sbo.ma.rcn.net (10.65.92.101) 8.650 ms 15.053 ms 31.978 ms
4 tge0-1-0-0.core1.sbo.ma.rcn.net (207.172.15.146) 14.279 ms
tge0-0-0-0.core1.sbo.ma.rcn.net (207.172.15.131) 15.723 ms
tge0-0-0-0.core2.sbo.ma.rcn.net (207.172.15.130) 15.387 ms
5 tge0-0-0-1.core2.nyw.ny.rcn.net (207.172.19.221) 21.253 ms
tge0-1-0-2.core1.nyw.ny.rcn.net (207.172.19.60) 13.328 ms
tge0-1-0-6.core1.nyw.ny.rcn.net (207.172.19.16) 25.616 ms
6 bdle3.border2.nyw.ny.rcn.net (207.172.15.85) 32.173 ms
bdle2.border2.nyw.ny.rcn.net (207.172.15.67) 14.729 ms
bdle3.border2.nyw.ny.rcn.net (207.172.15.85) 18.029 ms
7 nyiix.gi3-6.cr1.nyc1.choopa.net (198.32.160.157) 16.043 ms 18.456 ms 23.715 ms
8 ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net (108.61.80.26) 16.875 ms 17.804 ms 18.648 ms
9 vl203-cr1.ewr3.choopa.net (216.155.128.2) 19.271 ms 27.313 ms 41.780 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

Oleris · #15 08-01-2014, 06:13 PM

I've ran tracert to project 1999.org over the past week with the issues. sometimes rogean would be around 80-100, othertimes it would be around 150.

my ISP is Time Warner Cable from socal, I will edit out my IP adress from the ping test

a diriect tracert to rogean.com gave me:

Tracing route to rogean.com
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

3 10 ms 9 ms 12 ms 76.167.28.173
4 13 ms 11 ms 11 ms agg23.cyprcabw02r.socal.rr.com [72.129.21.88]
5 11 ms 15 ms 15 ms agg27.tustcaft01r.socal.rr.com [72.129.21.2]
6 13 ms 11 ms 11 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
7 10 ms 12 ms 12 ms ae3.pr1.lax10.tbone.rr.com [107.14.19.56]
8 11 ms * * xe-2-0-4.ar1.lax1.us.nlayer.net [69.31.127.73]
9 11 ms 12 ms 12 ms ae0-110g.cr1.lax1.us.nlayer.net [69.31.127.141]

10 50 ms 50 ms 50 ms xe-5-3-0.cr1.iah1.us.nlayer.net [69.22.142.121]

11 96 ms 97 ms 125 ms ae4-517.cr1.atl1.us.nlayer.net [69.22.142.134]
12 * 110 ms 111 ms xe-8-3-0.cr1.nyc2.us.nlayer.net [69.22.142.141]

13 102 ms 103 ms * vlan-77.ar1.nyc3.us.nlayer.net [69.31.34.132]
14 110 ms 116 ms 110 ms as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62]

15 100 ms 102 ms 101 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
16 111 ms 111 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
17 99 ms 102 ms 98 ms rogean.com [108.61.129.165]

Trace complete.

arsenalpow · #16 08-01-2014, 09:19 PM

my usual ping is 65is 75ish in EQ, it's now 100ish and it's the only thing that lags

also a TWC user, it's kind of annoying

**Rogean** · #17 08-01-2014, 10:55 PM

This seems to be isolated to TWC or a common carrier they use (RCN? Framingham has so many other options. FIOS.. Probably Comcast too...).

There's nothing I can do from this side, just need to wait for them to clear up whatever it is.

Oleris · #18 08-02-2014, 01:59 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

This seems to be isolated to TWC or a common carrier they use (RCN? Framingham has so many other options. FIOS.. Probably Comcast too...).

There's nothing I can do from this side, just need to wait for them to clear up whatever it is.

It's just strange that this popped up just a week ago. Hopefully it will clear up soon, thanks for the response though.

Vidrata · #19 08-03-2014, 05:59 PM

having same issues at my friends house. He's using DSL from frontier. Tracert dies on the 5th hope but gets rerouted to somewhere in chicago and goes on its way to you; around 15 jumps.

Below is a tracert x3. 2 out of 3 its bad pings, but that shouldnt effect the connect to get in game; considering the game was played with worse on dial.

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

C:\Users\Ally>tracert rogean.com

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

1 1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 1686 ms 1651 ms 2089 ms drr02.nrwl.oh.frontiernet.net [74.42.148.99]
3 2238 ms 2224 ms 685 ms ge--0-1-2---0.arr01.nrwl.oh.frontiernet.net [50.
42.14.17]
4 771 ms 1243 ms 1909 ms ae4---0.car03.chcg.il.frontiernet.net [74.42.149
.189]
5 2317 ms * * ae0---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
38]
6 46 ms 44 ms 47 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.NET [206.223
.119.12]
7 45 ms 43 ms 45 ms ae-6.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
4]
8 68 ms 61 ms * ae-4.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.4
1]
9 66 ms 62 ms 68 ms ae-1.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
49]
10 63 ms 61 ms 59 ms ae10.ar2.nyc3.us.nlayer.net [69.31.34.192]
11 70 ms 76 ms 63 ms as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62]

12 62 ms 62 ms 70 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
13 65 ms 67 ms 67 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
14 62 ms 61 ms 71 ms rogean.com [108.61.129.165]

Trace complete.

C:\Users\Ally>tracert rogean.com

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

1 4 ms 4 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 37 ms 35 ms 34 ms drr02.nrwl.oh.frontiernet.net [74.42.148.99]
3 35 ms 34 ms 36 ms ge--0-1-2---0.arr01.nrwl.oh.frontiernet.net [50.
42.14.17]
4 48 ms 45 ms 44 ms ae4---0.car03.chcg.il.frontiernet.net [74.42.149
.189]
5 43 ms 44 ms 41 ms ae0---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
38]
6 46 ms 42 ms 46 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.NET [206.223
.119.12]
7 43 ms 44 ms 45 ms ae-6.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
4]
8 62 ms 60 ms 62 ms ae-4.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.4
1]
9 72 ms 58 ms 61 ms ae-13.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.
166]
10 221 ms 350 ms * ae12.ar1.nyc3.us.nlayer.net [69.31.34.182]
11 1439 ms 1671 ms 2096 ms as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62]

12 2403 ms 1266 ms 121 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
13 219 ms 343 ms 666 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
14 742 ms 830 ms 995 ms rogean.com [108.61.129.165]

Trace complete.

C:\Users\Ally>tracert rogean.com

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

1 1 ms <1 ms <1 ms dslrouter.netgear.com [192.168.254.254]
2 2183 ms 2307 ms 1986 ms drr02.nrwl.oh.frontiernet.net [74.42.148.99]
3 1092 ms 1078 ms 1562 ms ge--0-1-2---0.arr01.nrwl.oh.frontiernet.net [50.
42.14.17]
4 2264 ms 2249 ms 1917 ms ae4---0.car03.chcg.il.frontiernet.net [74.42.149
.189]
5 * 2124 ms * ae0---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
38]
6 1936 ms 1154 ms 1160 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.NET [206.223
.119.12]
7 1742 ms 2247 ms 2318 ms ae-6.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
4]
8 1520 ms 1256 ms 1713 ms ae-4.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.4
1]
9 245 ms 61 ms 55 ms ae-13.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.
166]
10 63 ms 63 ms 63 ms ae12.ar1.nyc3.us.nlayer.net [69.31.34.182]
11 60 ms 65 ms 61 ms as20473.ae7.ar2.nyc3.us.nlayer.net [69.31.34.78]

12 57 ms 60 ms 72 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
13 71 ms 68 ms 66 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
14 66 ms 61 ms 62 ms rogean.com [108.61.129.165]

Trace complete.

Oleris · #20 08-04-2014, 03:21 AM

Well, I found someone else that has TWC and plays on the server. He happens to live in the same city as me and lives 5 minutes away. We both experience the issues at the same exact time. 2 "True" Linkdeads tonight where the 100% slowly went down at identical times, but the internet was still working. Here's hoping TWC fixes it.