Starfleet Veteran
Join Date: Feb 2013
Posts: 1
# 11
02-02-2013, 11:11 AM
every time since the anniversary iv booted rubber banned and its ticking me off
Empire Veteran
Join Date: Jun 2012
Posts: 613
# 12
02-02-2013, 11:23 AM
This is getting outrageous... I pay to play and I can't because you servers or connection are undersized:


Traccia instradamento verso patchserver.crypticstudios.com [208.95.185.41]
su un massimo di 30 punti di passaggio:

1 40 ms 94 ms 86 ms dsldevice.lan [192.168.1.254]
2 47 ms 47 ms 47 ms static-213-205-16-41.clienti.tiscali.it [213.205.16.41]
3 48 ms 48 ms 48 ms static-94-32-137-177.clienti.tiscali.it [94.32.137.177]
4 48 ms 47 ms 47 ms static-213-205-57-65.clienti.tiscali.it [213.205.57.65]
5 67 ms 67 ms 66 ms static-213-205-57-229.clienti.tiscali.it [213.205.57.229]
6 67 ms 67 ms 66 ms static-213-205-17-61.clienti.tiscali.it [213.205.17.61]
7 79 ms 78 ms 105 ms 94.32.135.145
8 76 ms 75 ms 75 ms ae3-300.trn22.ip4.tinet.net [77.67.82.229]
9 171 ms 171 ms 171 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
10 181 ms 182 ms 193 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 196 ms 180 ms 180 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
12 237 ms 251 ms 253 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 250 ms 245 ms 247 ms 208.95.185.41

Traccia completata.


ping patchserver.crypticstudios.com

Esecuzione di Ping patchserver.crypticstudios.com [208.95.185.41] con 32 byte di dati:
Richiesta scaduta.
Risposta da 208.95.185.41: byte=32 durata=253ms TTL=49
Risposta da 208.95.185.41: byte=32 durata=253ms TTL=49
Risposta da 208.95.185.41: byte=32 durata=249ms TTL=49

Statistiche Ping per 208.95.185.41:
Pacchetti: Trasmessi = 4, Ricevuti = 3,
Persi = 1 (25% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 249ms, Massimo = 253ms, Medio = 251ms


25% lost!!!!


Since I pay to play, I want a refound!!!!!!!!

Last edited by eurialo; 02-02-2013 at 11:25 AM.
Ensign
Join Date: Aug 2012
Posts: 20
# 13
02-02-2013, 11:30 AM
Really bad lag, unplayable, ran all the tests from the sticky, ran additional tests from pingtest and speedtest, all seems ok 100Mb up 100Mb down, 8 ms response, less than 180ms to cryptic servers. I have seen some lag before but nothing like this, it started at about 17:00 UTC, today.
Ensign
Join Date: Aug 2012
Posts: 20
# 14
02-02-2013, 11:34 AM
Quote:
Originally Posted by defbond7 View Post
Really bad lag, unplayable, ran all the tests from the sticky, ran additional tests from pingtest and speedtest, all seems ok 100Mb up 100Mb down, 8 ms response, less than 180ms to cryptic servers. I have seen some lag before but nothing like this, it started at about 17:00 UTC, today.
Here's the tracert from Bucharest, Romania



Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 5 ms 1 ms 192.168.100.1
3 28 ms 5 ms 15 ms adsl92-86-128-129.romtelecom.net [92.86.128.129]

4 37 ms 37 ms 37 ms 10.0.241.205
5 35 ms 35 ms 35 ms 10.0.200.22
6 37 ms 36 ms 36 ms ffm-b7-link.telia.net [213.248.97.89]
7 35 ms 35 ms 35 ms ffm-bb2-link.telia.net [80.91.247.74]
8 36 ms 36 ms 36 ms ffm-b12-link.telia.net [213.155.135.15]
9 37 ms 36 ms 37 ms be100.ccr22.fra03.atlas.cogentco.com [130.117.14
.89]
10 41 ms 43 ms 43 ms te0-0-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.48.165]
11 56 ms 56 ms 56 ms te0-3-0-2.ccr21.lpl01.atlas.cogentco.com [154.54
.37.94]
12 59 ms 135 ms 119 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.31.189]
13 122 ms 121 ms 122 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 124 ms 125 ms 128 ms 38.111.40.114
15 129 ms 122 ms 120 ms 208.95.185.41

