JCF2
@verizon.net | Lots of page loading time outs. (looks like DNS time outs)
I seem to be getting lots of time outs when loading websites. Browser likes to get stuck at "looking up domain" and then nothing.
It takes a while for it to get through if it ever does. It seems to rarely the last week. |
|
darcilicious
Cyber Librarian
Premium
join:2001-01-02
Forest Grove, OR
1 edit | I prefer »www.opendns.com for all my DNS needs... |
|
Leem
join:2003-11-01
Glen Rock, NJ
| reply to JCF2
Look at the other posts, such as packet loss etc, its been a problem with Verizon for at least a week now and is steadily getting worse, heres my latest smoke and its clearly showing that things are getting worse, not better.
»/r3/smokeping.···65d07.NY |
|
itdood
join:2008-02-07
Harleysville, PA
 ·Verizon FIOS
| something is up abuse-wise. I get the feeling that some providers are filtering 96.227 /11 addresses due to excessive bandwidth. I've been having issues for the past 12 days or so, packets dying after 5th or 6th hop in certain networks.
growing pains for FIOS, people getting these fat pipes and hitting them hard. It ends up affecting entire sub-nets when backbone providers starting filtering out the abusers. |
|
Leem
join:2003-11-01
Glen Rock, NJ | I'm not in the 96 block but I still have the same issues, so I don't think thats the answer :/ |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| Ok, so you were already tracking this issue over here. Let me say again - DNS lookup timeouts have NOTHING to do with the latency monitor spikes. That is a problem with the cogentco provider and is not related to Verizon or nameserver lookup times at all.
May I suggest you find out your nameserver IP(s) that you are using, and run my ns_bench program to test their response time, and post the results here? Maybe run it a few times and paste the results from all of the runs.
»SBC DSL FAQ »How do I test DNS lookup latency with ns_bench?
--
Hello...is there anybody in there? |
|
JCF2
@verizon.net
| reply to JCF2
Yeah i'm definitely getting time outs along my tracert.
Speed in general doesnt seem to hot either. Although i can get 30Mb a sec downloads on speakeasy's washington DC speed test. I can not connect to any of their other speedtests... including the new york one, and i'm in NY.
My IP is in the 72.68.xxx.xxx range.
Things do seem screwy. |
|
Dwindle
join:2008-03-06
| Just to give you an idea...
I've been trying to get to www.arin.net and the dns lookup failed over and over and over... now finally it went through and i tracert'd it.
Tracing route to www.arin.net [192.149.252.7]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 4 ms 4 ms 10.32.63.5
3 4 ms 4 ms 4 ms P0-0.LCR-03.NYCMNY.verizon-gni.net [130.81.38.116]
4 4 ms 4 ms 4 ms 130.81.29.200
5 6 ms 7 ms 7 ms 0.so-4-2-0.XT1.NYC8.ALTER.NET [152.63.10.1]
6 8 ms 7 ms 7 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
7 6 ms 7 ms 7 ms 0.ge-6-1-0.BR3.NYC4.ALTER.NET [152.63.3.166]
8 6 ms 7 ms 7 ms sl-crs2-nyc-0-1-2-0.sprintlink.net [144.232.18.237]
9 8 ms 7 ms 7 ms sl-crs1-nyc-0-0-0-1.sprintlink.net [144.232.13.42]
10 15 ms 14 ms 13 ms sl-bb23-pen-4-0-0.sprintlink.net [144.232.20.123]
11 13 ms 14 ms 13 ms sl-bb24-pen-9-0.sprintlink.net [144.232.16.66]
12 14 ms 13 ms 13 ms sl-bb20-rly-15-0-0.sprintlink.net [144.232.20.145]
13 20 ms 20 ms 19 ms sl-gw6-rly-0-0.sprintlink.net [144.232.25.245]
14 21 ms 21 ms 22 ms sl-ameri94-2-0.sprintlink.net [160.81.38.126]
15 24 ms 21 ms 22 ms host-252-131.arin.net [192.149.252.131]
16 20 ms 21 ms 22 ms host-252-7.arin.net [192.149.252.7]
Before i tracedrt to news.easynews.com (a place where i get 30Mb a second easily downloading, and today i get 5.2Mb
Tracing route to news.easynews.com [140.99.99.130]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 4 ms 10.32.63.5
3 6 ms 5 ms 4 ms P0-0.LCR-04.NYCMNY.verizon-gni.net [130.81.38.148]
4 7 ms 7 ms 6 ms 130.81.17.215
5 134 ms 172 ms 206 ms 130.81.14.42
6 7 ms 6 ms 6 ms 69.31.95.158
7 15 ms 11 ms 11 ms 69.22.142.17
8 12 ms 11 ms 12 ms xe-2-1-0.cr1.iad1.us.nlayer.net [69.31.31.153]
9 61 ms 29 ms 28 ms xe-1-1-0.cr1.atl1.us.nlayer.net [69.22.142.50]
10 33 ms 29 ms 28 ms 216.246.113.18
11 29 ms 31 ms 29 ms unknown.hwng.net [69.16.190.33]
12 67 ms 67 ms 67 ms 1-1.r1.ph.hwng.net [69.16.191.70]
13 65 ms 64 ms 67 ms 69.16.190.166
14 66 ms 65 ms 67 ms 69.16.128.130
15 67 ms 66 ms 69 ms 69.16.128.37
16 68 ms 67 ms 67 ms 69.16.128.53
17 68 ms 66 ms 67 ms 140.99.99.130
I tracert'ed Flickr.com because it seemed to be taking a bit to look up the dns and load the page...
Tracing route to www.flickr.vip.mud.yahoo.com [68.142.214.24]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms 10.32.63.5
3 5 ms 4 ms 4 ms P0-0.LCR-04.NYCMNY.verizon-gni.net [130.81.38.148]
4 14 ms 15 ms 13 ms so-7-0-0-0.ASH-PEER-RTR2.verizon-gni.net [130.81.17.179]
5 15 ms 19 ms 19 ms 130.81.15.170
6 70 ms 69 ms 69 ms 216.115.101.145
7 94 ms 69 ms 69 ms 216.115.96.60
8 70 ms 69 ms 74 ms UNKNOWN-216-115-102-139.yahoo.com [216.115.102.139]
9 70 ms 69 ms 69 ms ge-1-1-0-p101.msr1.mud.yahoo.com [216.115.104.107]
10 69 ms 74 ms 69 ms bas4.v206.mud.yahoo.com [68.142.209.11]
11 85 ms 69 ms 69 ms www.flickr.vip.mud.yahoo.com [68.142.214.24]
AND the finally. I cant get to www.microsoft.com in my browser and I cant tracert it... cant resolve the name.
I have these problems a lot this week. Lots of look up errors. Seems like there is some lag within the root some where
OK... its now tracing www.microsoft.com...
BTW in my browser.. it finally found microsoft.com but it takes a while to dl the page. Infact it jsut dl'd it broken and screwed up  Ah a refresh fixed it and it loaded fast. Fios is being very wierd
The trace is looking interesting... lots of time outs, and poor timings and other great nonsense
Tracing route to lb1.www.ms.akadns.net [207.46.192.254]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms 10.32.63.5
3 5 ms 4 ms 4 ms P0-0.LCR-04.NYCMNY.verizon-gni.net [130.81.38.148]
4 14 ms 14 ms 14 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]
5 13 ms 13 ms 14 ms 130.81.15.30
6 15 ms 14 ms 14 ms 207.46.47.92
7 14 ms 14 ms 14 ms ge-7-0-0-0.ash-64cb-1b.ntwk.msn.net [207.46.41.46]
8 96 ms 96 ms 97 ms 207.46.34.165
9 96 ms 96 ms 97 ms 207.46.34.122
10 97 ms 98 ms 97 ms 207.46.35.33
11 97 ms 96 ms 96 ms ten2-4.tuk-76c-1b.ntwk.msn.net [207.46.44.54]
12 97 ms 97 ms 96 ms po15.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.35.138]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * wwwtk2test1.microsoft.com [207.46.192.254] reports: Destination net unreachable.
Trace complete. |
|
Dwindle
join:2008-03-06 | reply to JCF2
Hell getting to google.com is shakey
Btw this is JCF2. |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| reply to Dwindle
I don't see anything wrong with those traceroutes. And the Speakeasy tests are notoriously inaccurate for FiOS, try this test instead:
»msiad.visualware.com/myspeed/
--
Hello...is there anybody in there? |
|
ProFiOSDude
Premium
join:2005-05-27
Chesapeake, VA | reply to Dwindle
Looks like statistics within VZ are good...once you leave, you are getting into problems. Not much they can do about other hops along the way.
PFD |
|
Jonson9688
Bogoman
join:2001-10-22
Little Neck, NY
| reply to JCF2
I've been getting these timeouts too.. but only in the past day or so. At first I thought it was a reaction to uploading constantly, and throttling, because before I uploaded (for friends) files for a 12 hour period, I had no problems. After my uploading though, I can hardly load google... what gives? It was fine up until yesterday.. |
|
More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA | Reboot the Actiontec and see if that makes a differernce. |
|
Jonson9688
Bogoman
join:2001-10-22
Little Neck, NY | I restarted my linksys router... that seems to have made the difference. Thanks =) should've realized the solution was something simple.. |
|
