Child Item

Site Totals

61489 Questions Answered 271 Categories

Slow upload speed on evenings for almost 2 months now on 75/35 fios

somebody PLEASE help

up until midday I get 35 to 40mbit upload no problems, then at evenings it goes down! DOWN DOWN! I was lucky on this one I've had it as low as 0.5mbit..

I've contacted verizon multiple times, they swaped the ONT, balanced the BON and still NOTHING

I'm in an area where the only provider is either FIOS or , and I'm considering satellite if they can fix my low upload speeds!

Broadband Speed Test

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [32768]
running 10s outbound test (client to server) . . . . . 5.85Mb/s
running 10s inbound test (server to client) . . . . . . 83.77Mb/s

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
45 Mbps T3/DS3 link found.
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 = 23.15 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.01% of the time
This connection is receiver limited 4.93% of the time.
This connection is sender limited 94.6% 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 [{edited for privacy}] but Client says [192.168.xxxxx]

Comments

dvernissi

another test, this at 10:28 pm... it's getting worse

Broadband Speed Test

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [32768]
running 10s outbound test (client to server) . . . . . 2.73Mb/s
running 10s inbound test (server to client) . . . . . . 54.84Mb/s

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261120 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 = 23.75 msec; the Packet size = 1360 Bytes; and
There were 71 packets retransmitted, 2086 duplicate acks received, and 2121 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 8.32% of the time.
This connection is sender limited 82.02% of the time.
This connection is network limited 9.66% 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 [xxxxxxxxxxxx] but Client says [192.168.xxxxxx]

Hubrisnxs

your send buffer is really REALLY low. You may want to run the fios optimizer, and see if you can increase it

Verizon Online -- FiOS Speed Optimizer

dvernissi

my send buffer is fine for what I do and the type of data I upload, as I said in the 1st post, I can get the 35mbit upload no problem during the day, the problem is towards the afternoon and evening!

Hubrisnxs

Fios Bandwidth Restrictions? - Verizon Fiber Optics | DSLReports ...

the discussion has been had before.

A properly optimized Windows PC will have a default send window size of 261360 bytes (called SendBufferSize in the Verizon Speedtest results screen).

According to a senior VZ tech

dvernissi

I keep losing my forum post.

ok, still, could anyone please explain why, with my meagle 32k sendwindow I get 35mbit up during the day but cannot get more than 10mbig up towards the evening and it goes down to less than 1mbit at midnight?

so this isn't a provisioning problem, it's a load problem in my area, I've contacted verizon multiple times and they can't fix it!! I'm out of ideas honestly

Hubrisnxs

if you're using windows auto size feature, then that would explain it.

if you think it's a load problem then what you want to do is post some traceroutes.

Do traceroutes during the day when everything is wonderful. and then do some at night when it's bad.

compare and contrast.

dvernissi

here we go, 10:20pm: also set the SendBufferSize to recommended so people would get off my back about it. Analysis information:

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

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

------ Web100 Detailed Analysis ------
Client Receive Window detected at 66792 bytes.
45 Mbps T3/DS3 link found.
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 = 10.96 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.02% of the time
This connection is receiver limited 39.35% of the time.
This connection is sender limited 60.15% 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

Hubrisnxs

This also stands out to me. 45 Mbps T3/DS3 link found.
Link set to Full Duplex mode

45 is a little low of a link to be handling a 75 mb connection.

Unfortunately that isn't something peers in a forum can fix, you might have to re-engage Verizon.

Point out that you've been sent a new router, you are hardwired, you have optimized and are testing at their site, and getting poor speeds, and that this sticks out to you "45 Mbps T3/DS3 link found."

then ask if they have network tech's available that can look into that, A network tech won't likely speak with you, they are there to support other tech's, but I think it wouldn't hurt for one to take a look. So that means either a call or a chat support session, or if you've had bad luck both ways, try their twitter support. it's exceptional.

dvernissi

the connection I have is a gigabit to my router and the router is connected to the ONT as 100 full duplex, no clue where this this 45 is coming from.

I'm just trying to figure out if anyone else is suffering the same problems as me, which is, perfect network during the day and awful at night 😞

Jb1677

