PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
 ·Verizon FiOS
| Southern California Performance Issue? I'm seeing lots of "constipation" (site does not respond then does, on and off) to certain sites, like msnbc.com, barnsandnoble.com, foxnews.com, whitehouse.gov, webmail.aol.com, fidelity.com, etc., whereas other sites are just fine, like cnn.com, nytimes.com, etc. Anybody else seeing this? My neighbor has the same issue. |
|
 siersema
join:2005-06-16
Huntington Beach, CA | Did you run any tracert on those sites? Post them so we can figure out what is happening. |
|
|
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
1 edit | I have but they are non-conclusive. It's strange -- if you go to a given site (e.g. weather.com) it will hang for quite some time. If you go to a second site and then back, weather.com comes up immediatly. dslreports.com NEVER hangs, and mostly only the big sites do (e.g. weather.com, msnbc.com, aol.com). CNN doesn't hang; wellsfargo.com does. I've reset my router and arp cache and the problem continues, intermittently. I'll send some traces in a private message. |
|
Reviews:
·Verizon FiOS
 ·Charter
·AT&T U-Verse
 ·DSL EXTREME
| reply to PJL
I haven't noticed any issues. I do know that somewhat recently there was a pretty big thread about DNS issues in socal on the VZ forums. Are you using VZ DNS? If so have you tried a third-party like VZ or level3's (level3's are fast and super low latency in socal):
4.2.2.2
4.2.2.3
--
150/75 mbit Verizon FiOS connection FTW! |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| said by houkouonchi:I haven't noticed any issues. I do know that somewhat recently there was a pretty big thread about DNS issues in socal on the VZ forums. Are you using VZ DNS? If so have you tried a third-party like VZ or level3's (level3's are fast and super low latency in socal):
4.2.2.2
4.2.2.3
I'm using the default Verizon DNS -- ipconfig shows 192.168.1.1 and 68.238.64.12. Now that I think of it, this problem does sound like a DNS issue. I'll try the other servers and see what happens. I haven't been able to find the other threads on DNS problems -- can your provide a link? Thanks. |
|
Reviews:
·Verizon FiOS
·Charter
·AT&T U-Verse
·DSL EXTREME
| Original thread started 2 weeks ago and is 11 pages:
»forums.verizon.com/t5/FiOS-Inter···p/393781
Not a whole lot of activity in the last week though and I didn't really read through much of the thread but looking now it might not just be DNS but does look to be a similar issue.
Kinda coincidental around when this thread started is also when routing on my own FIOS Switched again and i started getting lower latency to even IPs again instead of odd when usually its the reverse.
--
150/75 mbit Verizon FiOS connection FTW! |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
2 edits | It's think it's a DNS and routing problem. I switched from the obtain automatically setting (which gave me the 192.168.1.1 primary and 68.238.64.12) to the Level 3 (4.2.2.2 and 4.2.2.3) and all sites are instantenous. Then I manually tried 68.238.64.12 with no secondary and it failed -- and the diagnostics said I had a DNS issue. I then tried 192.168.1.1 and got the same results. I then went back to the Level 3 DNS and all works perfectly. I'll put in ticket on Verizon Direct and will follow through on Monday with Verizon chat -- there's supposed to be an open ticket for me. |
|
Reviews:
·Verizon FiOS
·Charter
·AT&T U-Verse
·DSL EXTREME
| Cool! Glad the DNS issue was fixed by using level3's DNS servers. I used a DNS bench program a while back and level3 was pretty much the fastest of other ones tested (like googles). Mainly cause the latency was so much lower.
--
150/75 mbit Verizon FiOS connection FTW! |
|
MrShoop
join:2003-05-20
Manhattan Beach, CA | reply to PJL
I've been having problems as well, but was already using google DNS, so I don't think it is DNS issue. I just tried switching over to Level 3 dns, and it didn't help. Where in so cal are you - I'm in Santa Monica.
I can always get to Yahoo, google, dslreports. Facebook, twitter, steam store, and godaddy work intermittently. I just tried Facebook, and some responses came back, but it took over a minute.. |
|
Reviews:
·Verizon FiOS
·Charter
·AT&T U-Verse
·DSL EXTREME
| Getting any packetloss or anything to facebook.com?
It is less than 1 second here.
root@dekabutsu: 11:49 PM :~# time wget -O /dev/null http://facebook.com
--23:49:15-- http://facebook.com/
=> `/dev/null'
Resolving facebook.com... 69.171.229.11, 66.220.149.11, 69.171.224.11
Connecting to facebook.com|69.171.229.11|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.facebook.com/common/browser.php [following]
--23:49:15-- http://www.facebook.com/common/browser.php
=> `/dev/null'
Resolving www.facebook.com... 69.171.228.11
Connecting to www.facebook.com|69.171.228.11|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12,878 (13K) [text/html]
100%[================================================================================== ================================================================================== =======================>] 12,878 --.--K/s
23:49:15 (163.44 KB/s) - `/dev/null' saved [12878/12878]
real 0m0.287s
user 0m0.002s
sys 0m0.003s
--
150/75 mbit Verizon FiOS connection FTW! |
|
MrShoop
join:2003-05-20
Manhattan Beach, CA | I seem to be getting 100% packet loss most of the time, then it will light up for a minute, then die again.
imac:tmp$ time wget -O /dev/null »facebook.com
--00:13:41-- »facebook.com/
=> `/dev/null'
Resolving facebook.com... 69.171.229.11, 66.220.149.11, 69.171.224.11
Connecting to facebook.com[69.171.229.11]:80... failed: Operation timed out.
Connecting to facebook.com[66.220.149.11]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: »www.facebook.com/common/browser.php [following]
--00:14:56-- »www.facebook.com/common/browser.php
=> `/dev/null'
Resolving www.facebook.com... 69.171.228.12
Connecting to www.facebook.com[69.171.228.12]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12,663 [text/html]
100%[================================================================================== ====================================================>] 12,663 --.--K/s
00:14:56 (276.58 KB/s) - `/dev/null' saved [12663/12663]
real 1m15.203s
user 0m0.002s
sys 0m0.005s
and ping
$ ping facebook.com
PING facebook.com (69.171.229.11): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
[..]
--- facebook.com ping statistics ---
102 packets transmitted, 0 packets received, 100.0% packet loss
|
|
| Maybe try running MTR or something on it to see which hops it starts failing on.
--
150/75 mbit Verizon FiOS connection FTW! |
|
Reviews:
·Verizon FiOS
·Charter
·AT&T U-Verse
·DSL EXTREME
| reply to PJL
What I am seeing to the IP you are getting loss to:
root@dekabutsu: 12:30 AM :~# mtr -c 200 -r -i .2 69.171.229.11
HOST: dekabutsu Loss% Snt Last Avg Best Wrst StDev
1. router.houkouonchi.jp 75.5% 200 0.1 0.2 0.1 1.0 0.1
2. L103.LSANCA-DSL-29.verizon-g 0.0% 200 1.2 1.5 0.8 28.4 2.1
3. G0-3-1-7.LSANCA-LCR-21.veriz 0.0% 200 5.9 10.0 5.4 75.3 12.2
4. so-6-0-0-0.LAX01-BB-RTR1.ver 0.0% 200 5.6 11.1 5.5 143.5 19.1
5. 0.ae1.BR3.LAX15.ALTER.NET 0.0% 200 5.8 9.1 5.8 66.7 10.1
6. 4.68.63.245 0.0% 200 25.7 9.8 5.8 98.5 12.3
7. vlan70.csw2.LosAngeles1.Leve 0.0% 200 3.9 4.1 2.9 14.4 2.1
8. ae-73-73.ebr3.LosAngeles1.Le 0.0% 200 3.1 3.6 2.9 7.5 0.7
9. ae-3-3.ebr1.SanJose1.Level3. 0.0% 200 17.3 16.2 15.4 22.4 0.9
10. ae-61-61.csw1.SanJose1.Level 0.0% 200 15.7 18.5 15.2 29.4 3.9
11. ae-1-60.edge2.SanJose3.Level 0.0% 200 15.6 18.5 14.8 82.3 10.8
12. FACEBOOK-IN.edge2.SanJose3.L 0.0% 200 16.0 17.4 15.5 73.0 7.1
13. ae2.bb02.sjc1.tfbnw.net 0.0% 200 13.9 13.8 12.1 48.9 5.1
14. ae12.bb02.prn1.tfbnw.net 0.0% 200 41.0 41.3 39.6 88.6 5.5
15. ae1.dr04.prn1.tfbnw.net 0.5% 200 39.7 43.4 39.4 150.5 13.3
16. po1023.csw06b.prn1.tfbnw.net 0.5% 200 39.9 39.7 38.8 50.1 1.6
17. www-10-06-prn1.facebook.com 0.5% 200 39.2 39.7 39.0 51.9 1.1
--
150/75 mbit Verizon FiOS connection FTW! |
|
benm1
join:2011-04-14
Santa Monica, CA | reply to MrShoop
I'm in Santa Monica and have been unable to load a few specific sites for a few days, regardless of which DNS servers I use. These include:
»www.techmeme.com
»speedtest.net
»store.steampowered.com
In addition, I cannot login to Xbox Live on my 360, and its network diagnostics report "MTU Error". |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 | On or about 1/30/12 a Verizon tech said they needed to flush a router cache that was causing the routing delays. This must have been done, because since about Tuesday 1/31/12 responses are now normal. |
|
benm1
join:2011-04-14
Santa Monica, CA | Hmm, maybe we're dealing with separate issues? I'm still experiencing the problem at this moment, and from what I've seen so far the sites I listed fail to load at all, rather than loading slowly or intermittently. Also, the sites that were giving you problems, PJL, are loading fine for me. (weather.com, msnbc.com, aol.com, wellsfargo.com) |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| said by benm1:Hmm, maybe we're dealing with separate issues? I'm still experiencing the problem at this moment, and from what I've seen so far the sites I listed fail to load at all, rather than loading slowly or intermittently. Also, the sites that were giving you problems, PJL, are loading fine for me. (weather.com, msnbc.com, aol.com, wellsfargo.com)
I've read on a variety of forums that alot of Southern California is having these types of routing issues. I see you've opened a thread on the Verizon Direct board. I did that too, but they didn't respond until after the problem was already fixed in response to a chat session I had. In the session, they wanted me to do a variety of things that I knew would not fix the issue but would muck up my PC -- like resetting browser settings to default, etc. (things that had not changed). They wanted to reset my router's IP (which woudl break remote DVR and caller ID), so I refused to let them do that. They wanted to replace my router (which I knew was not the problem) and I pretty much demanded an escallation to level 2 support since I knew others in the area had the same problem. About 24 hours later a level 2 tech called and admitted that there was a known issue impacting Southern California WAN routers and others as well. He placed a ticket with the router team to flush the router at my central office and up the chain. It seems to have worked -- things are much better now.
Router tables are getting corrupted somehow, and propagating across the network. Until the solve this root cause, we'll likely see more of these problems. I don't understand why they can't get it fixed -- these types of issues have been around for as long as networking has existed. |
|
benm1
join:2011-04-14
Santa Monica, CA | Ugh, sounds like it was a hassle. Thanks for the info. I hope that by now they have this flagged as a known issue in their ticketing system, and I'll be able to get it escalated to the router team without going through all that again.  |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| said by benm1:Ugh, sounds like it was a hassle. Thanks for the info. I hope that by now they have this flagged as a known issue in their ticketing system, and I'll be able to get it escalated to the router team without going through all that again.
Not too much of a hassle but I had to be persisent on the online chat, and when the tech called I needed to make sure he knew I knew about what I was talking -- I've worked IT/networking so I knew the terms and what the problem seemed to be -- routing tables sending packet to never-never land or not allowing the proper return route.
Verizon tries to route in the most efficient manner based on geography and point-of-presence to other Internet networks -- hence the difference in DNS returns for them versus other DNS servers. Something has this messed up. |
|
 rtcyFACTS only pleasePremium
join:1999-10-16
Norwalk, CA | reply to PJL
said by PJL:said by houkouonchi:I haven't noticed any issues. I do know that somewhat recently there was a pretty big thread about DNS issues in socal on the VZ forums. Are you using VZ DNS? If so have you tried a third-party like VZ or level3's (level3's are fast and super low latency in socal):
4.2.2.2
4.2.2.3
I'm using the default Verizon DNS -- ipconfig shows 192.168.1.1 and 68.238.64.12. Now that I think of it, this problem does sound like a DNS issue. I'll try the other servers and see what happens. I haven't been able to find the other threads on DNS problems -- can your provide a link? Thanks. I'm having them too and I have the router on OPENDNS servers and all the machines in the house too. still seeing a lot of freeze ups
also seeing pixelation the 7232 dvr 2 separate issues but maybe not. |
|
