Can someone help decipher my trace route and offer a possible fix?

tylerhalversonb16_ESO · April 2014

After searching high and low, I found a few people who appear to have similar problems. My game isn't crashing (I don't get an error and kicked out to desktop) but I am constantly getting logged out back to the title screen and unable to log in again for a few minutes. I ran a trace route and these were my results:

1 192.168.1.254 (192.168.1.254) 3.563 ms 1.501 ms 1.735 ms
2 10.144.48.1 (10.144.48.1) 8.144 ms 7.767 ms 7.708 ms
3 208.181.241.222 (208.181.241.222) 10.814 ms 9.349 ms 8.651 ms
4 209.121.72.251 (209.121.72.251) 13.425 ms
209.121.72.249 (209.121.72.249) 9.061 ms 13.580 ms
5 * * *
6 sttlwawbci01.bb.telus.com (75.154.217.108) 15.881 ms * *
7 sea-b1-link.telia.net (213.248.91.169) 13.699 ms
sea-b1-link.telia.net (80.239.128.217) 11.612 ms 19.202 ms
8 att-ic-153030-sea-b1.c.telia.net (195.12.254.190) 50.720 ms 11.443 ms 11.700 ms
9 cr81.st0wa.ip.att.net (12.122.82.10) 71.265 ms 75.041 ms 72.673 ms
10 cr2.st6wa.ip.att.net (12.122.5.198) 74.086 ms 72.179 ms 71.363 ms
11 cr1.st6wa.ip.att.net (12.122.31.121) 71.093 ms 73.042 ms 72.042 ms
12 cr2.sffca.ip.att.net (12.122.31.194) 70.767 ms 74.007 ms 71.939 ms
13 cr2.la2ca.ip.att.net (12.122.31.133) 73.365 ms 73.883 ms 72.653 ms
14 cr2.dlstx.ip.att.net (12.122.28.177) 72.681 ms 76.698 ms 71.924 ms
15 ggr3.dlstx.ip.att.net (12.122.138.25) 69.014 ms 73.228 ms 221.969 ms
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 * * *

I don't know what the * * * mean, but apparently that's bad?

Moonraker · April 2014

tylerhalversonb16_ESO wrote: »

After searching high and low, I found a few people who appear to have similar problems. My game isn't crashing (I don't get an error and kicked out to desktop) but I am constantly getting logged out back to the title screen and unable to log in again for a few minutes. I ran a trace route and these were my results:

1 192.168.1.254 (192.168.1.254) 3.563 ms 1.501 ms 1.735 ms
2 10.144.48.1 (10.144.48.1) 8.144 ms 7.767 ms 7.708 ms
3 208.181.241.222 (208.181.241.222) 10.814 ms 9.349 ms 8.651 ms
4 209.121.72.251 (209.121.72.251) 13.425 ms
209.121.72.249 (209.121.72.249) 9.061 ms 13.580 ms
5 * * *
6 sttlwawbci01.bb.telus.com (75.154.217.108) 15.881 ms * *
7 sea-b1-link.telia.net (213.248.91.169) 13.699 ms
sea-b1-link.telia.net (80.239.128.217) 11.612 ms 19.202 ms
8 att-ic-153030-sea-b1.c.telia.net (195.12.254.190) 50.720 ms 11.443 ms 11.700 ms
9 cr81.st0wa.ip.att.net (12.122.82.10) 71.265 ms 75.041 ms 72.673 ms
10 cr2.st6wa.ip.att.net (12.122.5.198) 74.086 ms 72.179 ms 71.363 ms
11 cr1.st6wa.ip.att.net (12.122.31.121) 71.093 ms 73.042 ms 72.042 ms
12 cr2.sffca.ip.att.net (12.122.31.194) 70.767 ms 74.007 ms 71.939 ms
13 cr2.la2ca.ip.att.net (12.122.31.133) 73.365 ms 73.883 ms 72.653 ms
14 cr2.dlstx.ip.att.net (12.122.28.177) 72.681 ms 76.698 ms 71.924 ms
15 ggr3.dlstx.ip.att.net (12.122.138.25) 69.014 ms 73.228 ms 221.969 ms
16 * * *

Well, it looks OK except for perhaps some delay at hop 6. hop 5 is probably just the router refusing to allow ping from traceroute. Unless it's a long stall on that one it probably nothing.

It will always end with *** as it will be blocked from pinging the game server directly (stop attacks etc.) so that's as far as it goes. Really it seems OK. Mine from Europe to Europe Megaserver ends in the same place;

Traceroute has started…

traceroute to 198.20.200.67 (198.20.200.67), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 1.274 ms 1.327 ms 1.109 ms
2 xx.xx.xx.xx. (xx.xx.xx.xx.) 22.507 ms 21.075 ms 20.885 ms
3 10.125.175.202 (10.125.175.202) 21.993 ms 22.380 ms 22.679 ms
4 xe-0-2-2-0.nctou201.toulouse.francetelecom.net (193.253.93.194) 22.116 ms 22.136 ms 21.598 ms
5 ae43-0.nipoi101.poitiers.francetelecom.net (193.252.160.49) 27.417 ms 27.995 ms 40.772 ms
6 81.253.184.58 (81.253.184.58) 42.000 ms 47.001 ms 41.390 ms
7 tengige0-7-0-8.madtr1.madrid.opentransit.net (193.251.128.177) 41.705 ms 43.636 ms 45.075 ms
8 tengige0-7-0-2.nyktr1.newyork.opentransit.net (193.251.242.158) 150.738 ms 152.182 ms 152.252 ms
9 tengige0-0-0-0.nyktr2.newyork.opentransit.net (193.251.129.50) 149.680 ms 152.052 ms 151.931 ms
10 te2-1.chise1.chicago.opentransit.net (193.251.129.53) 176.470 ms 175.852 ms 196.712 ms
11 192.205.32.61 (192.205.32.61) 175.102 ms 171.837 ms 171.495 ms
12 cr2.cgcil.ip.att.net (12.122.132.158) 176.526 ms 175.743 ms 175.714 ms
13 cr2.sl9mo.ip.att.net (12.122.2.22) 176.628 ms 180.360 ms 179.306 ms
14 cr1.sl9mo.ip.att.net (12.122.2.217) 173.280 ms 171.703 ms 172.548 ms
15 cr2.dlstx.ip.att.net (12.122.3.221) 176.485 ms 176.455 ms 176.250 ms
16 ggr3.dlstx.ip.att.net (12.122.138.25) 182.116 ms 182.948 ms 182.058 ms
17 * * *

From other threads it's most likely some issue at server end.

tylerhalversonb16_ESO · April 2014

DAMN! Thanks for the reply and clearing things up. I was hoping something there might have been causing my constant logging out issue. Guess I'll have to look around some more.

Moonraker · April 2014

tylerhalversonb16_ESO wrote: »

DAMN! Thanks for the reply and clearing things up. I was hoping something there might have been causing my constant logging out issue. Guess I'll have to look around some more.

No problem. Good luck with it.