Level3 issues? Post some info here

1 <1 ms <1 ms <1 ms Speedport.ip [192.168.2.1]
2 20 ms 19 ms 19 ms 217.0.117.179
3 24 ms 23 ms 23 ms 87.186.197.82
4 23 ms 23 ms 23 ms 217.239.52.134
5 48 ms 43 ms 43 ms 62.157.250.74
6 126 ms 124 ms 119 ms ae-130-3516.edge6.Amsterdam1.Level3.net [4.69.16
.238]
7 246 ms 216 ms 210 ms SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.
6.190]
8 118 ms 118 ms 118 ms amspsn-liv-gw04.planetside2.com [69.174.194.168]

Yeah, today Level3 has some more problems than usual - problems occurring for 3 hours now. Connection quality ingame is yellow - ping between 150ms and 200ms:

Traceroute to Cobalt:

Code:

tracert 69.174.194.166
 
  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.178.1]
  2    18 ms    17 ms    18 ms  217.0.119.205
  3    19 ms    18 ms    18 ms  217.0.89.246
  4    20 ms    20 ms    21 ms  217.239.52.74
  5    52 ms    *      52 ms  62.157.250.70
  6  115 ms  117 ms  139 ms  ae-130-3516.edge6.Amsterdam1.Level3.net [4.69.162.238]
  7  120 ms  120 ms  119 ms  SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
  8  120 ms  120 ms  121 ms  amspsn-liv-gw02.planetside2.com [69.174.194.166]

Traceroute from Level3:

Code:

  1  ae-120-3506.edge4.Amsterdam1.Level3.net (4.69.162.181)    0.817 ms  0.717 ms  0.806 ms
  2  64.208.27.145 (64.208.27.145)    98.0 ms  97.8 ms  191 ms
  3  80.156.160.57 (80.156.160.57)    96.3 ms  99.5 ms  110 ms
  4  k-ea2-i.K.DE.NET.DTAG.DE (217.5.73.109)    108 ms  108 ms  105 ms
  5  217.0.89.225 (217.0.89.225)    102 ms  106 ms  105 ms
  6   (DELETED)    122 ms !filtered  119 ms !filtered  121 ms !filtered

Ping graph:
http://i.imgur.com/ELnBNsc.png

0 XXXXX-PC.fritz.box [192.168.178.20]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 16ms 0/ 100 = 0% 0/ 100 = 0% 217.0.119.22
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% 87.190.163.58
0/ 100 = 0% |
4 23ms 0/ 100 = 0% 0/ 100 = 0% f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.238]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% te-3-0-0.edge5.Frankfurt1.Level3.net [4.68.62.141]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% ae-129-3515.edge6.Amsterdam1.Level3.net [4.69.162.234]
0/ 100 = 0% |
7 128ms 1/ 100 = 1% 1/ 100 = 1% SONY-ONLINE.edge6.Amsterdam1.Level3.net [212.72.46.190]
0/ 100 = 0% |
8 123ms 0/ 100 = 0% 0/ 100 = 0% amspsn-liv-gw02.planetside2.com [69.174.194.166]

Routenverfolgung zu lp.soe.com [64.37.171.24] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms [192.168.2.1]
2 18 ms 18 ms 18 ms 217.0.118.227
3 19 ms 19 ms 19 ms 87.190.168.226
4 23 ms 23 ms 23 ms 217.239.39.2
5 23 ms 23 ms 23 ms te-3-0-0.edge5.Frankfurt1.Level3.net [4.68.62.14
1]
6 175 ms 175 ms 175 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

7 176 ms 176 ms 176 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
8 176 ms 176 ms 176 ms lp.soe.com [64.37.171.24]

Ablaufverfolgung beendet.

since u're from germany and probably playing on one of the EU servers rather tracert/pathping amspsn-liv-gw02.planetside2.com [69.174.194.166] which is the european game serveri in Amsterdam

