View Single Post
Career Officer
Join Date: Jun 2012
Posts: 2,074
# 3
10-13-2013, 06:50 AM
Quote:
Originally Posted by cptlankford View Post

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

1 2 ms 2 ms 1 ms homeportal [192.168.1.254]
2 33 ms 28 ms 27 ms 99-26-244-3.lightspeed.gnvlsc.sbcglobal.net [99.
26.244.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 27 ms 28 ms 72.157.40.148
7 43 ms 37 ms 36 ms 12.81.44.58
8 37 ms 36 ms 36 ms 65.83.239.94
9 37 ms 36 ms 36 ms 12.81.34.5
10 48 ms 50 ms 36 ms 12.81.104.175
11 37 ms 44 ms 40 ms 12.81.46.3
12 38 ms 40 ms 38 ms 12.81.56.6
13 37 ms 36 ms 36 ms 12.81.56.15
14 38 ms 38 ms 41 ms 74.175.192.58
15 51 ms 51 ms 50 ms cr2.rlgnc.ip.att.net [12.123.152.110]
16 50 ms 51 ms 51 ms cr1.wswdc.ip.att.net [12.122.3.170]
17 48 ms 48 ms 47 ms gar13.n54ny.ip.att.net [12.122.81.245]
18 88 ms 87 ms 91 ms 192.205.37.106
19 92 ms 93 ms 91 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41
.206]

20 56 ms 54 ms 56 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
21 61 ms 62 ms 62 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
22 62 ms 62 ms 62 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
23 67 ms 70 ms 71 ms 38.111.40.114
24 61 ms 61 ms 64 ms 208.95.185.41

Trace complete.

C:\Windows\system32>

Nettest Results:

contacting nettest server..
Local IP: 99.26.247.0
Ping: 100.0 msec
Port: 80: 370 KB/sec 18 KB/sec 394 KB/sec 500
Port: 80: 630 KB/sec 21 KB/sec 666 KB/sec 500
Port: 443: 590 KB/sec 19 KB/sec 622 KB/sec 500
Port: 443: 672 KB/sec 22 KB/sec 710 KB/sec 500
Port: 7255: 637 KB/sec 20 KB/sec 672 KB/sec 500
Port: 7255: 602 KB/sec 19 KB/sec 635 KB/sec 500
Port: 7003: 578 KB/sec 18 KB/sec 610 KB/sec 500
Port: 7003: 685 KB/sec 22 KB/sec 723 KB/sec 500
Port: 7202: 694 KB/sec 22 KB/sec 733 KB/sec 500
Port: 7202: 574 KB/sec 18 KB/sec 606 KB/sec 500
Port: 7499: 714 KB/sec 23 KB/sec 754 KB/sec 500
Port: 7499: 599 KB/sec 19 KB/sec 634 KB/sec 500
Port: 80: 603 KB/sec 19 KB/sec 637 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

.....
Now assuming that there are no dropped packets, your 'Trace Route' and 'Net Test' statistics are actually pretty good...

Now I haven't had and disconnects from my connection from the Silicon Valley, so we can assume that there is nothing wrong with the STO Servers, and there is a suspicious increase in latency on the gateway between ATT and Cogent which could be a indication of localized network congestion...

Unfortunately, neither 'Net Test' or 'Trace Route' are good tools for diagnosing dropped packets, and since you are having problems, we can assume you are suffering from excessive packet drop somewhere along the route between your ISP and the STO servers.

You could try googling around for a better tool to diagnose packet drop, or you can contact your ISP and ask them to help diagnose a suspected packet drop issue connecting to the STO servers. If your problems are being caused by dropped packets, then this is a ISP issue, and only the ISP can correct the problem. And packet drop issues are usually intermittent in nature, and are usually associated with heavy network traffic load...