Make sure your ISP is not causing the lag. Do a tracert and ping the ip addresses that may timeout during the tracert.
I prefer
pingpath to
tracert
C:\Documents and Settings\Xiuhtecuhtli>pathping 4.2.2.2
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
0 175-Xiuhtecuhtli.null.net[10.5.11.113]
1 10.5.11.3
2 gw-brdr-100.null.net [25.152.81.100]
3 bur-edge-05.inet.qwest.net [67.130.147.69]
4 bur-core-02.inet.qwest.net [205.171.213.118]
5 los-core-02.inet.qwest.net [67.14.22.18]
6 lap-brdr-02.inet.qwest.net [205.171.32.6]
7 te-3-3.car4.LosAngeles1.Level3.net [4.68.63.65]
8 ge-5-1.core1.LosAngeles1.Level3.net [4.68.102.71]
9 vnsc-bak.sys.gtei.net [4.2.2.2]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 175-Xiuhtecuhtli.null.net [10.5.11.
113]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.5.11.3
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% gw-brdr-100.null.net [25.1
52.81.100]
0/ 100 = 0% |
3 46ms 0/ 100 = 0% 0/ 100 = 0% bur-edge-05.inet.qwest.net [67.130
.147.69]
0/ 100 = 0% |
4 49ms 0/ 100 = 0% 0/ 100 = 0% bur-core-02.inet.qwest.net [205.17
1.213.118]
0/ 100 = 0% |
5 49ms 0/ 100 = 0% 0/ 100 = 0% los-core-02.inet.qwest.net [67.14.
22.18]
0/ 100 = 0% |
6 46ms 0/ 100 = 0% 0/ 100 = 0% lap-brdr-02.inet.qwest.net [205.17
1.32.6]
0/ 100 = 0% |
7 45ms 1/ 100 = 1% 1/ 100 =
1% te-3-3.car4.losangeles1.level3.net
[4.68.63.65]
0/ 100 = 0% |
8 41ms 0/ 100 = 0% 0/ 100 = 0% ge-5-1.core1.losangeles1.level3.ne
t [4.68.102.71]
0/ 100 = 0% |
9 41ms 0/ 100 = 0% 0/ 100 = 0% vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.