Trace complete.
Career Officer
Join Date: Jun 2012
Posts: 17
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms buffalo.setup [192.168.1.2]
2 2 ms 1 ms 1 ms 172.16.0.254
3 13 ms 12 ms 12 ms adsl-75-61-79-254.dsl.pltn13.sbcglobal.net [75.6
1.79.254]
4 13 ms 14 ms 14 ms 12.83.90.157
5 15 ms 14 ms 14 ms ggr6.wswdc.ip.att.net [12.122.86.89]
6 15 ms 17 ms 17 ms te0-2-0-6.ccr21.sjc03.atlas.cogentco.com [154.54
.12.113]
7 17 ms 17 ms 17 ms te0-4-0-3.ccr21.sjc01.atlas.cogentco.com [154.54
.41.201]
8 18 ms 17 ms 17 ms te0-3-0-5.ccr21.sfo01.atlas.cogentco.com [154.54
.86.177]
9 112 ms 112 ms 102 ms te0-4-0-6.ccr21.mci01.atlas.cogentco.com [154.54
.45.65]
10 78 ms 82 ms 79 ms te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54
.84.74]
11 92 ms 92 ms 89 ms te0-7-0-26.ccr21.bos01.atlas.cogentco.com [154.5
4.6.21]
12 91 ms 92 ms 92 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
13 96 ms 92 ms 89 ms 38.111.40.114
14 90 ms 89 ms 89 ms 208.95.185.41

Trace complete.

C:\Windows\system32>

contacting nettest server..
Local IP: 75.61.76.223
Ping: 88.2 msec
Port: 80: 245 KB/sec 9 KB/sec 259 KB/sec 500
Port: 80: 181 KB/sec 9 KB/sec 194 KB/sec 500
Port: 443: 247 KB/sec 10 KB/sec 262 KB/sec 500
Port: 443: 191 KB/sec 9 KB/sec 203 KB/sec 500
Port: 7255: 251 KB/sec 10 KB/sec 266 KB/sec 500
Port: 7255: 466 KB/sec 19 KB/sec 493 KB/sec 500
Port: 7003: 441 KB/sec 21 KB/sec 467 KB/sec 500
Port: 7003: 479 KB/sec 20 KB/sec 508 KB/sec 500
Port: 7202: 264 KB/sec 11 KB/sec 280 KB/sec 500
Port: 7202: 466 KB/sec 19 KB/sec 493 KB/sec 500
Port: 7499: 170 KB/sec 9 KB/sec 183 KB/sec 500
Port: 7499: 62 KB/sec 3 KB/sec 66 KB/sec 500
Port: 80: 229 KB/sec 9 KB/sec 242 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

ISP is att&t or sbcglobal.net

Ever since the emergency shutdown of the server on Friday the launcher crashes when trying to patch. I did not have any problems with the game before Friday's shutdown.
Ensign
Join Date: Nov 2012
Posts: 5
# 16
02-02-2013, 03:27 PM
Getting this too.

Funny, I take a brake for a couple months, finally get in the mood to come back, then boom...can't get on. Great work lol.
Career Officer
Join Date: Jun 2012
Posts: 6,416
# 17
02-02-2013, 08:29 PM
Its worse than it was in the past few days, its really difficult to do any events.
Commander
Join Date: Jun 2012
Posts: 441
# 18
02-02-2013, 10:35 PM
Okay, first some general stuff:

It doesn't matter if you can play another game just fine. Unless both games happen to utilize the exact same path to their servers, what's affecting something along the route to STO isn't going to affect another game. Therefore, being able to play another game doesn't mean there isn't a problem along the route.

Think of a traceroute (operative part being "route") as an itinerary for the stops your data makes from your PC to the game server. It allows a user to see what's happening with their data packets along their merry way from point A to point B.

Now...for the individual stuffs:

Quote:
contacting nettest server..
Local IP: REDACTED
Ping: 88.2 msec
Port: 80: 245 KB/sec 9 KB/sec 259 KB/sec 500
Port: 80: 181 KB/sec 9 KB/sec 194 KB/sec 500
Port: 443: 247 KB/sec 10 KB/sec 262 KB/sec 500
Port: 443: 191 KB/sec 9 KB/sec 203 KB/sec 500
Port: 7255: 251 KB/sec 10 KB/sec 266 KB/sec 500
Port: 7255: 466 KB/sec 19 KB/sec 493 KB/sec 500
Port: 7003: 441 KB/sec 21 KB/sec 467 KB/sec 500
Port: 7003: 479 KB/sec 20 KB/sec 508 KB/sec 500
Port: 7202: 264 KB/sec 11 KB/sec 280 KB/sec 500
Port: 7202: 466 KB/sec 19 KB/sec 493 KB/sec 500
Port: 7499: 170 KB/sec 9 KB/sec 183 KB/sec 500
Port: 7499: 62 KB/sec 3 KB/sec 66 KB/sec 500
Port: 80: 229 KB/sec 9 KB/sec 242 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