4 11 ms 13 ms 11 ms te-0-2-0-8-sur03.bellevue.wa.seattle.comcast.net
[68.86.98.193]
5 14 ms 12 ms 14 ms be-40-ar01.seattle.wa.seattle.comcast.net [69.13
9.164.6]
6 16 ms 15 ms 15 ms he-1-3-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.93.165]
7 24 ms 23 ms 24 ms 66.208.232.170
8 38 ms 31 ms 41 ms tge2-2.fr3.sjc.llnw.net [69.28.171.145]
9 54 ms 45 ms 48 ms tge11-4.fr3.lax.llnw.net [69.28.172.53]
10 53 ms 48 ms 48 ms ve6.fr4.lax.llnw.net [69.28.171.206]
11 46 ms 55 ms 49 ms tge2-4.fr3.las.llnw.net [69.28.172.85]
12 50 ms 46 ms 47 ms switch.ge3-1.fr3.las.llnw.net [208.111.176.2]
13 47 ms 48 ms 45 ms be775.las-score7-3.sinap-tix.com [199.189.116.20
5]
14 46 ms 46 ms 47 ms sony.demarc3.sinap-tix.com [64.79.157.78]
15 46 ms 46 ms 44 ms lp.soe.com [64.37.171.24]

Up

I am at 150ms annd i played at 60ms it is horrible impossible to play vs shotgun player.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.254 - 0 | 125 | 125 | 0 | 0 | 4 | 0 |
| 78.202.246.254 - 0 | 125 | 125 | 5 | 8 | 27 | 7 |
| 213.228.41.158 - 0 | 125 | 125 | 6 | 8 | 26 | 7 |
| rennes-6k-1-po6.intf.routers.proxad.net - 0 | 125 | 125 | 6 | 8 | 28 | 7 |
| p11-9k-1-be1021.intf.routers.proxad.net - 0 | 125 | 125 | 12 | 13 | 33 | 12 |
|p11-crs16-1-be1004.intf.routers.proxad.net - 4 | 109 | 105 | 12 | 16 | 57 | 13 |
| th2-9k-1-be1001.intf.routers.proxad.net - 0 | 125 | 125 | 12 | 14 | 32 | 12 |
| ae56.edge4.Paris1.Level3.net - 39 | 49 | 30 | 0 | 46 | 96 | 48 |
| ae-239-3615.edge6.Amsterdam1.Level3.net - 0 | 125 | 125 | 42 | 53 | 85 | 48 |
| SONY-ONLINE.edge6.Amsterdam1.Level3.net - 0 | 125 | 125 | 44 | 57 | 220 | 51 |
| amspsn-liv-gw03.planetside2.com - 0 | 125 | 125 | 43 | 53 | 123 | 50 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Cavalier Telephone (aka CavTel)/Windstream - Virginia, USA.

This is the only internet-related issue that I have currently. Other SOE All Access MMO's are running fine.
Issue started Dec 23rd and it is on-going.

I get to the character selection screen fine. I can pick any of my characters. When I click on play, the music continues to play and the logging in message comes up (where "play" would be). The little progress indicator to the left stops moving. The music continues to play until the game crashes and I get sent to a web page that says "Game Error G15".
This same webpage has links to character profile information. When I look up my characters, the character that I logged in last shows up as being "on-line" even though the client has crashed. This changes when I try to log-in into a different character to show the last character that I attempted to be logged into as being logged in after the game crashes.
According to SOE Customer Service, when I attempt to log in a character it remains on-line for 15 minutes.

I contacted my Cavalier Telephone/Windstream today and put in a ticket in regards to the complete packet loss at LEVEL3.
Any pressure you can put on LEVEL3 from your side is appreciated.


Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:
0 -- Removed for security sake ---
1 -- Removed for security sake ---
2 ge-0-0-4-109.cr01.rcmdvazo.cavtel.com [64.83.47.149]
3 static-76-161-151-107.dsl.cavtel.net [76.161.151.107]
4 xe-2-2-2.er01.asbnvaeq.cavtel.com [76.160.127.10]
5 h230.18.129.40.static.ip.windstream.net [40.129.18.230]
6 ash-b1-link.telia.net [213.248.99.229]
7 ash-b1-link.telia.net [213.155.137.228]
8 carrierdomain-ic-310000-ffm-b10.c.telia.net [213.248.88.86]
9 ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
10 SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
11 lp.soe.com [64.37.171.24]
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 -- Removed for security sake ---
0/ 100 = 0% |
1 10ms 0/ 100 = 0% 0/ 100 = 0% -- Removed for security sake ---
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% ge-0-0-4-109.cr01.rcmdvazo.cavtel.com [64.83.47.149]
0/ 100 = 0% |
3 20ms 0/ 100 = 0% 0/ 100 = 0% static-76-161-151-107.dsl.cavtel.net [76.161.151.107]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% xe-2-2-2.er01.asbnvaeq.cavtel.com [76.160.127.10]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% h230.18.129.40.static.ip.windstream.net [40.129.18.230]
0/ 100 = 0% |
6 27ms 0/ 100 = 0% 0/ 100 = 0% ash-b1-link.telia.net [213.248.99.229]
0/ 100 = 0% |
7 38ms 0/ 100 = 0% 0/ 100 = 0% ash-b1-link.telia.net [213.155.137.228]
0/ 100 = 0% |
8 26ms 0/ 100 = 0% 0/ 100 = 0% carrierdomain-ic-310000-ffm-b10.c.telia.net [213.248.88.86]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
0/ 100 = 0% |
10 92ms 0/ 100 = 0% 0/ 100 = 0% SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
0/ 100 = 0% |
11 85ms 0/ 100 = 0% 0/ 100 = 0% lp.soe.com [64.37.171.24]
Trace complete.