I have the same basic problem though mine is more sporadic. Upload is basically unusable most of the day, Verizon simply has me run speed tests at various sites and then tells me "see all is well"

I have a tech coming again tomorrow (apparently on my dime) for one last ditch effort before I bolt

lamarchemj

Check to see if your router has QOS. I had a similar problem and found that my router was actually preventing the maximum upload speed as the QOS service was only set to support 5Mb upload.

Originally I was only getting 4.5Mbs upload even though I had purchased 50/25 Quantom. After changing the QOS service upload value from 5 to 30, I am now reliably getting 59Mbs down and 29Mbs up using speedtest.com.

Also, I found that my wired clients were not getting the advertised throughput until I ran the Verizon Broadband optimizer. My IPADs got the full 59/29 as soon as I fixed the router, no special tweaks needed.

My gateway / router is a Asus RT-N66U.

-Mike

Headhunter6

Same issue here with very slow uploads on all devices in the house. As with others, I've done the optimization, reset the router, reset the ONT, reset DHCP, turned WMM/QoS on and off, and even tried different FIOS Routers and via ethernet cable. All the same -- slow, slow upload speed and timing out for any upload greater than about 750kb. Verizon phone customer service tried all the basic things--line checks, remote ONT reset, and about a bizzilion speed checks, with no success. So today a Verizon Tech came to the house and manually reset everything, checked the household wiring, and then called his upper echelon support.

At first they said they didn't see a problem--all the lines seemed ok. But the Tech at my house could not upload anything bigger than 1mb on his own devices. So they thought maybe it might be something called a "bad pong" (this, I take it is a network card of some form up at the central office). But reseting the pong did not work. The upstream tech could indeed see that packet loss on the upload was high, but did not know why. So they decided to do something they call "kick the "key key"" (maybe "kick the kiki"?). Even the Verizon tech at my house did not know what a "ki ki" is or where such a device might be found. But, apparently, kicking the ki ki is something that can only be done during the nightime hours.

So here I sit, hoping that this ki ki kick works. If not, I have no clue.

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

------ Client System Details ------
OS data&colon; Name = Windows 7, Architecture = x86, Version = 6.1
Java data&colon; Vendor = Oracle Corporation, Version = 1.7.0_21

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
10 Mbps Ethernet 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 = 30.2 msec; the Packet size = 1452 Bytes; and
There were 75 packets retransmitted, 1480 duplicate acks received, and 954 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 7.09% of the time.
This connection is sender limited 86.28% of the time.
This connection is network limited 6.63% 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

Headhunter6

Well, kicking the Kiki dd not work. Still no upload greater than about 750kb. Anything over just times out. Even web surfing has slowed down (despite still good download speeds) because of the delay in sending page requests and the back-forth communication between the browswer and the server.

What now? And just to make sure I'm not crazy, I double checked using my iphone on wifi and then on 3G. The wifi stopped dead when sending an e-mail with a pic, whereas the 3G sent it in a jiffy. I also tested sending the e-mail to each of my several e-mail accounts with different providers, and uploading the photo to dropbox, CX, Google Docs, and MS Skydrive. All uploads or e-mails on the fiber failed. But all on 3G went just fine.

Trust me Verizon, this IS a problem.

[Deleted User]

Hi Headhunter6,

Your issue has been escalated to a Verizon agent. Please go to your profile page for the forum and look at the top of the middle column where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.

Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. Please keep all correspondence regarding your issue in the private support portal.

Headhunter6

And it just keeps getting worse. So slow now that even downloads are slow because the page requests can't get out. See this incredible Network Diagnostic Test !

Analysis information:

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

------ Client System Details ------
OS data&colon; Name = Windows 8, Architecture = x86, Version = 6.2
Java data&colon; Vendor = Oracle Corporation, Version = 1.7.0_21

------ Web100 Detailed Analysis ------
Client Receive Window detected at 540160 bytes.
10 Mbps Ethernet 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 = 20.42 msec; the Packet size = 1460 Bytes; and
There were 220 packets retransmitted, 1428 duplicate acks received, and 1624 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 14.87% of the time.
This connection is sender limited 72.78% of the time.
This connection is network limited 12.34% 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

Child Item