I honestly don't know what you mean by "trace route results" (Yes, I'm a technology noob). I tried clearing my browsing history to speed things up, so I may not have it. I have Verizon as an internet provider, if that helps. GTP is working fine now.
Trace Route is a command you can do in your windows command prompt that shows where your connection takes you before it gets to where you are going.
The command is "tracert"
Code:
[SIZE="4"][B][U]To use the tracert command in cmd do this.[/U][/B]
1: Click Start
2a: Type in cmd in the search bar(for vista/7)
2b: Click run and type in tracert(for XP)
3a: Right click and select run as administrator(vista/7)
3b: Hit enter(XP)
4: Type in this command in the command prompt tracert www.gtplanet.net
5: Wait
6: Right click and select Mark and then highlight the text from 01 to the end on the tracert results.
7: Hit enter to copy
8: Post here[/SIZE]
If you did it right you will get something like this.
1 2 ms 1 ms <1 ms 192.168.1.1
2 26 ms 25 ms 25 ms 172.18.112.71
3 25 ms 26 ms 25 ms 172.18.93.154
4 25 ms 25 ms 24 ms 172.18.239.14
5 28 ms 26 ms 28 ms 172.18.239.9
6 28 ms 26 ms 27 ms Bundle-Ether10.ken39.Sydney.telstra.net [203.45.17.17]
7 27 ms 36 ms 35 ms Bundle-Ether6.ken-core4.Sydney.telstra.net [203.50.6.145]
8 26 ms 27 ms 28 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50.6.29]
9 26 ms 27 ms 26 ms 203.50.13.114
10 215 ms 218 ms 215 ms i-0-0-2-0.tlot-core01.bx.reach.com [202.84.140.78]
11 170 ms 169 ms 169 ms i-1-1.tlot03.bi.reach.com [202.84.251.234]
12 * * * Request timed out.
13 252 ms 251 ms 251 ms ve16.tsr2.iad1.us.voxel.net [208.122.63.233]
14 259 ms 255 ms 255 ms 0.te1-1.tsr1.phl1.us.voxel.net [173.231.161.37]
15 256 ms 256 ms 258 ms 0.te1-3.tsr1.ewr4.us.voxel.net [173.231.161.57]
16 256 ms 256 ms 256 ms 0.te6-2.tsr1.ewr1.us.voxel.net [173.231.161.41]
17 253 ms 252 ms 261 ms 0.te1-1.tsr1.lga5.us.voxel.net [208.122.44.206]
18 252 ms 253 ms 251 ms 0.ae57.csr2.lga6.us.voxel.net [208.122.44.210]
19 251 ms 251 ms 252 ms server-new.gtplanet.net [72.251.193.205]
My connection has to go through 19 places before it comes to gtplanet.net.
Also try this command
ping 72.251.193.205
Which will give you this.
Pinging 72.251.193.205 with 32 bytes of data:
Reply from 72.251.193.205: bytes=32 time=252ms TTL=47
Reply from 72.251.193.205: bytes=32 time=251ms TTL=47
Reply from 72.251.193.205: bytes=32 time=251ms TTL=47
Reply from 72.251.193.205: bytes=32 time=253ms TTL=47
Ping statistics for 72.251.193.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 253ms, Average = 251ms
This will show your latency(ping or delay) since I am in Australia 250 is normal for me but I have gotten 500 on US based servers before which is high.
