dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1546
share rss forum feed


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

Anyone having problems in the Riverside County area?

I'm located in Perris/Moreno Valley and sometime last week I noticed speed tests are suddenly erratic, sometimes they'll just flat out report a download error (speedtest.net for example).

Netflix suddenly stops after a few seconds and constantly buffers. Sometimes my speeds go to their normal 82-84mbps down, sometimes it reports 30mbps down or less. I've tried different PCs (ethernet), and resetting the ONT.

Next step is to take my WNDR3700 out of the equation, before I do that I was wondering if anyone else is having similar problems.



houkouonchi

join:2002-07-22
Ontario, CA
Reviews:
·Verizon FiOS

I would think even in Perris you are still routed through L.A. which would be where I go through in Ontario. I haven't had any issues at all. Are you on ethernet to the ONT or coax with a bridged actiontec?
--
300/150 mbit Bonded Verizon FiOS connection FTW!



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

1 edit

ONT -> Ethernet -> Netgear WNDR3700 Router
The actiontec is after the netgear only to feed data to the STBs.

It's been setup this way for ~2years now with no issues. If you go to SpeedTest.net and run a test to the Irvine (Hosted by GoFiber) server does it work for you? I just get an error.

Netflix bugs out after a few minutes and start buffering on and off even at low quality. Anything sensitive to streaming seems to give me issues.

Ping seems to be off as well, I used to get sub 10ms ping times to nearby servers.

Some speed tests:

SpeedTest.net (DreamHost - LA)




SpeedTest.net (Gofiber - Irvine)
Fails to load

SpeedTest.net (Internode - LA)



SpeedTest.net (Charter - Monterey Park)



SpeedTest.net (Atlantic Metro - Los Angeles)






PingTest






Verizon's speed test gives me the following:

SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 32.57Mb/s
running 10s inbound test (server to client) . . . . . . 23.45Mb/s

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 157440 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 = 13.17 msec; the Packet size = 1460 Bytes; and
There were 465 packets retransmitted, 1880 duplicate acks received, and 2325 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.21 seconds (1.90%) of the time
This connection is receiver limited 3.37% of the time.
This connection is sender limited 64.99% of the time.
This connection is network limited 31.64% 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


RedCaliSS
Premium
join:2004-08-21
Murrieta, CA
reply to FutureX2001

I'm just down the road in Murrieta and I have not noticed any issues in the past week on either of my fios lines. (have two distinct fios installs here)



houkouonchi

join:2002-07-22
Ontario, CA
Reviews:
·Verizon FiOS
reply to FutureX2001

said by FutureX2001:

------ Web100 Detailed Analysis ------
Client Receive Window detected at 157440 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.

