|
Home | Reviews | Speed Test | Tools | News | Forums | Info | About | Join |
I have two 35/35 FIOS connections. In order to do this I had to get one business connection and one residential. Sadly the business (without static IP) cost as much as tripple play did on the residential which included phone and ultimate HD. Also it took several weeks to get the fiber drop done and Verizon had to reschedule the appointment 3 times. On one time they came by but because there was a lock box they didn't even ring my doorbell which I would have answered as I was home (not that they could have done the install anyway). Other than the fact it was a pain to get things installed service has been good. I get good latency to my server from both connections: admin@zeroshell: 09:31 AM :~# traceroute -i ETH01 208.97.141.21 traceroute to 208.97.141.21 (208.97.141.21), 30 hops max, 40 byte packets 1 L100.LSANCA-VFTTP-79.verizon-gni.net (173.51.208.1) 4.057 ms 3.926 ms 4.705 ms 2 4-2-1079.LSANCA-LCR-10.verizon-gni.net (130.81.107.150) 5.240 ms 3.903 ms 5.194 ms 3 so-4-0-0-0.LAX01-BB-RTR2.verizon-gni.net (130.81.28.74) 4.998 ms 4.152 ms 4.622 ms 4 0.so-6-0-0.XT2.LAX9.ALTER.NET (152.63.10.157) 7.469 ms 7.096 ms 7.176 ms 5 0.so-7-1-0.XL4.LAX15.ALTER.NET (152.63.1.242) 7.515 ms 6.725 ms 7.728 ms 6 POS7-0-0.GW3.LAX15.ALTER.NET (152.63.112.109) 9.695 ms 9.275 ms 9.948 ms 7 internapGIGE-gw.customer.alter.net (157.130.236.110) 9.969 ms 9.386 ms 9.794 ms 8 border11.po2-20g-bbnet1.lax.pnap.net (216.52.255.104) 9.800 ms 9.306 ms 9.807 ms 9 newdream-8.border11.lax.pnap.net (216.52.220.146) 9.804 ms 9.345 ms 9.803 ms 10 ip-66-33-201-115.dreamhost.com (66.33.201.115) 9.812 ms 14.265 ms 9.941 ms 11 gameserver.houkouonchi.jp (208.97.141.21) 7.527 ms 6.799 ms 7.459 ms admin@zeroshell: 09:31 AM :~# traceroute -i ETH02 208.97.141.21 traceroute to 208.97.141.21 (208.97.141.21), 30 hops max, 40 byte packets 1 L100.LSANCA-VFTTP-79.verizon-gni.net (173.51.208.1) 3.702 ms 3.732 ms 4.938 ms 2 4-2-1079.LSANCA-LCR-10.verizon-gni.net (130.81.107.150) 4.977 ms 3.979 ms 4.961 ms 3 so-4-0-0-0.LAX01-BB-RTR2.verizon-gni.net (130.81.28.74) 4.957 ms 4.235 ms 4.859 ms 4 0.so-6-0-0.XT2.LAX9.ALTER.NET (152.63.10.157) 7.321 ms 6.837 ms 7.423 ms 5 0.so-7-1-0.XL4.LAX15.ALTER.NET (152.63.1.242) 7.506 ms 6.694 ms 12.469 ms 6 POS7-0-0.GW3.LAX15.ALTER.NET (152.63.112.109) 9.950 ms 9.195 ms 9.949 ms 7 internapGIGE-gw.customer.alter.net (157.130.236.110) 9.976 ms 9.316 ms 10.202 ms 8 border11.po2-20g-bbnet1.lax.pnap.net (216.52.255.104) 9.962 ms 9.324 ms 29.947 ms 9 newdream-8.border11.lax.pnap.net (216.52.220.146) 9.970 ms 9.293 ms 9.958 ms 10 ip-66-33-201-115.dreamhost.com (66.33.201.115) 42.447 ms 24.072 ms 14.955 ms 11 gameserver.houkouonchi.jp (208.97.141.21) 7.480 ms 6.598 ms 7.482 ms File downloading goes fast over the bonded connection: admin@zeroshell: 09:27 AM :~# wget -O /dev/null »us.download.nvidia.com/X ··· 6.35.run --09:27:01-- »us.download.nvidia.com/X ··· 6.35.run => `/dev/null' Resolving us.download.nvidia.com... 64.208.159.48, 64.208.159.9 Connecting to us.download.nvidia.com[64.208.159.48]:80... connected. HTTP request sent, awaiting response... 200 OK Length: 42,572,777 [application/octet-stream] 100%[================================================================================== =>] 42,572,777 7.97M/s ETA 00:00 09:27:06 (7.90 MB/s) - `/dev/null' saved [42572777/42572777] I am enjoying the speeds. Single connection speed test: »www.speedtest.net/result ··· 2835.png Bonded: »www.speedtest.net/result ··· 4348.png Verizons test (bonded): »box.houkouonchi.jp/veriz ··· st_2.png When I decided to buy a house and move the *first* requirement I had was a Verizon FIOS area. I have been waiting a long time and finally got it and am enjoying having a 70/70 connection! Update 08/19/2010: So far I have had the service for well over a month and no problems. My non-business trippeplay connection got bumped up to 45/35. I found out some IPs on my works network show latency in the range of 3-4 ms =) Update 09/30/2011: Back in July I upgraded to the 150/35 plan. It is actually provisioned for around 155/75 and I am really glad I got it. The service has been reliably fast (never had problems not getting my full speed from my colo'd server) and the upload was even better than I was expecting (75mbit where I was expecting around 65mbit from some others testing). I think my most favorite thing since this upgrade is the latency. Sine they upgraded me to gpon I can get under 3ms (reliably) to my colo'd server and under 1ms to the gateway: Ping to gateway: PING 71.110.63.1 (71.110.63.1) 56(84) bytes of data. 64 bytes from 71.110.63.1: icmp_seq=1 ttl=126 time=0.992 ms 64 bytes from 71.110.63.1: icmp_seq=2 ttl=126 time=0.866 ms 64 bytes from 71.110.63.1: icmp_seq=3 ttl=126 time=0.968 ms 64 bytes from 71.110.63.1: icmp_seq=4 ttl=126 time=0.832 ms 64 bytes from 71.110.63.1: icmp_seq=5 ttl=126 time=0.928 ms --- 71.110.63.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 402ms rtt min/avg/max/mdev = 0.832/0.917/0.992/0.063 ms traceroute to colo: root@dekabutsu: 03:40 AM :~# traceroute -I 69.163.188.21 traceroute to ip-69-163-188-21.dreamhost.com (69.163.188.21), 30 hops max, 46 byte packets 1 router.houkouonchi.jp (1.1.1.1) 0.195 ms 0.180 ms 0.168 ms 2 L103.LSANCA-DSL-29.verizon-gni.net (71.110.63.1) 1.080 ms 0.766 ms 0.898 ms 3 G0-3-1-7.LSANCA-LCR-22.verizon-gni.net (130.81.146.60) 1.325 ms 1.210 ms 1.525 ms 4 so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net (130.81.29.126) 2.307 ms 2.008 ms 2.052 ms 5 0.xe-11-1-0.BR1.LAX15.ALTER.NET (152.63.112.5) 2.123 ms 2.208 ms 2.244 ms 6 te7-2.ccr02.lax05.atlas.cogentco.com (154.54.13.85) 2.387 ms 2.307 ms 2.275 ms 7 te0-0-0-2.ccr22.lax01.atlas.cogentco.com (154.54.30.193) 2.787 ms 2.810 ms 2.774 ms 8 te8-1.mpd03.lax01.atlas.cogentco.com (154.54.28.146) 2.548 ms 2.551 ms 2.515 ms 9 38.122.20.218 (38.122.20.218) 2.640 ms 2.704 ms 2.543 ms 10 ip-66-33-201-114.dreamhost.com (66.33.201.114) 57.120 ms 17.237 ms 11.554 ms 11 ip-69-163-188-21.dreamhost.com (69.163.188.21) 2.465 ms 2.442 ms 2.325 ms Long ping to server: 64 bytes from 69.163.188.21: icmp_seq=292 ttl=252 time=2.38 ms 64 bytes from 69.163.188.21: icmp_seq=293 ttl=252 time=2.42 ms 64 bytes from 69.163.188.21: icmp_seq=294 ttl=252 time=2.45 ms 64 bytes from 69.163.188.21: icmp_seq=295 ttl=252 time=2.45 ms 64 bytes from 69.163.188.21: icmp_seq=296 ttl=252 time=2.45 ms 64 bytes from 69.163.188.21: icmp_seq=297 ttl=252 time=2.54 ms 64 bytes from 69.163.188.21: icmp_seq=298 ttl=252 time=2.41 ms 64 bytes from 69.163.188.21: icmp_seq=299 ttl=252 time=2.40 ms 64 bytes from 69.163.188.21: icmp_seq=300 ttl=252 time=2.58 ms --- 69.163.188.21 ping statistics --- 300 packets transmitted, 300 received, 0% packet loss, time 30380ms rtt min/avg/max/mdev = 2.317/2.473/2.972/0.104 ms As you can see from the summary and results before, extremely stable latency with almost no jitter. Average jitter/mdev is only .104ms (1/10th of a ms). The latency is pretty incredible considering at work a 10 gig direct connection between two data centers (one in Irvine and one in LA) which is about 60 miles is 1.2ms. I am around 42 miles to the server and its a something I can get at a residence and its only 2.4ms Latency from my server in LA to another one about 5 miles away from me in Ontario is 1.7-2ms so just barely lower than what I am seeing and that is with peering and 1000m+ connections: # traceroute -I linkline.com traceroute to host-216-66-249-76.static.linkline.com (216.66.249.76), 30 hops max, 46 byte packets 1 ip-66-33-193-1 (66.33.193.1) 125.005 ms 0.449 ms 0.306 ms 2 ip-66-33-201-113 (66.33.201.113) 0.355 ms 0.624 ms 0.403 ms 3 linkline.com.any2ix.coresite.com (206.223.143.28) 0.430 ms 0.333 ms 0.274 ms 4 ca-ont-core-gsr.linkline.com (66.59.246.254) 1.335 ms 1.354 ms 1.473 ms 5 host-216-66-249-76.static.linkline.com (216.66.249.76) 2.168 ms 1.706 ms 1.979 ms Really shows how just about 'best case' I am getting latency wise. I am a gamer so its really nice to get such low latency. The biggest downside of the connection is the trouble I went through to get it. It took 6 months and a good 20+ hours on the phone with VZ to finally get them to do the upgrade. It wasn't until a great tech on dslreports got involved that the ball finally got rolling and things getting done. Update 2013-08-28: After vz had me upgrade to small business for heavy bandwidth usage they are now threatening disconnection even on small business. I dont understand what their problem is as they are still making money off me. This caused me to update my review and reduce the value for money as well as pre sales information. member for 21.6 years, 4332 visits, last login: 9 years ago updated 10.5 years ago
|