I currently have the Ignite 1 Gbps plan with 30Mbps upload speed. In actual use that 30Mbps upload speed turns out to be about 20Mbps. Nonetheless, whether 30Mbps or 20 Mbps, these are dinosaur speeds -- far too slow by orders of magnitude. I cannot reasonably perform a cloud backup or sync drives in the cloud, etc. Is there any way to get Rogers to increase my speed? If not, I'm off to Bell where I can get fiber to the home with a maximum upload (yes upload) speed of 940Mbps.
Definitely direct fiber is the best way to go, if you have it as an option.
Unfortunately, for a very large number of people, they do not have access to direct fiber 😞
Every person needs to see what is available in their area, and go with the best option.
(me for example. up to 1g rogers service.. or 5mbps DSL. Tough choice)
For now it's obvious that Bell FTTH is miles ahead of coax, Rogers is the better alternative against DSL we know that.
But in 5-10 years Bell's Fibre footprint will be almost Canada wide, and Rogers has to prepare for that, coax won't win that battle.The only reason they're doing so well is because Bell is not expanding fast enough.
I see Zoom and Join.me ads with people in conference calls communicating. -- just a dream for me!!!!
Held a webinar today using rogers. OMIGOD!! upload speeds were up to 6 mps but averaged around .1
Download speeds were 160 mps but I needed to upload and every few minutes I was disconnected from the video conference. it was
pathetic and unprofessional.
I hate Rogers
Welcome to the community!
Hate's a strong word :(, but given your experience I appreciate the strong feelings! We'll be happy to help identify what's going on. Just a few things to get started:
Does the intermittent upload speed occur consistently? Or only at specific times of the day?
Is this occurring with both a wired or a wireless connection?
Are you able to post a screenshot of your modem's signal levels? This is view-able by logging into your modem.
Given that RF level issues are the most common cause of performance variance we'll want to rule that out first if the issue is rooted deeper.