Your receive window is super small at only 150 kilobytes. Mine is 3 megabytes (my upload results are super low cause i am doing a lot of uploading while i did the speedtest:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [8192]
running 10s outbound test (client to server) . . . . . 11.05Mb/s
running 10s inbound test (server to client) . . . . . . 149.73Mb/s
 
------ Client System Details ------
OS data: Name = Linux, Architecture = amd64, Version = 2.6.39.4-web10g
Java data: Vendor = Oracle Corporation, Version = 1.7.0_09
 
------ Web100 Detailed Analysis ------
Client Receive Window detected at 3145728 bytes.
100 Mbps FastEthernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Alarm: Duplex mismatch condition found: Host set to Full and Switch set to Half duplexD
 

I think something is messed up with the irvine test server as it hung for a very long time and then gave me super low results:



Your latency seemed oddly high to me though. Sometimes speedtest.net is not very accurate for that though. Can you show me a traceroute to 208.97.141.21 (that is the DH speedtest.net server that you got 19ms to). I usually get 3-8ms to it. Probably would if i was not uploading a ton ATM:


--
300/150 mbit Bonded Verizon FiOS connection FTW!


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

I'm going to have to keep an eye on it over the next few days, today's test seemed fine:



Pinging 208.97.141.21 with 32 bytes of data:
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=7ms TTL=252
Reply from 208.97.141.21: bytes=32 time=13ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=42ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=18ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=14ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=9ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=20ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=11ms TTL=252
Reply from 208.97.141.21: bytes=32 time=21ms TTL=252
Reply from 208.97.141.21: bytes=32 time=16ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252
Reply from 208.97.141.21: bytes=32 time=12ms TTL=252
Reply from 208.97.141.21: bytes=32 time=8ms TTL=252
Reply from 208.97.141.21: bytes=32 time=10ms TTL=252

Ping statistics for 208.97.141.21:
Packets: Sent = 47, Received = 47, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 42ms, Average = 12ms



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS
reply to houkouonchi

I ran the verizon speed test again... didn't change anything on the computer:

SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 32.44Mb/s
running 10s inbound test (server to client) . . . . . . 57.97Mb/s

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 281600 bytes.
45 Mbps T3/DS3 link found.
Link set to Half Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 12.25 msec; the Packet size = 1460 Bytes; and
There were 307 packets retransmitted, 2727 duplicate acks received, and 3035 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 receiver limited 5.17% of the time.
This connection is sender limited 76.47% of the time.
This connection is network limited 18.36% 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
Information: Network Address Translation (NAT) box is modifying the Client's IP address



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

Just an update, the problem went away for 3 weeks until tonight:




Verizon
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 34.32Mb/s
running 10s inbound test (server to client) . . . . . . 2.94Mb/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

mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to FutureX2001

I'm in Walnut and problems still happening even with fios business, been on the phone with their support, they say they are not sure where the problem is and when it will be resolved.
packet loss and dropped connectivity and kilobit speeds always at night...I sure hope they fix it soon



dave49er

join:2004-05-05
Walnut, CA

I'm in Walnut, also. I've been having problems since around Thursday. I have the 50/25 package. Right now I'm getting 0.022 Mbps / 0.06 Mbps. I've been getting about 58/35 from 2:00 am until about 10:00 am, then it starts dropping all day, until 2:00 am, when it's suddenly blazing fast. The pattern's been repeating daily.

I had a similar problem last July. It took them several days to realize that they had a problem somewhere, then they went to work on it and it suddenly cleared up.

They sent me a new router. It's supposed to arrive tomorrow...


andyjai

join:2001-09-12
Rowland Heights, CA

Did they tell you what was the problem you had last July? Did a tech came and fix it or was is internal fixing?



dave49er

join:2004-05-05
Walnut, CA

It was a failure of their equipment. Except for today, my upload speed has been unaffected, only the download speed. As of now, my speeds are 0.249 / 35.27, so my upload seed is back. We'l see what 2:00 am brings.



dave49er

join:2004-05-05
Walnut, CA

1:58 am. Back to full speed, probably until about 10:00 am if the pattern holds.



FutureX2001

join:2000-10-25
Perris, CA
reply to FutureX2001

Well at least I know I'm not alone, I wonder if I should even bother calling.


mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS

1 edit
reply to FutureX2001

Click for full size
Run: 2013-01-30 02:46:35 EST
Download: 3789 (Kbps)
Upload: 14004 (Kbps)
In kilobytes per second: 462.5 down 1709.5 up

I pay for business 25/25 and I am getting this


dave49er

join:2004-05-05
Walnut, CA

Got my new router today. As I already knew, it did nothing to solve the problem. In fact it added others. It killed my DLNA streaming from wired to wireless. But through Google, I got that sorted out.

The second person I talked to, about 10 minutes ago, says it is now a known issue. It started in Pomona, and is affecting the whole state of California. They have been advised that the problem will be fixed tomorrow. Let's hope so.


mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to FutureX2001

It will be fixed tomorrow morning and broken tomorrow night

The problem is plain and simple, they oversold and did not build it to support the overload.

I think every VZ customer should start calling in an filing a complaint!

Who here has friends in the media, it would make for a great story.


knarf829

join:2007-06-02
kudos:1

said by mkaishar:

It will be fixed tomorrow morning and broken tomorrow night

The problem is plain and simple, they oversold and did not build it to support the overload.

Do you have any proof of this? This is not cable. Someone with more tech details may weigh in here with the exact specs, but I believe it is highly unlikely that - if no hardware is broken - users could saturate the FiOS backbone.

More likely that there's a broken piece of equipment that is limiting the amount of traffic and you're seeing symptoms during peak hours than it being an unsolvable systemic problem.
Expand your moderator at work

mkaishar

join:2000-12-20
united state
Reviews:
·Verizon FiOS
reply to mkaishar

Re: Anyone having problems in the Riverside County area?

And my proof is right here: like i said during the day everything is working fine, we will see this evening again and if I am wrong, egg on my face, but if I am right, then VZ needs to fix their congestion issues, especially for business customers, we're not just watching youtube or netflix

Speed Test #103923279 by dslreports.com
Run: 2013-01-30 12:41:05 EST
Download: 29995 (Kbps)
Upload: 24892 (Kbps)
In kilobytes per second: 3661.5 down 3038.5 up

Expand your moderator at work


FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS

1 edit
reply to FutureX2001

Re: Anyone having problems in the Riverside County area?

Took another one just now, this is on the 75mbps package.

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [65536]
running 10s outbound test (client to server) . . . . . 37.52Mb/s
running 10s inbound test (server to client) . . . . . . 24.93Mb/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 283136 bytes.
45 Mbps T3/DS3 link found.
Link set to Half Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 10.56 msec; the Packet size = 1460 Bytes; and
There were 484 packets retransmitted, 1363 duplicate acks received, and 1801 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 0.42 seconds (3.81%) of the time
This connection is sender limited 47.46% of the time.
This connection is network limited 51.93% 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
Information: Network Address Translation (NAT) box is modifying the



FutureX2001

join:2000-10-25
Perris, CA
Reviews:
·Verizon FiOS
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

Expand your moderator at work


mozam

@verizon.net
reply to FutureX2001

Re: Anyone having problems in the Riverside County area?

Having issues in Torrance CA. Every evening around 4pm to whenever. First noticed Mon eve. Seems ok in the day. I've called every night to voice complaint. Get the same story, will be resolved by 10:30 pm. When everyone starts going to bed?


JohnyDr

join:2013-01-30

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.



dave49er

join:2004-05-05
Walnut, CA
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.



Lloyd

@verizon.net
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.