- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting wierd latency problems around 12am to 9am. Its been happening for 2 weeks now and its quite annoying for any latency sensitive applications like gaming and such.
A good example is when im pinging google I get these results
Pinging google.com [66.249.81.104] with 32 bytes of data:
Reply from 66.249.81.104: bytes=32 time=354ms TTL=48
Reply from 66.249.81.104: bytes=32 time=155ms TTL=48
Reply from 66.249.81.104: bytes=32 time=50ms TTL=48
Reply from 66.249.81.104: bytes=32 time=46ms TTL=48
Ping statistics for 66.249.81.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 354ms, Average = 151ms
Like i mention before I just get these unstable latency bewteen that time, after that it becomes normal for the rest of the day. Any Idea why?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, pings are a good start. They tell you that there is a problem, but not where the problem is. The next thing you need is a trace route. This will give us a good idea where the problem is.
The next time the pings go high like that, run this from the command prompt and post the results
tracert www.google.com
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is normally between 9am to 12am:
Tracing route to google.com [66.249.90.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.0.1]
2 10 ms 9 ms 10 ms L100.NWRKNJ-VFTTP-121.verizon-gni.net [98.109.8
1]
3 12 ms 9 ms 10 ms 4-0-6-1721.NWRKNJ-LCR-07.verizon-gni.net [130.8
.131.128]
4 9 ms 17 ms 19 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81
29.8]
5 18 ms 19 ms 19 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.
1.17.6]
6 18 ms 29 ms 19 ms 0.xe-8-0-0.BR2.NYC4.ALTER.NET [152.63.3.130]
7 19 ms 13 ms 12 ms xe-10-2-0.edge2.NewYork2.level3.net [4.68.110.2
3]
8 23 ms 19 ms 18 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 27 ms 19 ms 19 ms ae-6-6.ebr4.NewYork1.Level3.net [4.69.141.21]
10 26 ms 14 ms 24 ms ae-64-64.csw1.NewYork1.Level3.net [4.69.134.114
11 23 ms 49 ms 19 ms ae-1-69.edge1.NewYork1.Level3.net [4.68.16.14]
12 21 ms 18 ms 19 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.
2]
13 31 ms 17 ms 12 ms 72.14.238.232
14 25 ms 19 ms 18 ms 209.85.241.222
15 17 ms 19 ms 19 ms lga15s04-in-f104.1e100.net [66.249.90.104]
Now this is between 12am to 9am:
Tracing route to google.com [66.249.80.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.0.1]
2 555 ms 128 ms 35 ms L100.NWRKNJ-VFTTP-121.verizon-gni.net [98.109.8.
1]
3 72 ms 130 ms 48 ms 4-0-6-1721.NWRKNJ-LCR-07.verizon-gni.net [130.81
.131.128]
4 22 ms 122 ms 132 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
29.8]
5 30 ms 21 ms 28 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 427 ms 675 ms 61 ms 0.xe-7-0-0.BR2.NYC4.ALTER.NET [152.63.3.166]
7 151 ms 362 ms 61 ms 204.255.173.54
8 65 ms 56 ms 72 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 39 ms 60 ms 48 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 137 ms 110 ms 58 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
11 19 ms 50 ms 110 ms ae-4-99.edge1.NewYork1.Level3.net [4.68.16.206]
12 122 ms 622 ms 232 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.8
6]
13 68 ms 16 ms 20 ms 72.14.238.232
14 40 ms 451 ms 377 ms 209.85.241.150
15 24 ms 67 ms 27 ms lga15s03-in-f104.1e100.net [66.249.80.104]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like your problems start right out of the gate there with the Verizon gateway router.
This is one where you want to try. rebooting and resetting the router (not likely to help but never hurts to try).
Reboot the ONT (unplug it and then find the battery unit, open it up and disconnect the quick connect on top. wait about 2 minutes, then plug back into electric. wait until the "replace battery" lights back up and then reconnect the battery). Then go check the internet.
Then if that fails, contact Verizon tech support and provide them with the trace route information to report to the network techs and let them know you rebooted the ONT.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have had similar problems over the last week where I cannot connect to the internet overnight (6PM - 6AM). During the day the connection is fine. I'm a novice when it comes to internet connectivity and do not know anything about pings or tracings. How do I obtain this information? We have a FIOS representative to come out to our house in two days, however I worry they may not be able to fix the problem if they arrive during the day when the internet is working. I also rebooted the ONT with no change. Thanks in advance for your help!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are a windows user:
1. Start/Programs/Accessories/Command Promp.
2. Type in "ping www.google.com > ping-google.txt 2>&1".
3. Type in "notepad ping.google.txt".
4. You can cut&paste results.
5. Type in "tracert www.google.com > tracert-google.txt 2>&1".
6. Type in "notepad tracert-google.txt".
7. You can cut&paste results.
If you are Linux/FreeBSD or other *nix user:
1. Start console.
2. Type in "su - root".
3. Type in "ping www.google.com > ping-google.txt 2>&1".
4. Type in "vi ping.google.txt".
5. You can cut&paste results. When you done type in ":q".
6. Type in "traceroute www.google.com > tracert-google.txt 2>&1".
7. Type in "vi tracert-google.txt".
8. You can cut&paste results.When you done type in ":q".
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jarr96 wrote:This is normally between 9am to 12am:
Tracing route to google.com [66.249.90.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.0.1]
2 10 ms 9 ms 10 ms L100.NWRKNJ-VFTTP-121.verizon-gni.net [98.109.8
1]
Could you provide data from Bandwidth monitoring (Connect tot router, System Monitoring/Bandwith Monitoring) for these hours? Some Information from router logs would also helpful.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is unacceptable. I'm going to call a verizon tech first thing in the morning.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Verizon techs can't seems to understand the difference between bandwidth and latency >_>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content