Lag every day around the same time on the Famfrit server

[Aegeis]

Ok, now I'm in IT, but i do software development and QA, so this is all greek to me. I did a tracert periodically through the night. I had lag issues the entire time. Here are the results:

6:23 PM EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 8 ms 8 ms L100.RCMDVA-VFTTP-23.verizon-gni.net [72.84.246.1]
3 16 ms 16 ms 10 ms G0-6-1-0.RCMDVA-LCR-22.verizon-gni.net [100.41.205.136]
4 15 ms 16 ms 9 ms ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.29.112]
5 28 ms 42 ms 16 ms 0.xe-4-0-1.XL2.IAD8.ALTER.NET [152.63.7.138]
6 11 ms 17 ms 17 ms 0.xe-11-0-1.GW9.IAD8.ALTER.NET [152.63.33.169]
7 13 ms 19 ms 15 ms tinet-gw.customer.alter.net [152.179.50.30]
8 23 ms 28 ms 24 ms xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
9 30 ms 26 ms 26 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 83 ms 30 ms 27 ms 192.34.76.2
11 31 ms 27 ms 28 ms 199.91.189.234
12 30 ms 27 ms 26 ms 199.91.189.39

Trace complete.

7:04 PM EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 8 ms 8 ms L100.RCMDVA-VFTTP-23.verizon-gni.net [72.84.246.1]
3 21 ms 8 ms 11 ms G0-6-1-0.RCMDVA-LCR-22.verizon-gni.net [100.41.205.136]
4 16 ms 17 ms 22 ms ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.29.112]
5 13 ms 23 ms 45 ms 0.xe-4-0-1.XL2.IAD8.ALTER.NET [152.63.7.138]
6 15 ms 17 ms 17 ms 0.xe-11-0-1.GW9.IAD8.ALTER.NET [152.63.33.169]
7 13 ms 17 ms 16 ms tinet-gw.customer.alter.net [152.179.50.30]
8 26 ms 26 ms 26 ms xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
9 29 ms 27 ms 26 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 35 ms 34 ms 35 ms 192.34.76.2
11 35 ms 37 ms 33 ms 199.91.189.234
12 32 ms 28 ms 37 ms 199.91.189.39

Trace complete.

7:26 PM EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 8 ms 8 ms L100.RCMDVA-VFTTP-23.verizon-gni.net [72.84.246.1]
3 15 ms 8 ms 11 ms G0-6-1-0.RCMDVA-LCR-22.verizon-gni.net [100.41.205.136]
4 16 ms 17 ms 17 ms ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.29.112]
5 16 ms 17 ms 17 ms 0.xe-4-0-1.XL2.IAD8.ALTER.NET [152.63.7.138]
6 12 ms 18 ms 17 ms 0.xe-11-0-1.GW9.IAD8.ALTER.NET [152.63.33.169]
7 13 ms 17 ms 17 ms tinet-gw.customer.alter.net [152.179.50.30]
8 53 ms 42 ms * xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
9 46 ms 46 ms 45 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 40 ms 45 ms 45 ms 192.34.76.2
11 39 ms 45 ms 45 ms 199.91.189.234
12 41 ms 42 ms 46 ms 199.91.189.39

Trace complete.
8:09 PM EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 7 ms 8 ms L100.RCMDVA-VFTTP-23.verizon-gni.net [72.84.246.1]
3 18 ms 15 ms 7 ms G0-6-1-0.RCMDVA-LCR-22.verizon-gni.net [100.41.205.136]
4 63 ms 15 ms 17 ms ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.29.112]
5 14 ms 17 ms 17 ms 0.xe-4-0-1.XL2.IAD8.ALTER.NET [152.63.7.138]
6 13 ms 17 ms 17 ms 0.xe-11-0-1.GW9.IAD8.ALTER.NET [152.63.33.169]
7 13 ms 17 ms 20 ms tinet-gw.customer.alter.net [152.179.50.30]
8 58 ms 66 ms 64 ms xe-8-3-0.mtl10.ip4.gtt.net [141.136.105.74]
9 56 ms 63 ms 66 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 57 ms 57 ms 65 ms 192.34.76.2
11 61 ms 63 ms 62 ms 199.91.189.234
12 60 ms 65 ms 65 ms 199.91.189.39

Trace complete.

9:28 PM EST

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 7 ms 8 ms L100.RCMDVA-VFTTP-23.verizon-gni.net [72.84.246.1]
3 10 ms 7 ms 11 ms G0-6-1-0.RCMDVA-LCR-22.verizon-gni.net [100.41.205.136]
4 20 ms 79 ms 72 ms ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.29.112]
5 14 ms 17 ms 17 ms 0.xe-4-0-1.XL2.IAD8.ALTER.NET [152.63.7.138]
6 16 ms 17 ms 17 ms 0.xe-11-0-1.GW9.IAD8.ALTER.NET [152.63.33.169]
7 17 ms 18 ms 17 ms tinet-gw.customer.alter.net [152.179.50.30]
8 44 ms 44 ms 45 ms xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
9 41 ms 44 ms 46 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 42 ms 44 ms 45 ms 192.34.76.2
11 41 ms 43 ms 44 ms 199.91.189.234
12 * 46 ms 44 ms 199.91.189.39

Trace complete.

Now is this good or bad? I have no idea.

[Aegeis]

Bumping due to my prior comment.

[Malzian]

Bumping due to my prior comment.

Your connection seems fairly consistent, very few lost packets if any and only one instance of a very minor increase in transit time, plus 12 hops is pretty good as well. The source of the lag doesn't seem to be coming from the route, at least from what I can tell from this. You should try using PingPlotter to get a real long-term view of what's going on, it's free for about a month to start and really gives a good overview of the entire connection for an extended span of time since, unfortunately, tracert can only give you a result when you actively run it (which might just fall on a moment when you don't have any lag).