O Canada! → Canadian → Rogers > Extremely slow upload speeds and stalls

The slowness continues in the evenings here in Rural Ottawa.

Click on a web page and it stalls for up to several seconds and then wham, the page loads fast. Download something from a single site and it stalls, then chugs down at maximum rate.

Do a speed test, and the test stalls awaiting the ping test. Then stalls awaiting the download - then full speed download. Do the upload test and it stalls ... then crawls upstream at barely 100kbps (1/5th of the 500+ I get during the day) with lots of stalls midstream.

Rogers really is messing up something!

I've noticed that for the last couple of weeks that speeds are really slow at times. ( K-W) There are times when Rogers is slower then a 14.4 baud modem and other times I can't connect at all

Mt speeds (at home) go from 10 mbs to 25mbs to 5mbs

Lucky me I'm in an area where I cannot get DSL.

I have been feeling the website browsing glitches here for a while now... It's not DNS i have changed various servers.

Often times I'll click on a link and get a time out, then click try again and it will load in a split second...

This is Rogers Business 12/1 in downtown Toronto, btw.
--
BUCK FELL ,,!,,('-'),,!,,

Exact same problem I'm having... but this ONLY happens on HTTP traffic. HTTPS traffic and all other traffic forms (ESP packets, UDP etc) all work fine.

Makes me think Rogers transparent proxies are bogged down...

Also should note that this is only an issue during peak periods - problem starts to clear up around 11pm... which is why I think it's a load issue.

Rogers abandoned proxies back in Sep 2005 They couldn't manage the proxy farm adequately, and as they added more and more users they couldn't keep up with the size, speed and so on required. If I remember correctly the proxy farm was at YM so all traffic had to route via YM creating a huge load there and a major point of congestion. Many of us were really cheesed off with the proxy and disabled it long before since nothing actually loaded any faster, and then we'd get lots of out of date pages (when whoever wrote dynamic pages forgot to include instant expiry in the HTML. It was a real mess.

So, finally, halleluiah, they abandoned the farm.

There is definitely something up that is more or less only affecting HTTP traffic. Performance is fine over HTTPS and I can bypass all slowness and stalling by tunnelling.

For example, over an OpenSSL UDP VPN, I can sustain a solid down and upstream rate with no latency spikes to my data centre.

Over a 6in4 IPv6 tunnel to Hurricane Electric, I can sustain same.

Over HTTPS on standard IPv4, no issues.

It's really -only- HTTP that's slowing.

So Rogers is doing -something- to packets that are IPv4 port 80 and it appears they are currently having issues doing so.

Yup started at 7 pm tonight almost on the dot and it's impacting anything sending larger packets including https.

Small packets seem to go through without only small delays.

Latency to some locations is fine, but others is just a disaster. The most annoying things are the stalls and it's definitely not DNS causing this.

Yup, noticed exactly the same stuff here in Kanata yesterday and today was a bit better - it was beautiful on the weekend though ( »Speed upgrade? Almost.... ).
Perhaps this has something to do with Rogers turning on SpeedBoost (or whatever), giving each DOCSIS2 connection 25Mbps for the first few seconds and that is killing the network?

Horrible Night. Started around 6pm.

I can do speedtests and get a download rate of (14.3Mb / sec)
Upload Test (Failed to connect)

Trying to FTP images to my site. 128 KB image.
2 mins. 30 Images. 1 Hour to upload them all. Stalls out, reconnects, etc....

I am REEEEALLLY annoyed.

Having 1 server manage the connection and 3 pcs's behind it thought I would try directly connecting the PC's to the modem.
All 3. SLOOOOW.

Hope this is a temporary problem.

Not sure if this is related, but I've been getting pretty inconsistent (mostly poor) 3G speeds on my iPhone for the past couple of days on the Fido/Rogers network. 75% of the time I get 500Kbps-1Mbps speeds and sometimes it goes up to 2Mbps and up to 4.5Mbps once today.

The signal is good - I even tested right by the cell tower where I used to get ~5Mbps and now I got only 1.5Mbps, but I guess it could be another issue all together...

All quiet on the western front. Uploading at 200kB/s.

transfer aborted by user after transferring 5,046,272 bytes in 26 seconds

On Ultimate package, 25 minutes west of Ottawa.

Odd that Ted and/or SMC fixed us western country bumpkins first. Are you using your SMC as a standalone modem like myself, or as a wireless router combo?

FYI Rogers called me back on this. Support vetted my line as not responsible for my issues and dumped it up to IT.

IT called back today to say "we are aware of this issue and our ticket is being folded into a master ticket. No ETA, sorry".

I think these are unrelated issues.

I've started getting stalls here in London. Not sure if they were happening yesterday, but it's definitely happening today.
Just now my modem became unresponsive for a few minutes. Really annoying..

7pm and the stalls start all over again.

Nylon, Your issue is soemthing a little different.

Who the hell is Nylon? Got yer knickers in a bind there, sbrook?



***EDIT***

Very weird, Nylon shows up AFTER my post! Call me Kreskin or call sbrook at work!

Have been having the same problem here in Downtown Toronto for a few days. I recently upgraded my service from Extreme to Extreme Plus and had to change out my Motorola modem for the SMC modem. There is tremendous inconsistency and latency after 7pm.

