[Northeast] Ping fluctuation. Staten Island
Are anyone in the Staten Island, NY having fluctuation on trace route results? My results are inconsistant. At my parents home in the bronx, I get a consistent 6ms on the first hop. I am directly wired to the Actiontec Rev. I router. FIOS install was done in Sep 2012 but before I moved in to the home so unable to have a baseline.
You can see there is inconsistency even between your computer and the router. A few things can cause this... Heavy network activity, a malfunctioning router, a bad cable, or the computer is using wireless connection even though a wired connection is available. I've seen some cases where the wifi connection is given a higher priority than the ethernet connection in the computer's networking settings. In such a case, the computer will use wifi even when a wired connection is available. If I had to guess, though, the most likely scenarios are heavy network activity or a malfunctioning router. I'd make sure nobody else on your network is active when doing a test. Perhaps reset the router to the defaults to make sure the settings are good. Are you sure nobody is leeching your wireless? The default FiOS WEP keys aren't very secure.
|reply to revned |
I'm getting same kind of a problem for the last couple of weeks, especially at the evening.
|reply to yyonline |
I have upgraded the router firmware to the latest version. Also changed the cables and tested when no one is using the router. As for the Wifi, it is using WPA2 as the encryption. I'm hoping it is a malfunctioning router so I can just get verizon to swap it. Below are the ping and trace results to google from my parents home in the bronx which is about 30 miles north of staten island.
Ping has started
PING google.com (184.108.40.206): 56 data bytes
64 bytes from 220.127.116.11: icmp_seq=0 ttl=252 time=5.702 ms
64 bytes from 18.104.22.168: icmp_seq=1 ttl=252 time=6.858 ms
64 bytes from 22.214.171.124: icmp_seq=2 ttl=252 time=5.545 ms
64 bytes from 126.96.36.199: icmp_seq=3 ttl=252 time=7.502 ms
64 bytes from 188.8.131.52: icmp_seq=4 ttl=252 time=6.621 ms
64 bytes from 184.108.40.206: icmp_seq=5 ttl=252 time=6.793 ms
64 bytes from 220.127.116.11: icmp_seq=6 ttl=252 time=7.609 ms
64 bytes from 18.104.22.168: icmp_seq=7 ttl=252 time=8.349 ms
64 bytes from 22.214.171.124: icmp_seq=8 ttl=252 time=5.149 ms
64 bytes from 126.96.36.199: icmp_seq=9 ttl=252 time=5.234 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.149/6.536/8.349/1.041 ms
Traceroute has started
traceroute: Warning: google.com has multiple addresses; using 188.8.131.52
traceroute to google.com (184.108.40.206), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 1.437 ms 1.103 ms 1.187 ms
2 l100.nycmny-vfttp-169.verizon-gni.net (220.127.116.11) 2.844 ms 2.444 ms 2.591 ms
3 g1-5-1-5.nycmny-lcr-21.verizon-gni.net (18.104.22.168) 4.676 ms 6.850 ms 8.560 ms
4 so-11-0-0-0.ny325-bb-rtr1.verizon-gni.net (22.214.171.124) 4.889 ms 5.324 ms 5.007 ms
5 0.xe-4-1-0.xt2.nyc4.alter.net (126.96.36.199) 6.468 ms 6.050 ms 5.572 ms
6 tengige0-5-2-0.gw8.nyc4.alter.net (188.8.131.52) 9.069 ms
tengige0-7-4-0.gw8.nyc4.alter.net (184.108.40.206) 13.570 ms
tengige0-7-1-0.gw8.nyc4.alter.net (220.127.116.11) 9.552 ms
7 google-gw.customer.alter.net (18.104.22.168) 23.585 ms 24.387 ms 24.749 ms
8 22.214.171.124 (126.96.36.199) 6.842 ms 10.187 ms 107.621 ms
9 188.8.131.52 (184.108.40.206) 7.214 ms 11.331 ms 7.767 ms
10 lga15s29-in-f2.1e100.net (220.127.116.11) 7.084 ms 6.470 ms 5.937 ms
|reply to Dmitriy5 |
Have you contacted verizon about it yet? That would be my next step, but wanted the community input before I do so that I cover all bases before I speak to a tech.
I'll do trace and show you how it looks from my site.
Fountain Valley, CA
the original poster has problems in the house between his pc and the router.
If you are hardwired, change out that cable, or try a different port on the router.
if you are wireless, I would start changing those wifi channels in a hurry
|reply to revned |
@revned - Do you have a wireless connection on the computer you're testing from? If so, disable it to make sure you're using wired connection and post some fresh tracert results. If you're not sure, post the results of running the command "route print" from the command line. This will show the metrics of each connection.
The results from your parents house mean little here, unfortunately... Different central office, different edge routers, it's even pinging a different google server.
|reply to revned |
First Off. Thank you for the troubleshooting steps everyone!
1- I am on a wired connection and also turned off wireless on the router before running these tests. I have replaced the ethernet cables and turned off any devices such as STBs.
2- I have tried different computers and the results are the same.
3- I also received a brand new router from verizon. The tech ran signal tests on his end and they are within range. The tech determined it is the router. BUT I am still getting the same results.
4- I am thinking it may be the coaxial cable from the ONT to the router. The connection between the ONT to the router at my parents house is ethernet as suppose to the standard coaxial cable.
This is the tracert results from the new router I received from Verizon.
Tracing route to google.com [18.104.22.168]
over a maximum of 30 hops:
1 17 ms 3 ms 29 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 10 ms 8 ms L100.NYCMNY-VFTTP-133.verizon-gni.net [98.113.42
3 11 ms 12 ms 11 ms G0-1-1-5.NYCMNY-LCR-21.verizon-gni.net [130.81.1
4 9 ms 9 ms 10 ms 22.214.171.124
5 12 ms 13 ms 13 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [126.96.36.199]
6 13 ms 15 ms 12 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET [188.8.131.52]
7 66 ms 67 ms 66 ms google-gw.customer.alter.net [184.108.40.206]
8 19 ms 15 ms 13 ms 220.127.116.11
9 38 ms 18 ms 14 ms 18.104.22.168
10 12 ms 13 ms 10 ms lga15s35-in-f6.1e100.net [22.214.171.124]
Route Print Results
20...00 ff f6 d9 1f fa ......TAP-Win32 Adapter V9
13...00 1f e2 5d 5d 4e ......Realtek RTL8168B/8111B Family PCI-E Gigabit Ethe
et NIC (NDIS 6.20) #2
11...00 1f e2 5d 5d 4f ......Realtek RTL8168B/8111B Family PCI-E Gigabit Ethe
et NIC (NDIS 6.20)
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
IPv4 Route Table
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.3 200
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.3 356
192.168.1.3 255.255.255.255 On-link 192.168.1.3 356
192.168.1.255 255.255.255.255 On-link 192.168.1.3 356
126.96.36.199 240.0.0.0 On-link 127.0.0.1 306
188.8.131.52 240.0.0.0 On-link 192.168.1.3 356
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.3 356
IPv6 Route Table
If Metric Network Destination Gateway
15 58 ::/0 On-link
1 306 ::1/128 On-link
15 58 2001::/32 On-link
15 306 2001:0:4137:9e76:3462:2a59:9d8e:d53b/128
11 276 fe80::/64 On-link
15 306 fe80::/64 On-link
15 306 fe80::3462:2a59:9d8e:d53b/128
11 276 fe80::a4e7:2378:8428:fcaf/128
1 306 ff00::/8 On-link
15 306 ff00::/8 On-link
11 276 ff00::/8 On-link
Those results definitely show a problem between your computer and the router. It's either a hardware issue, or some excessive amount of traffic on your network is overloading the router.
Let's try this test to see if it's a traffic problem or a hardware problem. Disconnect the COAX cable from the router, but leave the computer plugged in to the router. You will have network access, but no internet access. Therefore, no internet traffic. Once the COAX is disconnected, run this command from command prompt:
ping -n 20 192.168.1.1
If those results show good pings (1ms range) with the internet disconnected, it's something on your network causing excessive internet traffic. Check for viruses, spyware, rogue file sharing programs, neighbors stealing your wifi, etc.
If the results show bad pings, it's definitely a hardware problem. Bad network card in your computer, bad cable, bad router...it's odd that this persists after changing it. You're not using some oddly long 500 foot cable or anything strange like that, are you?
Did you get a new power supply (power cord) with the new router? Did you use the new power supply, or just plugged in the old one? Routers do all sorts of bizarre things when the power supplies are going bad.