Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.Belkin [192.168.2.1]
2 1 ms 1 ms 1 ms 100.75.70.17
3 667 ms 649 ms 799 ms dpc6935160130.direcpc.com [69.35.160.130]
4 747 ms 651 ms 729 ms dpc6935164017.direcpc.com [69.35.164.17]
5 671 ms 717 ms 669 ms tuk-edge-11.inet.qwest.net [63.235.80.137]
6 741 ms 1147 ms 659 ms sjp-brdr-04.inet.qwest.net [67.14.34.38]
7 679 ms 839 ms 840 ms te0-7-0-29.ccr21.sjc03.atlas.cogentco.com [154.5
4.13.193]
8 719 ms 909 ms 659 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
9 692 ms 789 ms 699 ms be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28
.69]
10 919 ms 839 ms 890 ms be2135.mpd22.mci01.atlas.cogentco.com [154.54.6.
34]
11 712 ms 739 ms 1799 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 1664 ms 1089 ms 829 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
.178]
13 947 ms 849 ms 879 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 1242 ms 967 ms 1259 ms 38.111.40.114
15 832 ms 1346 ms 1058 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
this is my trace ill admit some look even for my satelite connection not sure where it lays running other test shortly
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.Belkin [192.168.2.1]
2 1 ms 1 ms 1 ms 100.75.70.17 3 667 ms 649 ms 799 ms dpc6935160130.direcpc.com [69.35.160.130]
4 747 ms 651 ms 729 ms dpc6935164017.direcpc.com [69.35.164.17]
5 671 ms 717 ms 669 ms tuk-edge-11.inet.qwest.net [63.235.80.137]
6 741 ms 1147 ms 659 ms sjp-brdr-04.inet.qwest.net [67.14.34.38]
7 679 ms 839 ms 840 ms te0-7-0-29.ccr21.sjc03.atlas.cogentco.com [154.5
4.13.193]
8 719 ms 909 ms 659 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
9 692 ms 789 ms 699 ms be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28
.69]
10 919 ms 839 ms 890 ms be2135.mpd22.mci01.atlas.cogentco.com [154.54.6.
34]
11 712 ms 739 ms 1799 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 1664 ms 1089 ms 829 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
.178]
13 947 ms 849 ms 879 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 1242 ms 967 ms 1259 ms 38.111.40.114
15 832 ms 1346 ms 1058 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
this is my trace ill admit some look even for my satelite connection not sure where it lays running other test shortly
These are very bad values, and start with the first hop into the Network of your ISP... This is clearly a issue caused by direcpc.com, and you should contact them about this...
This also may be a property of a satellite connection, as Geo-synchonous orbit is 2/3 of the distance to the Moon, and even at the speed of light, increased latency is unavoidable...
These are very bad values, and start with the first hop into the Network of your ISP... This is clearly a issue caused by direcpc.com, and you should contact them about this...
This also may be a property of a satellite connection, as Geo-synchonous orbit is 2/3 of the distance to the Moon, and even at the speed of light, increased latency is unavoidable...
knock on wood i was actually able to log in and do stuff i wanted this morning. so maybe was just bad day to logon
Comments
Now if you could run the 'Net Test' and 'Trace Route' network diagnostics, described in this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155
... and post the results, that would provide clues on what the problem may be...
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Phillip>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.Belkin [192.168.2.1]
2 1 ms 1 ms 1 ms 100.75.70.17
3 667 ms 649 ms 799 ms dpc6935160130.direcpc.com [69.35.160.130]
4 747 ms 651 ms 729 ms dpc6935164017.direcpc.com [69.35.164.17]
5 671 ms 717 ms 669 ms tuk-edge-11.inet.qwest.net [63.235.80.137]
6 741 ms 1147 ms 659 ms sjp-brdr-04.inet.qwest.net [67.14.34.38]
7 679 ms 839 ms 840 ms te0-7-0-29.ccr21.sjc03.atlas.cogentco.com [154.5
4.13.193]
8 719 ms 909 ms 659 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
9 692 ms 789 ms 699 ms be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28
.69]
10 919 ms 839 ms 890 ms be2135.mpd22.mci01.atlas.cogentco.com [154.54.6.
34]
11 712 ms 739 ms 1799 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 1664 ms 1089 ms 829 ms be2139.ccr21.bos01.atlas.cogentco.com [154.54.43
.178]
13 947 ms 849 ms 879 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 1242 ms 967 ms 1259 ms 38.111.40.114
15 832 ms 1346 ms 1058 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
this is my trace ill admit some look even for my satelite connection not sure where it lays running other test shortly
contacting nettest server..
timed out
hit return to exit
These are very bad values, and start with the first hop into the Network of your ISP... This is clearly a issue caused by direcpc.com, and you should contact them about this...
This also may be a property of a satellite connection, as Geo-synchonous orbit is 2/3 of the distance to the Moon, and even at the speed of light, increased latency is unavoidable...
knock on wood i was actually able to log in and do stuff i wanted this morning. so maybe was just bad day to logon