Never had this issue with the Motorola. In fact did not have the issue on the SMC until Rogers pushed the new firmware onto it the day after I got it. Talked to Rogers tech. Level 1 is clueless as usual but did note down the problem and asked me to swap out the modem. I'll try that tomorrow.

Yeah, me too. I am in Downtown using Scientific Atlanta modem and experiencing the exact same issue (like a roller-coaster - slow, fast, slow, fast.....) In the evening after 7PM it's super slow with short blips of fast. I thought it was a virus and reformatted my XP machine Now it's brand new install and still slow. Something is wrong with Rogers network. May be we all got moved to that crappy Dupont hub by accident???

I'm relieved that everybody is experiencing this, I just got my PC back from a tech and thought it had something wrong because the internet was so slow, it's exactly like sbrook says, it stalls and then loads the page, but why is my download speed the same, around 14 mbds down and yet so slow to load a page?

Using SMC as a modem with a WRT-120n as router. DNS set to 8.8.8.8 and 8.8.4.4 from my tcp/ip settings on my onboard nic.

Currently on the 99.224.136.x range with a SNR of 37dB across all four channels.

Honestly I don't think everyone suddenly had their lines go bad. Sounds like a problem on Rogers end.

Tech I talked to said something to the effect of "Cisco has installed some new gear that isn't working properly."

Also, some good news. I asked about standalone DOCSIS 3.0 modems.

Tech said "we had a bunch from Cisco. They all worked and then Cisco did a remote firmware updated on them all to fix a minor issue and it ended up seriously breaking them and they all had to be swapped out."

He did say that there are -definitely- standalone D3 modems from Cisco in the pipe though.

Likely this, or a variant:

»www.cisco.com/en/US/prod/collate···a168.pdf

That's GREAT news, the part about stand alone modems. I hope whomever made the call for this POS SMC combo job got fired, how schtuped can one be? Unfortunate Rogers isn't going with the tried and true Toshiba product (Motorola SB6120 SURFboard DOCSIS 3.0 eXtreme Broadband Cable Modem) especially after seeing how well the test run went with Cisco.... not!

Hey everyone,

Rogers is definitely up to something.

I have a traceroute from yesterday to 192.88.99.1:

traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 52 byte packets
 1  172.16.254.1 (172.16.254.1)  1.183 ms  0.655 ms  0.519 ms
 2  10.8.180.1 (10.8.180.1)  7.353 ms  7.085 ms  7.302 ms
 3  69.63.243.77 (69.63.243.77)  9.013 ms  8.871 ms  8.059 ms
 4  so-4-0-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.82.97)  8.647 ms  8.522 ms  12.196 ms
 5  64.71.241.118 (64.71.241.118)  22.218 ms  23.495 ms  21.640 ms
 6  ash-core-2.tengigeth8-0-0.swip.net (206.223.115.161)  21.954 ms  22.386 ms  26.031 ms
 7  cbv-core-3.pos0-4-2-0.swip.net (130.244.207.209)  104.063 ms  104.679 ms  104.505 ms
 8  cbv-core-2.tengigabiteth2-2.swip.net (130.244.52.229)  103.430 ms *  103.387 ms
 

Just now, my D3GN rebooted several times. Now that it's back up, my trace looks like this:

 1  172.16.254.1 (172.16.254.1)  5.161 ms  0.881 ms  0.642 ms
 2  10.18.0.1 (10.18.0.1)  6.595 ms  6.775 ms  6.023 ms
 3  69.63.243.85 (69.63.243.85)  6.243 ms  7.378 ms  7.806 ms
 4  69.63.250.21 (69.63.250.21)  8.890 ms  12.707 ms  8.572 ms
 5  64.71.241.110 (64.71.241.110)  21.178 ms  22.698 ms  21.655 ms
 6  ash-core-2.tengigeth8-0-0.swip.net (206.223.115.161)  25.475 ms  22.761 ms  22.401 ms
 7  cbv-core-3.pos0-4-3-0.swip.net (130.244.207.205)  103.722 ms  103.557 ms  104.334 ms
 8  cbv-core-2.tengigabiteth2-2.swip.net (130.244.52.229)  104.113 ms *  105.793 ms
 

So I've definitely been moved. Hoping this will solve my issues and hopefully same for you all.

Someone (can't remember where) said that the 6120's don't actually pass certification testing on the Rogers network. If Rogers is using Cisco CMTS (and I think they are) going with the Cisco modems makes sense. You'd assume Cisco would vet them fully as interoperable.

I have no issues taking a Cisco modem - especially if it means getting rid of this SMC.

As I understand it, it's not that the 6120 didn't pass certification, just that SMC made a deal Rogers couldn't refuse, but it required either exclusivity or a huge bulk purchase of the SMCD3GNs

Put politely, SMC had a bunch of junk that should have gone in a landfill and sold it in bulk to Rogers, who is sticking us with it.

I don't know why I even bother anymore..

Email sent 11/24/2010 4:07PM.
Reply received 11/27/2010 1:39pm
»pastebin.com/fz1NBjgd

Luckily, the problem seems to have resolved itself, apparently without the assistance of anyone at Rogers..

What part of Ottawa are you in, random? I like to track what cities and areas of the city Rogers/SMC(firmware pushes?) works on. They fixed Ottawa West (west of Kanata) last week (numerous positive reports) and *some* evidence of College Square area.

*****EDIT*****

I see you are in London from an earlier post!