My ping is only normal at night.

szymiszymi

Hello.

I was very excited when I heard that FIOS gonna be available in my area. At start it worked fine, but right now I get the worst pings I ever had with any internet. What's funny my ping is only bad when I'm playing games and it is most important for me, because I like to play over the internet. I tried various things, and none of them worked. Guys at customer service are not able to help me either. I'm really dissapointed.

When I try to connect to europe I get pings as high as 220. Of course you can say that's servers issues, distance etc., but how can you explain this? During the day I pick for example Luxembourg - from speedtest.net I get ~100ms, in game I get ~220ms and it goes DOWN at night to ~100ms. What's funny I ping ~100ms to Stockholm whole day which is further away from me. I tried various servers and 2 games to make sure it's not game issue and it's not.

I'm living in USA, but I'm from Europe and I have many long time friends there. I want to play with them, especially when I know it should be working just fine. With TWC I never had problems like this, of course it's shaky by itself, but other than that my ping was always stable and I was always around ~100ms on Europe. Kinda funny the main reason I switched to Verizon is not working at all. I hope anybody can help me with this.

BTW my internet is 73/35 and my TWC was 15/1.

Tracerts:

To LoL Europe East server:

Tracing route to FRAG1N4SVR182 [95.172.70.182]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 9 ms 8 ms L100.NYCMNY-VFTTP-245.verizon-gni.net [70.104.13
5.1]
3 11 ms 14 ms 11 ms G1-14-2-0.NYCMNY-LCR-21.verizon-gni.net [130.81.
217.116]
4 12 ms 9 ms 9 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.151.222]
5 10 ms 9 ms 9 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6 11 ms 15 ms 15 ms TenGigE0-4-4-0.GW8.NYC4.ALTER.NET [152.63.18.202
]
7 138 ms 136 ms 136 ms tinet-gw.customer.alter.net [152.179.72.122]
8 234 ms 224 ms 220 ms xe-0-0-1.fra23.ip4.tinet.net [141.136.110.121]
9 209 ms 210 ms 206 ms internap-gw.ip4.tinet.net [77.67.73.166]
10 * * * Request timed out.

To LoL Europe West server:

Tracing route to 95.172.69.84 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 8 ms 9 ms L100.NYCMNY-VFTTP-245.verizon-gni.net [70.104.13
5.1]
3 10 ms 11 ms 12 ms G1-14-2-0.NYCMNY-LCR-21.verizon-gni.net [130.81.
217.116]
4 11 ms 10 ms 8 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.151.222]
5 11 ms 9 ms 9 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6 17 ms 12 ms 15 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET [152.63.21.69]

7 142 ms 138 ms 132 ms tinet-gw.customer.alter.net [152.179.72.122]
8 267 ms 264 ms 258 ms xe-7-3-2.fra23.ip4.tinet.net [141.136.110.97]
9 214 ms 216 ms 232 ms internap-gw.ip4.tinet.net [77.67.73.166]
10 internap-gw.ip4.tinet.net [77.67.73.166] reports: Destination host unreach
able.

To DOTA 2 Europe West:

Tracing route to 146.66.154.117 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 8 ms 9 ms L100.NYCMNY-VFTTP-245.verizon-gni.net [70.104.13
5.1]
3 9 ms 11 ms 15 ms G1-14-2-0.NYCMNY-LCR-22.verizon-gni.net [130.81.
217.118]
4 9 ms 9 ms 9 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.199.12]
5 12 ms 9 ms 9 ms 0.so-0-0-0.XT2.NYC4.ALTER.NET [152.63.17.21]
6 11 ms 14 ms 12 ms TenGigE0-5-1-0.GW8.NYC4.ALTER.NET [152.63.21.73]

7 136 ms 135 ms 131 ms tinet-gw.customer.alter.net [152.179.72.122]
8 226 ms 217 ms 218 ms xe-10-1-0.fra60.ip4.tinet.net [141.136.109.249]

9 226 ms 229 ms 236 ms valve-gw.ip4.tinet.net [77.67.74.170]
10 228 ms 224 ms 215 ms 146-66-154-227.valve.net [146.66.154.227]
11 * * * Request timed out.

To DOTA 2 Europe East:

Tracing route to 146.66.155.82 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 8 ms 10 ms L100.NYCMNY-VFTTP-245.verizon-gni.net [70.104.13
5.1]
3 14 ms 13 ms 10 ms G1-14-2-0.NYCMNY-LCR-21.verizon-gni.net [130.81.
217.116]
4 9 ms 9 ms 9 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.
102]
5 8 ms 9 ms 9 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6 12 ms 9 ms 9 ms GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.
20.49]
7 68 ms 30 ms 33 ms teliasonera-test.customer.alter.net [157.130.255
.206]
8 35 ms 36 ms 102 ms nyk-bb2-link.telia.net [213.155.130.244]
9 136 ms 133 ms 131 ms ffm-bb2-link.telia.net [213.155.135.62]
10 150 ms 152 ms 152 ms win-bb2-link.telia.net [80.91.246.31]
11 152 ms 157 ms 150 ms win-b4-link.telia.net [213.155.133.77]
12 149 ms 151 ms 152 ms valve-ic-156665-win-b4.c.telia.net [195.12.255.1
86]
13 157 ms 163 ms 157 ms 146.66.155.227
14 * * * Request timed out.

And finally <drumroll> Verizon speed test:

Speed Test for the North East (NY - New York) region

All done! Review your speed test results below or see more details

Your download
speed is

44.303 Mbps

Your upload
speed is

37.397 Mbps

and the second one:

Speed Test for the North East (NY - New York) region

All done! Review your speed test results below or see more details

Your download
speed is

50.42 Mbps

Your upload
speed is

37.178 Mbps

smith6612

Dota 2 and LoL (PC gamer within me waves hi!)

Looks like you're biting an issue with the Inteliquent (Tinet.net) peering router between Verizon and Inteliquent. There's another thread mentioning similar issues with another set of folks who are trying to reach a server that needs to route over that location in New York City. What this means is, while the problem isn't so much Verizon's, it's an issue with how much bandwidth Inteliquent is purchasing from Verizon for peering onto their network. They need to purchase more bandwidth in this case or get a beefier router if it's the problem. If not, it's possible it's a load balancing issue that needs to be corrected in which case that is something both Inteliquent and Verizon must work together on. Some users have noted that by changing your IP address, you get a cleaner route, although not perfect, it's better.

As for Telia, looks like something is in fact up with your route between Verizon's backbone and the Telia peering router. This could very well be what I mentioned above: Either bandwidth constraint between the two partners or a load balancing issue in this case between circuits/routers. Here's a similar trace from my DSL connection:

Tracing route to 146.66.155.82 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.3.1
2 7 ms 7 ms 6 ms 10.41.15.1
3 7 ms 6 ms 7 ms P1-0.BFLONY-LCR-02.verizon-gni.net [130.81.195.222]
4 19 ms 19 ms 43 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
5 19 ms 18 ms 18 ms 0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
6 19 ms 19 ms 18 ms GigabitEthernet5-0-0.GW1.NYC4.ALTER.NET [152.63.20.101]
7 19 ms 19 ms 18 ms teliasonera-test.customer.alter.net [157.130.255.206]
8 20 ms 19 ms 19 ms nyk-bb2-link.telia.net [213.155.130.244]
9 121 ms 122 ms 122 ms ffm-bb2-link.telia.net [213.155.131.148]
10 134 ms 133 ms 133 ms win-bb2-link.telia.net [213.155.133.57]
11 140 ms 140 ms 148 ms win-b4-link.telia.net [213.155.133.77]
12 134 ms 134 ms 172 ms valve-ic-156665-win-b4.c.telia.net [195.12.255.186]
13 140 ms 140 ms 142 ms 146.66.155.227
14 * * * Request timed out.
15 ^C

Obviously much cleaner, it's going over some different interfaces (a factor!) and much cleaner.

Without getting to know what exactly is going on between Verizon and the other bandwidth providers, it's honestly hard to troubleshoot without some reverse traces and aggregated data from multiple connections/IPs.

Now your speed tests do seem a bit low. Make sure you're on a Wired connection while running those as with 75Mbps you might be pushing the capabilities of your Wireless link, and if you could try http://testmy.net/ for some results. Use the server selector at the top and run a test against all four options and then supply some results. Flash tests can be a bit iffy.