ISP is att&t or sbcglobal.net
I've done you the favor of blacking out your local IP from your nettest results. To you and everyone else, remember that your IP is visible in your nettest--remove it or edit it out before posting for your own security!! Anyway...those results are all over the place. Some results are fine, others are abnormal. What you'll want to shoot for is 200 for first and third columns, and 20 for the middle.

Looks like some ports may be throttled back, either by your router or your ISP. Check with your ISP to see if they can work on cleaning that up a bit or at least explaining why those results are varying that much.

Your traceroute looks okay, just some hops are getting a bit high towards the end (100ms+)

Quote:
Here's the tracert from Bucharest, Romania



Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 5 ms 1 ms 192.168.100.1
3 28 ms 5 ms 15 ms adsl92-86-128-129.romtelecom.net [92.86.128.129]

4 37 ms 37 ms 37 ms 10.0.241.205
5 35 ms 35 ms 35 ms 10.0.200.22
6 37 ms 36 ms 36 ms ffm-b7-link.telia.net [213.248.97.89]
7 35 ms 35 ms 35 ms ffm-bb2-link.telia.net [80.91.247.74]
8 36 ms 36 ms 36 ms ffm-b12-link.telia.net [213.155.135.15]
9 37 ms 36 ms 37 ms be100.ccr22.fra03.atlas.cogentco.com [130.117.14
.89]
10 41 ms 43 ms 43 ms te0-0-0-2.ccr21.ams03.atlas.cogentco.com [130.11
7.48.165]
11 56 ms 56 ms 56 ms te0-3-0-2.ccr21.lpl01.atlas.cogentco.com [154.54
.37.94]
12 59 ms 135 ms 119 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.31.189]
13 122 ms 121 ms 122 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 124 ms 125 ms 128 ms 38.111.40.114
15 129 ms 122 ms 120 ms 208.95.185.41
Those last hops are a bit high as well. It appears the bos hub of Cogent is having some issues again.

Quote:
Traccia instradamento verso patchserver.crypticstudios.com [208.95.185.41]
su un massimo di 30 punti di passaggio:

1 40 ms 94 ms 86 ms dsldevice.lan [192.168.1.254]
2 47 ms 47 ms 47 ms static-213-205-16-41.clienti.tiscali.it [213.205.16.41]
3 48 ms 48 ms 48 ms static-94-32-137-177.clienti.tiscali.it [94.32.137.177]
4 48 ms 47 ms 47 ms static-213-205-57-65.clienti.tiscali.it [213.205.57.65]
5 67 ms 67 ms 66 ms static-213-205-57-229.clienti.tiscali.it [213.205.57.229]
6 67 ms 67 ms 66 ms static-213-205-17-61.clienti.tiscali.it [213.205.17.61]
7 79 ms 78 ms 105 ms 94.32.135.145
8 76 ms 75 ms 75 ms ae3-300.trn22.ip4.tinet.net [77.67.82.229]
9 171 ms 171 ms 171 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
10 181 ms 182 ms 193 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 196 ms 180 ms 180 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
12 237 ms 251 ms 253 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 250 ms 245 ms 247 ms 208.95.185.41

Traccia completata.
Traceroute is far more informative than a ping to the same destination. Looks like around hop 9, your latency is quite problematic. As I can see that your latency closer to home is fine, I suspect there may be some transoceanic lag there.

And before you start demanding a refund, understand that ToS states that PWE cannot guarantee access to the service whenever you wish to use it.
****
Lagging, D/Cing, or rubberbanding? Here's some help.

Current ships: A lot. RTR 15 National Championships....and counting
Ensign
Join Date: Aug 2012
Posts: 20
# 19
02-03-2013, 01:39 AM
What was really weird was that the game was lagged on my Klingon character and was working fine on my Fed until log-in queues started showing up. I guess this has more to do with server load due to the 3 year anniversary, which is understandable, its working fine again now. Thanks lewstelamon01, for taking time to review our logs.
Starfleet Veteran
Join Date: Jun 2012
Posts: 582
# 20 Cryptic is Crippltic
02-03-2013, 02:08 AM
It is funny that before they did the emergency reboot, I was able to play through the anniversary mission four times without any problems. The first toon I played aftr the reboot was rubberbanding so bad that it took twice as long to finish and made me walk away from the computer for half a day. The game has not shown any improvement and I think we all are waiting for the eventual meltdown of the server. LTS US player
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 09:23 AM.