I've actually had no issues over the last 3-4 days.
I played for about 4 hours on Saturday and only dropped 1 packet the entire duration. To me, the issue seems resolved wherever it was.
Same. Haven't had any issues in the past few days.
Scratch that. it's back. Having issues tonight (9/18). Had no issues earlier today, but started getting that customary lag at around 7pm EST.
Tracing route to 199.91.189.20 over a maximum of 30 hops
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 9 ms 9 ms L100.WASHDC-VFTTP-73.verizon-gni.net [72.83.250.1]
3 25 ms 8 ms 11 ms G0-6-4-6.WASHDC-LCR-22.verizon-gni.net [130.81.212.144]
4 11 ms 8 ms 10 ms so-14-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.22.56]
5 14 ms 8 ms 9 ms 0.ae4.XL2.IAD8.ALTER.NET [152.63.8.125]
6 13 ms 9 ms 10 ms 0.xe-11-2-1.GW9.IAD8.ALTER.NET [152.63.42.2]
7 38 ms 39 ms 37 ms tinet-gw.customer.alter.net [152.179.50.30]
8 59 ms 58 ms 59 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 55 ms 57 ms 59 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 * 149 ms 148 ms 192.34.76.2
11 61 ms 57 ms 57 ms 199.91.189.234
12 60 ms 58 ms 58 ms 199.91.189.20
Having an issue at hop 10 obviously. Whois says that IP belongs to Ormuco. Same deal as before, others aren't experiencing this lag. I've been lag-free for the past few days, not sure what's changed.
For me it seems it's directly related to the tinet-gw.customer.alter.net (152.179.50.30 in my tracert) router. I've done some research and FiOS users have been reporting issues with traffic directed through that router since January, at least. This router is in Ashburn, VA, and is controlled by Verizon Business, formerly Alter.net.
A quote from the info I've found: "These traceroutes were done from different locations to kinda pinpoint the issue, but you can clearly see that as long as it doesn't touch the tinet-gw.customer.alter.net router there is no latency present."
edit: sources http://forums.verizon.com/t5/FiOS-Internet/Routing-Latency-issues/td-p/525091
http://whois.net/ip-address-lookup/152.179.50.30
Lag went away last weekend, but has come back during this week.
Still pretty much the same exact lag.
same issue here with the tinet
Even though im out of pittsburgh.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 10 ms 4 ms L100.PITBPA-VFTTP-24.verizon-gni.net [96.236.155
.1]
3 6 ms 7 ms 7 ms G0-1-1-7.PITBPA-LCR-22.verizon-gni.net [130.81.6
0.138]
4 33 ms 11 ms 14 ms xe-1-1-1-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
209.18]
5 20 ms 19 ms 18 ms 0.xe-11-1-1.XL2.IAD8.ALTER.NET [152.63.5.249]
6 18 ms 19 ms 18 ms 0.xe-11-2-1.GW9.IAD8.ALTER.NET [152.63.42.2]
7 * * * Request timed out.
8 70 ms 71 ms * xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 70 ms 71 ms 71 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 66 ms 67 ms 67 ms 192.34.76.2
11 68 ms 68 ms 67 ms 199.91.189.234
12 69 ms 70 ms 67 ms 199.91.189.20
Trace complete.
Continuing to have issues as well.
WinMTR Statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| Wireless_Broadband_Router.home | 0 | 150 | 150 | 0 | 0 | 1 | 0 |
| L100.BLTMMD-VFTTP-52.verizon-gni.net | 0 | 150 | 150 | 5 | 6 | 9 | 6 |
| G5-0-352.BLTMMD-LCR-03.verizon-gni.net | 0 | 150 | 150 | 5 | 6 | 9 | 6 |
| so-9-0-2-0.RES-BB-RTR1.verizon-gni.net | 0 | 150 | 150 | 7 | 18 | 100 | 9 |
| 0.ae5.XL1.IAD8.ALTER.NET | 24 | 113 | 87 | 8 | 10 | 20 | 9 |
| 0.xe-10-1-1.GW9.IAD8.ALTER.NET | 0 | 150 | 150 | 8 | 11 | 74 | 10 |
| tinet-gw.customer.alter.net | 13 | 126 | 110 | 13 | 15 | 34 | 14 |
| xe-1-0-0.mtl10.ip4.tinet.net | 0 | 150 | 150 | 24 | 30 | 92 | 27 |
| ormuco-gw.ip4.tinet.net | 0 | 150 | 150 | 40 | 43 | 58 | 42 |
| 192.34.76.2 | 0 | 150 | 150 | 40 | 45 | 112 | 44 |
| 199.91.189.234 | 0 | 150 | 150 | 43 | 44 | 66 | 43 |
| 199.91.189.30 | 0 | 150 | 150 | 42 | 44 | 62 | 44 |
Lag continues. Below is the trace route taken around 6:50pm EDT on 10/11/2013.
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| Wireless_Broadband_Router.home | 0 | 500 | 500 | 0 | 0 | 1 | 0 |
| L100.BLTMMD-VFTTP-52.verizon-gni.net | 0 | 500 | 500 | 5 | 7 | 114 | 7 |
| G5-0-352.BLTMMD-LCR-03.verizon-gni.net | 0 | 500 | 500 | 5 | 7 | 118 | 7 |
| so-9-0-2-0.RES-BB-RTR1.verizon-gni.net | 0 | 500 | 500 | 7 | 18 | 176 | 99 |
| 0.ae5.XL1.IAD8.ALTER.NET | 3 | 457 | 446 | 7 | 10 | 48 | 42 |
| 0.xe-10-1-1.GW9.IAD8.ALTER.NET | 0 | 500 | 500 | 7 | 11 | 123 | 12 |
| tinet-gw.customer.alter.net | 5 | 421 | 401 | 15 | 19 | 97 | 17 |
| xe-1-0-0.mtl10.ip4.tinet.net | 0 | 500 | 500 | 25 | 37 | 184 | 37 |
| ormuco-gw.ip4.tinet.net | 0 | 500 | 500 | 42 | 45 | 148 | 43 |
| 192.34.76.2 | 0 | 500 | 500 | 42 | 46 | 147 | 45 |
| 199.91.189.234 | 1 | 496 | 495 | 40 | 45 | 170 | 41 |
| 199.91.189.30 | 0 | 500 | 500 | 40 | 43 | 147 | 41 |
Still having ALTER.NET issues...
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| Wireless_Broadband_Router.home | 0 | 1000 | 1000 | 0 | 0 | 1 | 0 |
| L100.BLTMMD-VFTTP-52.verizon-gni.net | 0 | 1000 | 1000 | 5 | 7 | 35 | 7 |
| G0-7-2-4.BLTMMD-LCR-21.verizon-gni.net | 0 | 1000 | 1000 | 5 | 9 | 25 | 10 |
| so-1-1-0-0.RES-BB-RTR1.verizon-gni.net | 1 | 996 | 995 | 7 | 12 | 100 | 10 |
| 0.ae5.XL1.IAD8.ALTER.NET | 7 | 804 | 755 | 0 | 15 | 58 | 15 |
| 0.xe-8-1-0.GW9.IAD8.ALTER.NET | 1 | 996 | 995 | 7 | 11 | 77 | 10 |
| tinet-gw.customer.alter.net | 2 | 944 | 930 | 8 | 11 | 65 | 12 |
| xe-4-0-0.mtl10.ip4.tinet.net | 0 | 1000 | 1000 | 25 | 36 | 143 | 93 |
| ormuco-gw.ip4.tinet.net | 1 | 996 | 995 | 37 | 41 | 49 | 39 |
| 192.34.76.2 | 1 | 996 | 995 | 37 | 43 | 105 | 40 |
| 199.91.189.234 | 1 | 996 | 995 | 42 | 45 | 67 | 47 |
| 199.91.189.30 | 1 | 996 | 995 | 37 | 41 | 50 | 43 |
Other players have posted traceroutes showing their traffic meeting up on tinet.net before reaching SE's network. C'mon Verizon, fix your stuff!
Bringing this topic back to the top as it's a prevalent problem since around Mid-December:
Tracing route to 199.91.189.57 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 116 ms 7 ms 8 ms L100.NYCMNY-VFTTP-116.verizon-gni.net [173.68.109.1]
3 12 ms 12 ms 9 ms G1-15-0-4.NYCMNY-LCR-21.verizon-gni.net [100.41.192.118]
4 48 ms 6 ms 7 ms ae5-0.NY325-BB-RTR1.verizon-gni.net [130.81.163.208]
5 10 ms 9 ms 10 ms 0.xe-4-0-0.BR3.NYC4.ALTER.NET [152.63.23.173]
6 26 ms 27 ms 27 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
7 34 ms 32 ms 32 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 32 ms 32 ms 32 ms 4.69.201.37
9 33 ms 32 ms 32 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 141 ms 211 ms 212 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 37 ms 34 ms 35 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 37 ms 37 ms 81 ms 192.34.76.10
13 34 ms 34 ms 34 ms 199.91.189.242
14 35 ms 31 ms 32 ms 199.91.189.57
Trace complete.
That 10th hop varies if it comes back at all.
Start a new topic or ask questions in the open forum.
