For customers on Verizon Fios, particularly on the east coast, we have noticed that the connection speeds to our data center (located in California) do not approach the speeds that are achieved for connections that are more local to the area.
Sometimes due to network issues along the path from an ISP to Backblaze's servers, customers on these networks may not max out their connection speed to our datacenter. You may have heard of some similar performance issues on Verizon Fios connections with Netflix. The issue is very much the same. Unfortunately, there is nothing that we can currently do to resolve this issue, as it is one that lies with either Verizon or their peering partners.
Backblaze does not throttle your connection: The Backblaze client encapsulates data in 10MB chunks, uses https connections, uses a single connection at a time, so latency can play a very large role in overall backup speed.
In most cases it is recommended to leave the Performance Settings of the program set to Auto-Throttle, so it can match the strength of the connection & increase Threads automatically, uploading as fast as the connection allows.
However, if you wish to configure the Performance Settings manually, would advise the following:
1. Set the program to 1 Thread and allow it to run uninterrupted for 24 hours, notating the speed reported by the Performance Setting in that time.
2. Use our speedtest here: https://secure.backblaze.com/online-backup-speed.htm a few different times in that 24 hour period to get an average speed to our servers
3. Plug the info from 1 & 2 into this equation:
Mbps speed / Mbps on 1 Thread = X Threads[round down]
That is, " Mbps of speed on network divided by Mbps reported over 1 Thread equals number of threads, round down, for stable transfer."
We have had some customers report improved upload speeds by using the Verizon Speed Optimizer:
As well as a few where using a VPN allowed alternative pathing, allowing a more stable connection.