An Accepted Solution is available for this post.
High Ping with new Fios service
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I recently got fios installed in a new apartment. The speeds seem accurate (50/25) but the latency is bad. I ping 130 to 64.7.194.1, whereas all my friends and family in the area (east coast) ping somewhere between 80 and 90. I also ping 80-90 to this server with the very same computer in several locations, anywhere from 1 to 15 miles away from my current one. I am wondering if this is bad routing on verizon's behalf, too little bandwidth on the part of certain servers, or a router issue? I absolutely need latency to be normal again...
Here is my tracert and pingtesting:
tracert 64.7.194.1
Tracing route to border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 22 ms 17 ms 16 ms L100.BSTNMA-VFTTP-87.verizon-gni.net [98.118.119
.1]
3 21 ms 21 ms 25 ms G0-10-2-5.BSTNMA-LCR-21.verizon-gni.net [130.81.
104.50]
4 7 ms 10 ms 9 ms ae0-0.BOS-BB-RTR1.verizon-gni.net [130.81.209.86
]
5 87 ms 82 ms 82 ms 0.xe-2-0-0.XL3.LAX15.ALTER.NET [152.63.2.66]
6 82 ms 81 ms 82 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
7 123 ms 129 ms 131 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
8 126 ms 122 ms 130 ms border1.te9-3.riotgames-55.lax010.pnap.net [64.7
.194.1]
Reply from 64.7.194.1: bytes=32 time=136ms TTL=252
Reply from 64.7.194.1: bytes=32 time=113ms TTL=252
Reply from 64.7.194.1: bytes=32 time=129ms TTL=252
Reply from 64.7.194.1: bytes=32 time=132ms TTL=252
Reply from 64.7.194.1: bytes=32 time=138ms TTL=252
Reply from 64.7.194.1: bytes=32 time=130ms TTL=252
Reply from 64.7.194.1: bytes=32 time=126ms TTL=252
Reply from 64.7.194.1: bytes=32 time=125ms TTL=252
Reply from 64.7.194.1: bytes=32 time=122ms TTL=252
Reply from 64.7.194.1: bytes=32 time=128ms TTL=252
Reply from 64.7.194.1: bytes=32 time=116ms TTL=252
Reply from 64.7.194.1: bytes=32 time=122ms TTL=252
Reply from 64.7.194.1: bytes=32 time=319ms TTL=252
Reply from 64.7.194.1: bytes=32 time=150ms TTL=252
Reply from 64.7.194.1: bytes=32 time=129ms TTL=252
Reply from 64.7.194.1: bytes=32 time=113ms TTL=252
Reply from 64.7.194.1: bytes=32 time=111ms TTL=252
Reply from 64.7.194.1: bytes=32 time=117ms TTL=252
Reply from 64.7.194.1: bytes=32 time=119ms TTL=252
Reply from 64.7.194.1: bytes=32 time=123ms TTL=252
Reply from 64.7.194.1: bytes=32 time=206ms TTL=252
Now here is a tracert and pingtest from my friends' house, about 15 miles from where I live, also using FiOS service (same computer is used):
tracert 64.7.194.1
Tracing route to border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
over a maximum of 30 hops:
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms CISCO15405 [192.168.0.1]
2 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 3 6 ms 6 ms 3 ms L300.BSTNMA-VFTTP-86.verizon-gni.net [98.110.176.1]
4 9 ms 11 ms 8 ms G0-10-3-6.BSTNMA-LCR-22.verizon-gni.net [130.81.212.180]
5 7 ms 8 ms 6 ms ae0-0.BOS-BB-RTR2.verizon-gni.net [130.81.209.94]
6 91 ms 91 ms 91 ms 0.xe-2-0-0.XL4.LAX15.ALTER.NET [152.63.2.86]
7 93 ms 93 ms 93 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8 87 ms 113 ms 89 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
9 90 ms 93 ms * border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
10 88 ms 89 ms 91 ms border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
2 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
4 9 ms 11 ms 8 ms G0-10-3-6.BSTNMA-LCR-22.verizon-gni.net [130.81.212.180]
5 7 ms 8 ms 6 ms ae0-0.BOS-BB-RTR2.verizon-gni.net [130.81.209.94]
6 91 ms 91 ms 91 ms 0.xe-2-0-0.XL4.LAX15.ALTER.NET [152.63.2.86]
7 93 ms 93 ms 93 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8 87 ms 113 ms 89 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
9 90 ms 93 ms * border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
10 88 ms 89 ms 91 ms border1.te9-3.riotgames-55.lax010.pnap.net [64.7.194.1]
Reply from 64.7.194.1: bytes=32 time=81ms TTL=242
Reply from 64.7.194.1: bytes=32 time=79ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=82ms TTL=242
Reply from 64.7.194.1: bytes=32 time=81ms TTL=242
Reply from 64.7.194.1: bytes=32 time=79ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=81ms TTL=242
Reply from 64.7.194.1: bytes=32 time=82ms TTL=242
Reply from 64.7.194.1: bytes=32 time=82ms TTL=242
Reply from 64.7.194.1: bytes=32 time=81ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=79ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
Reply from 64.7.194.1: bytes=32 time=82ms TTL=242
Reply from 64.7.194.1: bytes=32 time=80ms TTL=242
I have called too many times and done everything from opening up ports, DMZ zone, firewall off, resetting router, changing from moca to ethernet, TCP optimizing programs, etc. I have concluded that it is definitely not my computer because I can simply pick my laptop up, move about 3 miles to another house, try the connection there, and find it to be perfect. I hope there is a solution, because if not I might have to move houses.