Reviews:
 ·Verizon FiOS
| [Southwest] Socal VZ connectivity issues/packetlossLooks like cogent is having some issues on VZ in the socal area. Only one of my connections is being effected:
Problematic line:
traceroute to 208.97.140.21 (208.97.140.21), 30 hops max, 40 byte packets
1 L103.LSANCA-DSL-29.verizon-gni.net (71.110.63.1) 1.200 ms 0.850 ms 0.749 ms
2 G0-3-1-7.LSANCA-LCR-21.verizon-gni.net (130.81.140.224) 5.394 ms 5.458 ms 5.657 ms
3 so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.151.236) 5.707 ms 5.617 ms 5.518 ms
4 0.so-6-2-0.XT1.LAX7.ALTER.NET (152.63.112.45) 5.819 ms 5.846 ms 5.997 ms
5 0.xe-4-1-1.XL3.LAX15.ALTER.NET (152.63.10.138) 5.810 ms 5.921 ms 5.953 ms
6 POS6-0-0.GW3.LAX15.ALTER.NET (152.63.112.105) 7.526 ms 6.399 ms 5.839 ms
7 internapGIGE-gw.customer.alter.net (157.130.236.110) 7.757 ms 6.300 ms 6.286 ms
8 border3.po1-20g-bbnet1.lax010.pnap.net (216.52.255.10) 7.045 ms 6.791 ms 6.821 ms
9 dreamhost-1.border3.lax010.pnap.net (64.7.192.250) 6.157 ms 6.206 ms 9.425 ms
10 * gar-border-1.dreamhost.com (66.33.203.4) 49.516 ms 49.017 ms
11 * box.houkouonchi.jp (208.97.140.21) 48.807 ms 49.750 ms
Good:
traceroute to 208.97.140.21 (208.97.140.21), 30 hops max, 40 byte packets
1 L100.LSANCA-VFTTP-158.verizon-gni.net (108.38.63.1) 1.083 ms 0.883 ms 0.814 ms
2 G0-3-1-7.LSANCA-LCR-21.verizon-gni.net (130.81.140.224) 5.513 ms 5.463 ms 5.473 ms
3 so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.29.124) 5.593 ms 5.479 ms 5.566 ms
4 0.xe-4-1-0.XL3.LAX15.ALTER.NET (152.63.6.21) 7.457 ms 5.835 ms 7.316 ms
5 POS6-0-0.GW3.LAX15.ALTER.NET (152.63.112.105) 49.709 ms * 49.792 ms
6 internapGIGE-gw.customer.alter.net (157.130.236.110) 59.273 ms 58.516 ms 58.941 ms
7 border3.po2-20g-bbnet2.lax010.pnap.net (216.52.255.101) 14.891 ms 16.168 ms 17.874 ms
8 dreamhost-1.border3.lax010.pnap.net (64.7.192.250) 5.996 ms 6.065 ms 6.199 ms
9 gar-border-1.dreamhost.com (66.33.203.4) 50.022 ms 50.431 ms *
10 box.houkouonchi.jp (208.97.140.21) 6.245 ms 6.115 ms 6.356 ms
As you can see big latency difference. Also seeing tons of packetloss:
--- 208.97.140.21 ping statistics ---
500 packets transmitted, 364 received, 27% packet loss, time 8166ms
rtt min/avg/max/mdev = 48.863/49.230/50.135/0.343 ms, pipe 5
And to level3's DNS servers which was making browsing slow as shit which is kind of why it caught my attention:
--- 4.2.2.2 ping statistics ---
500 packets transmitted, 369 received, 26% packet loss, time 8157ms
rtt min/avg/max/mdev = 48.495/48.913/53.511/0.531 ms, pipe 5
The reverse traceroute shows the latency jump when hitting cogent.
Problematic connection:
traceroute to fios.houkouonchi.jp (71.110.63.2), 30 hops max, 46 byte packets
1 ip-66-33-193-1.dreamhost.com (66.33.193.1) 0.778 ms 0.935 ms 0.543 ms
2 ip-66-33-203-3.dreamhost.com (66.33.203.3) 0.195 ms 0.167 ms 0.191 ms
3 vl204.mag01.lax01.atlas.cogentco.com (38.122.20.217) 127.393 ms 176.970 ms 0.579 ms
4 te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 0.892 ms 0.745 ms 0.428 ms
5 te8-3.ccr02.lax05.atlas.cogentco.com (154.54.29.202) 0.530 ms 0.640 ms 0.603 ms
6 uunet.lax05.atlas.cogentco.com (154.54.13.86) 0.442 ms 0.520 ms 0.410 ms
7 0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6) 32.774 ms 159.575 ms 24.414 ms
8 * * *
9 * fios.houkouonchi.jp (71.110.63.2) 48.977 ms 48.958 ms
good one:
traceroute to pool-71-160-127-29.lsanca.fios.verizon.net (71.160.127.29), 30 hops max, 46 byte packets
1 * * *
2 ip-66-33-203-3.dreamhost.com (66.33.203.3) 0.267 ms 0.207 ms 0.250 ms
3 vl204.mag01.lax01.atlas.cogentco.com (38.122.20.217) 0.441 ms 0.383 ms 0.396 ms
4 te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 0.467 ms 0.469 ms 0.466 ms
5 te8-2.ccr02.lax05.atlas.cogentco.com (130.117.50.90) 47.062 ms 185.769 ms 2.407 ms
6 uunet.lax05.atlas.cogentco.com (154.54.13.86) 66.112 ms 0.575 ms 0.482 ms
7 0.ae1.LAX01-BB-RTR1.verizon-gni.net (152.63.112.2) 1.995 ms 1.909 ms 2.049 ms
8 * * *
9 pool-71-160-127-29.lsanca.fios.verizon.net (71.160.127.29) 6.077 ms 6.163 ms 6.026 ms
At first i thought it was cogent but I am also seeing it on the second connection to he.net:
traceroute to he.net (216.218.186.2), 30 hops max, 46 byte packets
1 router.houkouonchi.jp (1.1.1.1) 0.180 ms 0.077 ms 0.499 ms
2 L100.LSANCA-VFTTP-158.verizon-gni.net (108.38.63.1) 1.157 ms 0.908 ms 1.041 ms
3 G0-3-1-7.LSANCA-LCR-21.verizon-gni.net (130.81.140.224) 5.648 ms 6.463 ms 5.932 ms
4 so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.151.246) 5.745 ms 5.790 ms 6.014 ms
5 0.ae1.BR3.LAX15.ALTER.NET (152.63.2.129) 5.997 ms 6.453 ms 5.910 ms
6 te6-3-10G.ar4.LAX2.gblx.net (64.208.110.169) 425.141 ms 984.483 ms 1357.859 ms
7 64.209.105.42 (64.209.105.42) 53.029 ms 58.197 ms *
8 10gigabitethernet2-4.core1.pao1.he.net (72.52.92.21) 58.999 ms 60.394 ms *
9 10gigabitethernet1-2.core1.fmt1.he.net (184.105.213.65) 59.794 ms 94.900 ms *
10 he.net (216.218.186.2) 59.430 ms * 62.870 ms
So it looks like they are having some issues right now.
--
300/150 mbit Bonded Verizon FiOS connection FTW! |
|
| Same here, frustrating.  |
|
| reply to houkouonchi
I'm in Murrieta and connection is slower then granny crossing the street..
don't need to do a bunch of trace routes to notice something weird is going on.. trying to do some shopping at newegg and amazon and pages are taking forever. |
|
| reply to houkouonchi
Visualware |
These are my current speed tests to myspeed.visualware.com's Los Angeles site.
Speedtest.net does not even complete loading up so no tests from there.
Speed test statistics
---------------------
Download speed: 62120 bps
Upload speed: 14988040 bps
Quality of service: 6 %
Download test type: socket
Upload test type: socket
Maximum download pause: 5276 ms
Average download pause: 574 ms
Minimum round trip time to server: 48 ms
Average round trip time to server: 646 ms
--
--50/25 FIOS ~ 58.36D--36.52U-- |
|
| reply to houkouonchi
Same here, Victorville, CA
Tracing route to 216.65.212.121 over a maximum of 30 hops
1 3 ms 4 ms 4 ms L300.LSANCA-VFTTP-82.verizon-gni.net [98.112.134.1]
2 5 ms 7 ms 7 ms G0-6-3-7.LSANCA-LCR-21.verizon-gni.net [130.81.107.64]
3 6 ms 7 ms 7 ms ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.254]
4 51 ms 52 ms 52 ms 0.ae1.BR3.LAX15.ALTER.NET [152.63.2.129]
5 51 ms 52 ms * 204.255.168.134
6 9 ms 9 ms 9 ms cr1.la2ca.ip.att.net [12.123.30.6]
7 5 ms 7 ms 9 ms 12.123.132.217
8 53 ms 54 ms 54 ms 12.122.251.154
9 11 ms 12 ms 14 ms 206.19.184.114
10 51 ms 52 ms 52 ms core2-z-g1-1.irv.sbcidc.com [216.65.209.14]
11 * * 55 ms dst2-b-g1-1.irv.sbcidc.com [216.65.208.145] |
|
ALbino
join:2003-02-01
Chino Hills, CA | So happy to see this thread, as I was already in troubleshoot mode.
Barely working here in Chino Hills as well. No obvious packet loss on my tracert, but websites are barely loading, and many aren't loading at all. SpeedTest doesn't load either, but I tried downloading a file from a work FTP and only got around 10kB/s on my 150mbit connection. Weirdly, I seem to be able to upload just fine, and uploaded a large file back to the FTP at 30+ mbit. |
|
Reviews:
·Verizon FiOS
| said by ALbino:So happy to see this thread, as I was already in troubleshoot mode.
Barely working here in Chino Hills as well. No obvious packet loss on my tracert, but websites are barely loading, and many aren't loading at all. SpeedTest doesn't load either, but I tried downloading a file from a work FTP and only got around 10kB/s on my 150mbit connection. Weirdly, I seem to be able to upload just fine, and uploaded a large file back to the FTP at 30+ mbit.
Unfortunately its hard to troubleshoot with just a traceroute. The reason is because the type of routing vz uses on their juniper routers (they vary depending on destination/source ip (and port) means that even if you are going to the same IP address going to a different port can possibly take a completely different route. This also means that you might be getting tons of packetloss to a game-server and once the route cache goes away and you reconnect a few min later (to the same destination IP/port but different source IP/port) your latency/packetloss will be fine.
This is why ICMP I am seeing 30% packetloss but when i do a wget download off my server i get 150 megabits (no slowdown). However; on another site I get 0% ICMP packetloss to it is *crawling* so obviously the HTTP/port 80 route is getting the PL. Their decisions on routing kind of make it hard to troubleshoot issues at times =(
--
300/150 mbit Bonded Verizon FiOS connection FTW! |
|
ALbino
join:2003-02-01
Chino Hills, CA | Yeah, definitely.
Well, hopefully they're working on it?  |
|
 PinanPremium,ExMod 2000-03
join:2000-09-02
Murrieta, CA
kudos:1 | reply to RedCaliSS
Yup. Murrieta is sloooooowwwwww. |
|
| reply to houkouonchi
I'm experiencing the same issue on Verizon DSL in Commerce. I didn't see anyone point it out on the DSL forum, but I saw this topic on the DSLR homepage. Now that I know I'm not the only one with the problem, I'll probably just wait it out and see if it's fixed by tomorrow (Monday) afternoon before I call it in. |
|
|
|
Reviews:
·Verizon FiOS
| reply to houkouonchi
one minute everything is all good once again, then bad to sucking..
i'm on the quantum 50/30
speedtest.net is totally unreachable
below is Verizons speedtest..
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 37.04Mb/s
running 10s inbound test (server to client) . . . . . . 8.84Mb/s
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [xxx.xx.xx.xx] but Client says [192.168.1.11] |
|
rlstarryPremium
join:2002-05-22
Lake Elsinore, CA | reply to houkouonchi
Slow here in Lake Elsinore as well. Can't believe tethering via cell phone is faster than my FIOS. Hopefully Verizon gets on this soon, I'm going to use up all my cell phone data allotment for the month |
|
| reply to houkouonchi
hesperia ca. running into all kinds of slow up here. trace routes are all over the place. |
|
| reply to houkouonchi
I am having the problem too, but I don't have a fancy second line like somebody (snicker).
--- 8.8.8.8 ping statistics ---
46 packets transmitted, 37 packets received, 19% packet loss
round-trip min/avg/max = 82.394/98.244/128.187 ms
|
|
 ara
@verizon.net | reply to houkouonchi
Having issues also. In Glendora.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\arathres>tracert www.google.com
Tracing route to www.google.com [74.125.224.179]
over a maximum of 30 hops:
1
C:\Users\arathres>tracert www.battle.net
Tracing route to www.battle.net [12.129.242.30]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms myrouter.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.LSANCA-VFTTP-140.verizon-gni.net [173.51.17
3.1]
3 12 ms 7 ms 9 ms G0-10-2-1.LSANCA-LCR-21.verizon-gni.net [130.81.
138.122]
4 8 ms 8 ms 8 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.151.236]
5 * * * Request timed out.
6 7 ms 7 ms 6 ms 204.255.168.134
7 8 ms 10 ms * cr1.la2ca.ip.att.net [12.123.132.129]
8 7 ms 8 ms 7 ms gar29.la2ca.ip.att.net [12.122.129.241]
9 51 ms 8 ms 8 ms 12-122-254-234.attens.net [12.122.254.234]
10 * 51 ms * mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
Looks like a routing issue because it is Hit/Miss.
Very slow and choppy as the connection gets re-routed through servers.
hope they fix it.
Does anyone know of a Verizon FIOS site where to report issues?
Thanks. |
|
| reply to houkouonchi
Slow in Lake Mathews area. Fast peaks here and there. |
|
| reply to houkouonchi
Slow in so cal. Looks widespread |
|
danman48
join:2007-10-11
Huntington Beach, CA | reply to houkouonchi
Received tweet back from VZ Support. They are aware of the issue and have a est. fix time of 10pm |
|
lordsegan
join:2002-04-16
Palos Verdes Peninsula, CA | reply to houkouonchi
Very slow |
|
| reply to houkouonchi
Slow as hell here in Lake Elsinore as well; so very thankful its just not me. |
|
