US Telco Support > Verizon > Verizon Fiber Optics > Anyone having problems in the Riverside County area?

reply to mkaishar

Re: Anyone having problems in the Riverside County area?

reply to FutureX2001

Re: Anyone having problems in the Riverside County area?

reply to FutureX2001
I've submitted a ticket on the Verizon Direct forum with my tests so far, today I also decided to bypass the router and run the verizon test directly from the ONT to my PC's ethernet port:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 7.04Mb/s
running 10s inbound test (server to client) . . . . . . 33.28Mb/s

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 237824 bytes.
45 Mbps T3/DS3 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 = 10.78 msec; the Packet size = 1460 Bytes; and
There were 518 packets retransmitted, 1849 duplicate acks received, and 2319 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.21 seconds (2.09%) of the time
This connection is sender limited 71.41% of the time.
This connection is network limited 27.67% 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
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

reply to FutureX2001

Re: Anyone having problems in the Riverside County area?

Also in Torrance, went through the whole 2 hour dance with Tech Support last Saturday. They concluded I needed a new router. I received the router on Tuesday and it's made no difference. I haven't called again because it hurts.

Normal speed for me is 30 mbps upload and download. As of 1/31 at 650 pm PST, 12.44 down and 23.65 up. It was fine until about 5 pm.

If this is not corrected soon, I'll be asking for a reduction on my bill. I'm not getting the service I pay for. I'll likely have to call again to document the repeated problem, as much as I hate doing so.

reply to FutureX2001
Been having the problem since last Thursday, exactly one week. Tuesday, they finally figured out that they had a problem affecting California. I was told that it would be fixed Wednesday. It was better Wednesday and today, but not fixed. Tonight I was told that it would be fixed by 11 am - 12 noon Friday (tomorrow).

Most of the people complaining in this thread, and this other thread: »[Southwest] Problem with Fios
are in So Cal. I'm in Walnut, as is another person. Others are in Rowland Heights, Redondo Beach, and Perris.

Someone in my neighborhood changed their SSID to "Slow_Internet_byVerizon". That cracked me up. I did get a new wireless-n router out of it, though.

reply to JohnyDr
I'm in Walnut, CA, and I've been noticing these problems since Monday night. I'm seeing excessive packet loss of more than 25% when just pinging a website like io9.com. I ran a tracert and the packets would start dropping at the 4th hop, which is and IP in the 130.81.x.x subnet, which is a Verizon router for the "LAX" area (at least that's what the reverse lookup said).

I called tech support and they were worse than helpless, the first guy I talked to on Tuesday afternoon did a factory reset of my router without my approval! I called again that night after fixing everything and got someone helpful who took down my findings, but I heard nothing of it. I called again last night and the guy wanted to send a tech out to my house to check on my equipment after I repeatedly told him that it's not my gear that's busted, but Verizon's. I called again tonight and got the same deal and I had to raise my voice to the support rep because he was still talking about sending a tech over. Lastly, I called customer service and eventually spoke to someone in Escalations. I explained my problem again and FiOS tech support's shortcomings, and he said he was going to create a "ROC" ticket that would have more weight within the company, whatever that means. If you guys have the patience, maybe that would be the way to go. Tech Support always assumes that the problem is on the consumer's end, but we have to talk to someone higher-up who will believe us and who has the authority to do something other than just dispatch technicians or equipment to our homes.

reply to FutureX2001
A lot slower tonight:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 6.21Mb/s
running 10s inbound test (server to client) . . . . . . 8.93Mb/s
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address

reply to FutureX2001
I just called again tonight. The Tech Support person logged my call and had a supervisor call me back. He said that the reason for the slow speeds was that we were being transferred to an alternate FiOS line because of the problem. He said that they have had a group working on it, and they are replacing some equipment at the CO in Walnut. Estimated ETA is 3:00 am.
Since everything goes fine after 2:00 am, I suppose that we won't know until tomorrow.

Posted in the other thread, also: »[Southwest] Problem with Fios

reply to FutureX2001
I called today and they say ETA is tonight 7PM.

Yesterday evening my connection was for all intents and purposes dead -- I couldn't connect at all, and this was the worst it's been since this fiasco started. So I called Verizon again and they acknowledged there was an "outage" in my area (Torrance) which would be repaired by 10 p.m. That concluded by 4th call with Verizon on this issue.

Today, everything has been fine thus far. I'm hoping that this is the end to the saga.

reply to FutureX2001
try this speedtest server I went through same thing while after sandy only to realize it were the host's causing trouble not vzw network

while speedtest.net barely gave me 30-50 mbps this speedtest always gave me 100% speeds (New York server)

give it a try.

»spdtst-dlls.tx.centurylink.net/

The problem is that the connection is good to only some servers, seems like there's congestion along the way on Verizon's part. Some will be good and some will be bad.

I got this from that speed test you linked:
Download Speed: 72465 kbps (9058.1 KB/sec transfer rate)
Upload Speed: 2862 kbps (357.8 KB/sec transfer rate)
Latency: 201 ms
2/3/2013 9:54:29 PM

reply to mkaishar
everything seems to be stable now, they've been calling me back daily for the last week even on the weekend to confirm everything is good. it turned out to be a major problem on their end as suspected, now they said it was an issue with their routers, specifically what, i have no idea, but i am happy that it was resolved, puts my faith back in fios and their business support team, although it took a lot of pulling teeth, in the end it was resolved.