- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Most websites load real fast (I have FIOS 35/35).
But then there are others that load REAL slow. I am talking ONE MINUTE or MORE
like:
mayoclinic
medlineplus.gov
This problem is over 2 weeks old. Please check into it.
Here are traceroutes for those two respectively
to mayoclinic:
Tracing route to mayoclinic.com [129.176.217.6]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 200 ms 6 ms 6 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1]
3 18 ms 14 ms 17 ms G0-12-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.
184.78]
4 40 ms * 10 ms so-14-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.
22.56]
5 11 ms 9 ms 10 ms 0.xe-1-0-1.BR2.IAD8.ALTER.NET [152.63.39.13]
6 28 ms 56 ms * ae17.edge1.washingtondc12.level3.net [4.68.62.13
7]
7 * * * Request timed out.
8 64 ms 36 ms 69 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
9 61 ms 74 ms 36 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
10 54 ms 46 ms 77 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
11 184 ms * 67 ms ae-4-4.car1.Minneapolis1.Level3.net [4.69.136.10
5]
12 * 75 ms 64 ms MAYO-FOUNDA.car1.Minneapolis1.Level3.net [4.59.6
4.10]
to medlineplus.gov
Tracing route to medlineplus.gov [130.14.16.160]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 72 ms 6 ms 9 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1]
3 8 ms 11 ms 11 ms G0-12-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.
184.78]
4 52 ms * * so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.32]
5 35 ms 21 ms 9 ms 0.xe-3-1-0.BR2.IAD8.ALTER.NET [152.63.38.157]
6 55 ms 23 ms 39 ms ae17.edge1.washingtondc12.level3.net [4.68.62.13
7]
7 * 58 ms 28 ms vl-3503-ve-117.ebr1.Washington12.Level3.net [4.6
9.158.26]
8 30 ms 27 ms 28 ms ae-8-8.ebr1.Washington1.Level3.net [4.69.143.217
]
9 * 62 ms 53 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
10 57 ms * 109 ms ae-4-90.edge3.Washington1.Level3.net [4.69.149.2
09]
11 58 ms 51 ms 53 ms NATIONAL-LI.edge3.Washington1.Level3.net [4.59.1
44.190]
12 * * * Request timed out.
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
and ACTUALLY 200 ms 6 ms 6 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1] Looks pretty bad.
That is your first gateway hop so that should be under 10ms.
you may want to see if you can change your routing. This sometimes works.
Actiontec MI424-WR - RELEASE DHCP
Click on MY NETWORK icon at the top.
Select NETWORK CONNECTIONS from the menu on the left.
Select BROADBAND CONNECTION (coax or ethernet) depending on your connection to the ONT.
Click SETTINGS
Click RELEASE
Click APPLY
Disconnect the router immediately to prevent it from re-requesting a DHCP lease.
wait AT LEAST 5-10 minutes so that your ip can get cycled into the pool, and when you reconnect your router you should get a new ip that is hopefully in a different subnet. it 'might' help.
Compare your ip before and after at www.whatismyip.org
and make sure the first three octets change or are different.
If that doesn't help then for that kind of a problem right at their gateway, it will either self heal or you need to call it in to get the ball rolling.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why not report this to Verizon tech support instead of posting here?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You mean like call them and describe that level 2 or level 3 is having failure? Uhhhh, right!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use open dns, and the traceroutes look good to me, so I don't think it's network related.
If it's hardwired change the dns
if it's wireless you may have to change the wifi channels.
you can change that in the router. open a browser, and go to http://192.168.1.1
user name is admin. and the password is most likely the serial number found on the service tag of your VZ router unless you changed it. Once you login succesfully, go to the top and hit wireless, then on the left basic security. then go to option 3 which is channel 1, 6 and 11 and are the only channels you should try.
So it will likely be set to auto, change it to 11 and put the check for keep settings even after reboot (Directly under the channel) and then hit apply. after you hit apply, test your connection out, if you notice a difference, leave it like that until the problem happens again, and if it happens again, go back into the router, and try channel 6, test it out. and then finally 1 if the first two don't work.
Also take a look at page 2 of Actiontec's Wireless PDF File. It gives you some idea's with regards to position and orientation of where the router sits and how it can best be positioned for maximum coverage.
http://support.actiontec.com/doc_files/MI424WR_Rev(all)_Wireless_Networking_Guide.pdf
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
and ACTUALLY 200 ms 6 ms 6 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1] Looks pretty bad.
That is your first gateway hop so that should be under 10ms.
you may want to see if you can change your routing. This sometimes works.
Actiontec MI424-WR - RELEASE DHCP
Click on MY NETWORK icon at the top.
Select NETWORK CONNECTIONS from the menu on the left.
Select BROADBAND CONNECTION (coax or ethernet) depending on your connection to the ONT.
Click SETTINGS
Click RELEASE
Click APPLY
Disconnect the router immediately to prevent it from re-requesting a DHCP lease.
wait AT LEAST 5-10 minutes so that your ip can get cycled into the pool, and when you reconnect your router you should get a new ip that is hopefully in a different subnet. it 'might' help.
Compare your ip before and after at www.whatismyip.org
and make sure the first three octets change or are different.
If that doesn't help then for that kind of a problem right at their gateway, it will either self heal or you need to call it in to get the ball rolling.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Hubrisnxs,
I reset my IP as instructed. It appears it may be routing (which I suspected). My new IP is a different Class B level IP
Connection does seem much better. Not lightning fast but definitely a massive improvement.
THANKS!
Here is the new traceroute to medlineplus:
Tracing route to medlineplus.gov [130.14.16.160]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 7 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1]
3 16 ms 24 ms 14 ms G0-12-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.
184.78]
4 41 ms * 36 ms so-14-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.
22.56]
5 37 ms * * 0.xe-5-1-0.BR2.IAD8.ALTER.NET [152.63.38.161]
6 23 ms 21 ms 22 ms ae17.edge1.washingtondc12.level3.net [4.68.62.13
7]
7 27 ms 26 ms 26 ms vl-3502-ve-116.ebr1.Washington12.Level3.net [4.6
9.158.22]
8 * 56 ms * ae-8-8.ebr1.Washington1.Level3.net [4.69.143.217
]
9 47 ms 54 ms 51 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
10 27 ms 84 ms 25 ms ae-1-60.edge3.Washington1.Level3.net [4.69.149.1
7]
11 27 ms 26 ms 26 ms NATIONAL-LI.edge3.Washington1.Level3.net [4.59.1
44.190]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well I am glad that it helped, but it's strange because almost all the numbers in your traceroute look the same, except the first hop is performing better.
maybe it was a glitch in the matrix, at any rate. glad it helped
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
actually it took a slightly different level 3 path, but the verizon path where I first noticed the bad ms, stayed the same. so wierd, but hey - the proof is in the pudding I guess.
🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Like I said it wasn't as fast as most websites for the two indicated, but it was markedly improved. Still issues there though I think.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your path through verizon-gni.net in Washington DC is still shoddy, so you'll need to get someone in Verizon to fix this. I don't think changing your IP is a suitable fix here besides having a workaround to go by. This may also be related to all of the other issues folks are seeing in the Northeast.