Connection to Cobalt
200-300ms
Routenverfolgung zu amspsn-liv-gw01.planetside2.com [69.174.194.165]
ber maximal 30 Abschnitte:
0 XXX-PC.Speedport_W_921V_1_36_000 [192.168.2.116]
1 speedport.ip [192.168.2.1]
2 87.186.224.82
3 87.190.161.202
4 l-eb2-i.L.DE.NET.DTAG.DE [62.154.89.46]
5 217.243.216.202
6 ae-126-3512.edge3.Amsterdam1.Level3.net [4.69.162.174]
7 SONY-ONLINE.edge3.Amsterdam1.Level3.net [212.72.33.26]
8 amspsn-liv-gw01.planetside2.com [69.174.194.165]


Berechnung der Statistiken dauert ca. 200 Sekunden...
Quelle zum Abs. Knoten/Verbindung Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 XXX-PC.Speedport_W_921V_1_36_000 [192.168.2.116]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% speedport.ip [192.168.2.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/100 = 0% 87.186.224.82
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% 87.190.161.202
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0%l-eb2-i.L.DE.NET.DTAG.DE [62.154.89.46]
1/ 100 = 1% |
5 --- 100/ 100 =100% 99/ 100 = 99% 217.243.216.202
0/ 100 = 0% |
6 --- 100/ 100 =100% 99/ 100 = 99% ae-126-3512.edge3.Amsterdam1.Level3.net [4.69.162.174]
0/ 100 = 0% |
7 246ms 1/ 100 = 1% 0/ 100 = 0% SONY-ONLINE.edge3.Amsterdam1.Level3.net [212.72.33.26]
0/ 100 = 0% |
8 243ms 1/ 100 = 1% 0/ 100 = 0% amspsn-liv-gw01.planetside2.com [69.174.194.165]
Ablaufverfolgung beendet.

I'm in Livingston UK, connecting to Miller:

In game connection status fluctuates between 300ms - 5000ms+ latency and Connection Quality between bad, poor and good.

Traceroute at the moment is:
1 9 ms 8 ms 7 ms cpc3-livi5-2-0-gw.sgyl.cable.virginm.net [77.97.236.1]
2 8 ms 7 ms 6 ms sgyl-core-2b-ae9-706.network.virginmedia.net [81.97.49.161]
3 * * * Request timed out.
4 * * * Request timed out.
5 30 ms 26 ms 24 ms nrth-bb-1c-ae1-0.network.virginmedia.net [62.254.42.222]
6 * * * Request timed out.
7 35 ms 34 ms 36 ms be5089.agr21.fra03.atlas.cogentco.com [130.117.14.133]
8 35 ms 34 ms 36 ms be2184.ccr41.fra03.atlas.cogentco.com [130.117.48.70]
9 191 ms 192 ms 192 ms be2259.ccr41.par01.atlas.cogentco.com [154.54.62.73]
10 192 ms 192 ms 192 ms be2497.ccr41.lon13.atlas.cogentco.com [154.54.39.65]
11 194 ms 192 ms 192 ms be2391.ccr21.lpl01.atlas.cogentco.com [154.54.39.150]
12 190 ms 191 ms 194 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44.161]
13 190 ms 193 ms 192 ms be2137.ccr41.ord01.atlas.cogentco.com [154.54.43.193]
14 190 ms 193 ms 191 ms be2152.ccr21.dca01.atlas.cogentco.com [154.54.30.121]
15 201 ms 191 ms 191 ms be2168.ccr41.atl01.atlas.cogentco.com [154.54.31.93]
16 191 ms 193 ms 192 ms be2172.ccr21.iah01.atlas.cogentco.com [154.54.29.18]
17 194 ms 192 ms 194 ms be2065.ccr21.lax01.atlas.cogentco.com [154.54.5.66]
18 201 ms 200 ms 200 ms be2536.rcr21.las02.atlas.cogentco.com [154.54.82.26]
19 200 ms 207 ms 200 ms 154.24.35.242
20 240 ms 245 ms 250 ms 38.104.170.102
21 277 ms 295 ms 285 ms be775.las-score7-3.sinap-tix.com [199.189.116.205]
22 215 ms 207 ms 207 ms sony.demarc3.sinap-tix.com [64.79.157.78]
23 206 ms 208 ms 209 ms lp.soe.com [64.37.171.24]

