US Telco Support > Verizon > Verizon Fiber Optics > [Southwest] Problem with Fios

[Southwest] Problem with Fios

Re: Problem with Fios

reply to andyjai
I'm in Walnut with FIOS Business and this is been happening a lot at night, massive packet loss, massive slowdown into the kilobit speeds, massive disconnects.

Been on the phone with support for days now, every time I get a different answer, this is hurting a lot more than just casual surfing, hitting me in the wallet with work!!!

Router has nothing to do with it, I run my own firewall and it is a problem on their end, especially at night, I sure hope they are not throttling the connection, this is going to force me to end my 4+ year business with FiOS.

I don't have any packet loss problem, just getting slower and slower speed. I understand your pain, our company was using verizon dsl and the top speed is 0.5Mbps on a 7Mbps plan and it also disconnect very frequently. Verizon never fix the problem because they say DSL is old and you will only get what you can get, and we just switched to another 4G ISP.

reply to andyjai
Redondo Beach...

35/35 Plan

Me too. Walnut, CA, just down the road from Rowland Heights. More in this thread:

»Anyone having problems in the Riverside County area?

1:58 am. Back to full speed, probably until about 10:00 am.

reply to andyjai
I too have been having youtube issues. its gotten so bad that i don't even dream about 1080p (almost always loads much slower than real time), and 720p works maybe half the time. I have talked to others across the country (not on fios), and they have been saying that youtube sucks too.

The effective value of 50/25 is slowly declining.

reply to praetoralpha

Re: Problem with Fios

reply to andyjai
I swap to the refurbished Actiontec Rev I that I got from Verizon today and it gave me another IP, but the problem still exist.

Verizon speedtest

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 246.95Kb/s
running 10s inbound test (server to client) . . . . . . 21.23kb/s

------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11

------ Web100 Detailed Analysis ------
Client Receive Window detected at 66560 bytes.
Link detection algorithm failed due to excessive Round Trip Times.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 0 msec; the Packet size = 1452 Bytes; and
There were 28 packets retransmitted, 10 duplicate acks received, and 21 SACK blocks received
The connection stalled 3 times due to packet loss
The connection was idle 0 seconds (Na%) of the time

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
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

Speedtest.net Los Angeles
Atlantic Metro 17ms 33.21Down 24.45Up
DreamHost 11ms 38.63Down 30.07Up
Internode 17ms Test stuck on connecting
Race Comm. 21ms Test stuck on connecting

Centurylink.net (San Jose) 35ms 55.58Up 32.54Down
Speakeasy.net Test Fail

Microsoft 800KB/s
Nvidia 400KB/s
Ati 4KB/s
Apple 2000KB/s

Now is 6pm and I will expect even worse speed after dinner.

reply to andyjai
Just called Verizon again and they put me on hold while a network tech take a look, but at the end they are just sending a tech out.

reply to andyjai
this problem is still occurring, the writing is on the wall, whether verizon believes it or not, their backbone is way over subscribed and this is why it is only happening at night, i think it might be time to alert the media this would make for a good story to someone willing to investigate it

reply to andyjai
Yes, I've been having this problem, too. It first started happening on the evening of January 28th, went away around 1 AM and the issue is now back in full force this evening. I tried calling Verizon tech support and they reset my router to factory defaults without me telling them! It looks like there's a router somewhere at the 4th hop where the packet loss starts. The router's IP Address is:

130.81.29.124
130.81.151.246

reply to andyjai
3 6 ms 6 ms 7 ms 130.81.182.226
4 32 ms * 33 ms 130.81.29.126
5 41 ms 31 ms * 152.63.10.157
6 * 77 ms * 152.63.18.241
7 * 77 ms 76 ms 152.63.21.65
8 122 ms 122 ms 118 ms 152.179.72.66
9 80 ms 76 ms 76 ms 209.85.255.68
10 80 ms 76 ms 78 ms 209.85.252.242
11 81 ms 87 ms 83 ms 209.85.249.11
12 82 ms 85 ms 81 ms 72.14.238.16
13 82 ms 88 ms 94 ms 216.239.49.145
14 88 ms 85 ms 84 ms 8.8.8.8

these problems have been occurring for me since december and all they are doing is wasting people's time, no reason to have a tech out to a home when the issues are clearly on verizon's transport and backbone.

these problems go away during the dawn hours and day when most people are sleeping or not at home.

they just need to fix their network, damn it, hate wasting time with B.S. crap

reply to andyjai
I realize it's not an issue that can be fixed with the push of a button, but Verizon does need to stop sending out techs for issues that obviously have nothing to do with equipment at the homes. They need to "own up" and resolve the issue.

reply to andyjai
I made a similar post a few weeks back, I have the same exact issue. It seems to come and go...

reply to andyjai

reply to jk111

reply to andyjai
2AM and speed is back. I am able to stream youtube 60-80Mbps.

Verizon standard speedtest

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 39.03Mb/s
running 10s inbound test (server to client) . . . . . . 45.81Mb/s

------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
100 Mbps FastEthernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 9.95 msec; the Packet size = 1452 Bytes; and
There were 587 packets retransmitted, 2405 duplicate acks received, and 2941 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 0.42 seconds (4.19%) of the time
This connection is sender limited 72.41% of the time.
This connection is network limited 27.08% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
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 [71.104.67.209] but Client says [192.168.1.168]

Verizon 100Mb test 6ms 84.1Down 39.32Up
Speakeasy 73.09Down 27.94Up
Speedtest.net 4servers all around 80Down 30Up

Nvidia 8000KB/s
ATI 5500KB/s
Microsoft 6000KB/s
Apple 6000KB/s

Does Verizon reboot their equipments at 2 am or something? I just don't get how things get clear up after certain time and then get clog up again next day.