to much packet loss this morning.

C:\WINDOWS\system32>ping www.planetside2.com

Pinging planetside2.com [64.37.171.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 64.37.171.22: bytes=32 time=78ms TTL=120

Ping statistics for 64.37.171.22:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 78ms, Average = 78ms

C:\WINDOWS\system32>tracert www.planetside2.com

Tracing route to planetside2.com [64.37.171.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 21 ms 21 ms 21 ms phnx-dsl-gw68.phnx.qwest.net [67.40.227.68]
3 21 ms 21 ms 21 ms phnx-agw1.inet.qwest.net [75.160.238.25]
4 34 ms 34 ms 34 ms los-brdr-01.inet.qwest.net [67.14.102.30]
5 * 32 ms 32 ms 63.146.27.34
6 37 ms 38 ms 38 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

7 38 ms 37 ms 37 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

8 * * 81 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
9 * 38 ms 38 ms www-new.planetside2.com [64.37.171.22]

Trace complete.

Routenverfolgung zu amspsn-liv-gw01.planetside2.com [69.174.194.165] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 24 ms 23 ms 21 ms 217.0.118.45
3 25 ms 26 ms 26 ms 87.186.241.6
4 24 ms 24 ms 24 ms 217.239.52.82
5 54 ms 54 ms 54 ms te-3-0-0.edge5.Frankfurt1.Level3.net [4.68.62.141]
6 55 ms 53 ms 107 ms ae-129-3515.edge6.Amsterdam1.Level3.net [4.69.162.234]
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.
18 * * * Zeitüberschreitung der Anforderung.
19 * * * Zeitüberschreitung der Anforderung.
20 * * * Zeitüberschreitung der Anforderung.
21 * * * Zeitüberschreitung der Anforderung.
22 * * * Zeitüberschreitung der Anforderung.
23 * * * Zeitüberschreitung der Anforderung.
24 * * * Zeitüberschreitung der Anforderung.
25 * * * Zeitüberschreitung der Anforderung.
26 * * * Zeitüberschreitung der Anforderung.
27 * * * Zeitüberschreitung der Anforderung.
28 * * * Zeitüberschreitung der Anforderung.
29 * * * Zeitüberschreitung der Anforderung.
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

I have the exactly same picture with the this:
69.174.194.166
69.174.194.167
69.174.194.168

Is there any chance to fix this? I mean. I have ping problems since dezember 2014. Or is that a fight between Level 3 and Deutsche Telecom and all i can do is to deinstall this game forever?

You can't get a normal ping during primetime, so on evenings. It is because many people are in the internet and it will take longer from a server to response. I think, you can uninstall it or play only during non-primetime and wait for a fix (Which will never happen because German Telekom gives a **** about it)

It would be very hard for me to deinstall this game, because its still awsome and i spent over 200€ in this game.
3 weeks a go it was possible for me to play at 1am with constant 70ms. And now since this 3 weeks run my teammates and enemys the hole time for 2 or 3 seconds in the air. Hitching/warping. 24/7. And now its really unplayable.

logging to Cobalt this morning all was good, now there is massive lag cannot play game:

Pinging amspsn-liv-gw03.planetside2.com [69.174.194.167] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Update 1: still cannot ping Cobalt Server seems to be massive packet loss:

Tracert:

Tracing route to amspsn-liv-gw03.planetside2.com [69.174.194.167]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms livebox.home [192.168.1.1]
2 10 ms 8 ms 9 ms 197.225.224.1
3 10 ms 8 ms 8 ms 196.192.102.222
4 11 ms 9 ms 19 ms tengig4-1-tr.telecomplus.net [196.20.254.169]
5 230 ms 218 ms 218 ms 81.52.188.125
6 213 ms 215 ms 214 ms gigabitethernet8-0-2.marcr2.Marseille.opentransi
t.net [193.251.133.205]
7 208 ms 206 ms 208 ms tengige1-12-0-4.pastr1.Paris.opentransit.net [19
3.251.132.98]
8 * * * Request timed out.
9 280 ms 274 ms 277 ms ae-240-3616.edge6.Amsterdam1.Level3.net [4.69.16
2.254]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15

well i dont know what u guys are posting but my loading screen wont get to player selection it stops at 94% my friend is having the same problem and we dont live near eachother nor have the same internet provider

Tracing Route to Cobalt

1 <1 ms 1 ms <1 ms livebox.home [192.168.1.1]
2 10 ms 8 ms 8 ms 197.225.224.1
3 9 ms 10 ms 8 ms 196.192.102.222
4 10 ms 9 ms 11 ms tengig4-1-tr.telecomplus.net [196.20.254.169]
5 220 ms 221 ms 224 ms 81.52.188.125
6 217 ms 239 ms 214 ms gigabitethernet8-0-2.marcr2.Marseille.opentransi
t.net [193.251.133.205]
7 213 ms 210 ms 215 ms tengige1-12-0-5.pastr1.Paris.opentransit.net [19
3.251.132.166]
8 * * * Request timed out.
9 281 ms 276 ms 280 ms ae-238-3614.edge6.Amsterdam1.Level3.net [4.69.16
2.246]
10 * * * Request timed out.
11 * * * Request timed out.
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.

Tracing Route to Cobalt
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms livebox.home [192.168.1.1]
2 10 ms 11 ms 10 ms 197.225.224.1
3 8 ms 11 ms 8 ms 196.192.102.222
4 10 ms 9 ms 9 ms tengig4-1-tr.telecomplus.net [196.20.254.169]
5 248 ms 221 ms 221 ms 81.52.188.125
6 215 ms 214 ms 258 ms gigabitethernet13-2-1.marcr2.Marseille.opentrans
it.net [193.251.133.209]
7 212 ms 206 ms 206 ms tengige2-7-0-8.pastr1.Paris.opentransit.net [193
.251.151.21]
8 * * * Request timed out.
9 279 ms 275 ms 278 ms ae-238-3614.edge6.Amsterdam1.Level3.net [4.69.16
2.246]
10 * * * Request timed out.
11 * * * Request timed out.
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.


Tracing Route to Cobalt
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms livebox.home [192.168.1.1]
2 8 ms 7 ms 11 ms 197.225.224.1
3 11 ms 9 ms 9 ms 196.192.102.222
4 11 ms 11 ms 11 ms tengig4-1-tr.telecomplus.net [196.20.254.169]
5 222 ms 219 ms 220 ms 81.52.188.125
6 213 ms 213 ms 214 ms gigabitethernet13-2-1.marcr2.Marseille.opentran
it.net [193.251.133.209]
7 209 ms 208 ms 210 ms tengige1-12-0-5.pastr1.Paris.opentransit.net [1
3.251.132.166]
8 * * * Request timed out.
9 275 ms 276 ms 276 ms ae-238-3614.edge6.Amsterdam1.Level3.net [4.69.1
2.246]
10 * * * Request timed out.
11 * * * Request timed out.
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.

Tracing Route to Cobalt
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms livebox.home [192.168.1.1]
2 10 ms 8 ms 11 ms 197.225.224.1
3 12 ms 9 ms 10 ms 196.192.102.222
4 10 ms 11 ms 9 ms tengig4-1-tr.telecomplus.net [196.20.254.169]
5 291 ms 225 ms 221 ms 81.52.188.125
6 214 ms 213 ms 215 ms gigabitethernet8-0-2.marcr2.Marseille.opentrans
t.net [193.251.133.205]
7 210 ms 209 ms 211 ms tengige0-2-0-1.pastr1.Paris.opentransit.net [19
.251.129.179]
8 * * * Request timed out.
9 277 ms 276 ms 277 ms ae-240-3616.edge6.Amsterdam1.Level3.net [4.69.1
2.254]
10 * * * Request timed out.
11 * * * Request timed out.
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.

Issue has been on going since Sunday 15th March afternoon,in the morning all was ok but now I cannot play there is massive lag I believe issue is with level3 Router.

Please help

I send message daybreak about ping spike.
They told me that It's just your location problem.


Response Tongariki T. via Email 07/01/2015 01:30 PM
Greetings amender1,

We apologize you feel this way. If you have any other questions please let me us know and we'd be happy to help.

Regards,

Your reference number for this contact is: 150628-000034.

Tonga T.
Technical Support
DayBreak Games
Customer amender1 soe via CSS Web 06/30/2015 03:41 PM
Ok, I don't want to connect to other server.
I can't get over the answer that just my location problem..

I am playing ps2 in Korea since 2013.
Sometimes I had suffered ping spike once a day.

Of course I agree high pings are normal behavior but why dose the number of ping spike increase?
Recently, ping spikes occur frequently when server pop is overload.
I think that It means server pop occur ping spikes not just my connect location and server band width is not enough to keep these connect.

Maybe I stop playing this game. sadly.
I have no choice.

Anyway, Thank you replying so fast.
Response Tongariki T. via Email 06/30/2015 12:13 PM
Greetings amender1,

Since you are in Korea, high pings are a normal behavior due to transatlantic connections. You may want to connect to a server located the closest to your country.

Regards,

Your reference number for this contact is: 150628-000034.

Tonga T.
Technical Support
DayBreak Games
Customer amender1 soe via CSS Web 06/29/2015 09:06 PM

It is not my computer or my ISP problem.
It is your comunication company problem.

I found loss at level 3 node as tracert command result.
AGAIN ASK, I am wondering that your company have plan for Connery server fix.



1. KT in Korea
2. maybe kt device.
3. home
4. wireless
5. GigaBit Ethernet
6. maximum: 100 Mbps

Auto-Response 06/27/2015 08:45 PM
This is a courtesy message that has been generated based on you selecting the category: Connectivity.

We'll need some information about your computer to troubleshoot your connectivity issue. Please respond to your ticket with the following information.

1. Who is your ISP?
2. Make and model of the modem and router?
3. Are you at home/school/office?
4. Type of connection (Wireless/Wired)?
5. DSL, Cable or Fiber?
6. What are your download and upload speeds (You can check this by going to http://speedtest.net/ )?

In addition to this, please follow these instructions to collect information about the quality of your connection to our servers.

1. Go to Start > All Programs > Accessories, right-click the Command Prompt and select "Run as administrator"

For Windows 8 - Press the WINDOWS and X keys together and then click on Command Prompt (Admin). Click Yes to the User Account Control message that appears.

2. Copy and paste the below commands into your command prompt. You can paste into your command prompt by right clicking and selecting paste.

ipconfig /all > c:\netinfo.txt
tracert lp.soe.com >> c:\netinfo.txt
pathping lp.soe.com >> c:\netinfo.txt

These commands will not output to the command prompt, they will create a file named c:\netinfo.txt

Make sure to run each command one at a time. Because you are outputting to a file, it will appear as though nothing is happening for a while, especially on the second and third commands. Make sure you wait for the cursor to pop up again and allow you to type before proceeding to the next step. Once complete, please attach the file c:\netinfo.txt to your ticket and an agent will answer as soon as possible.
Customer amender1 soe via CSS Web 06/27/2015 08:45 PM
When sever pop is peak, I have ping spikes always.
Ping test result is avg ping =170~200 but packet loss 5 in 1 min.
Game playing is impossible.

Briggs server is good but Connery is very bad.
Korea user is suffering ping spikes.

How can I fix it?
Is there way to fix it?
It is Just sever problem or distance between countries?
Additionally, I am wondering that your company have plan for Connery server fix.

PSA-
Level3 has suffered a physical attack on backbone cables in California. Pretty sure the reason you have connectivity issues is because they are forced to route traffic in some rather inconvenient methods to allow for any conectivity at all for some people.

http://www.9news.com/story/news/loc...ttack-downs-services-with-cut-lines/29527161/