Has this board been down for the past few days?

[blackram]

I've been having a ton of trouble connecting to this website for the past few days, I just thought the site was down, but it looks like there's been plenty of activity all around here. Did any of you guys have any trouble with the website timing out constantly, during the past couple of days?

I'm starting to get the feeling that it was just a problem with my ISP, because right now, I'm accessing it by connecting my laptop through my smartphone using my mobile data plan rather than my home Internet. Good thing my data plan is unlimited.

 

[paul mott]

I think there was one brief time I couldn't get on, but when I rebooted then it was fine and no problem since.

 

[mmad]

No problems on my end.

 

[slurp]

BR, do you use Bell for home ISP? I've been having a LOT of issues similar to what you described lately with Bell, replaced router and modem but now others in town saying they have Bell troubles. Like you I had to tehter to my phone to get some work (and play) stuff done. I'm ready to switch ISP and then I will be totally free of Bell. Cable has some attractive looking services, I'm thinking of going to 120Mb service. Then I'll have to learn to fap faster to the porn!

 

[blackram]

No, I am with Teksavvy, which connects through Rogers cable for its last mile. I looked at the traceroute and it looked like the last hop that was just before hubgfe.com was going into an infinite loop rather than reach HUBGFE. But when I went through my cellphone tether, the exact same last hop handled it properly. So I assumed that Teksavvy must've screwed up their routing tables. But just as I was about to open up a case with Teksavvy, I did one last traceroute, and this time it went through properly, which meant that I should be able access the website properly again. I tried it and it began working again. So Teksavvy must've discovered their own problem and fixed it in the meantime. So I never bothered to call them, but I have a feeling that they will likely screw up again in the future in exactly the same way. If it can happen once, it can happen again.

As far as Bell goes, yes, it's likely they've done similar things. I wouldn't hesitate to dump them. I used to be with them before, and though their service wasn't unreliable, it was full of annoyances, such as one time they used to throttle various services like bittorrents during certain times of the day, and they admitted to it too! And I was paying them $70/month for that crappy service. Rogers isn't much better most of the time either. This was actually my first ever problem with Teksavvy.

 

[mmad]

I use Bell Fibe unlimited and have been for about 10 months. Never had an issue other than my PC getting screwed up and having to do a restart. Seems any problems I have, maybe once every few weeks is corrected by a PC restart. I try to do one weekly but sometimes forget.
I had Bell DSL before and Fibe is, I think, far superior and don't have to worry about routers. The one that they supply does all the TVs and internet. Speed is excellent!

 

[mmad]

I use Bell Fibe and am very happy. I get 20Mbps download and 7.5 upload speed using speedtest.net

 

[Jingles]

I am with Rogers but I am thinking of switching to Teksavy. I tried to order Teksavy but they say I have to cut ties with Rogers first.

 

[Ryan1967]

I recently (2 weeks ago) switched from Bell to Primus, I wanted to stay on DSL since my phone ports are more convenient than my cable ports for wired connections. I know that DSL speeds to not match Cable speeds, but at the lower end (I am on 25 Mbps) Primus was the cheapest. Fibe is only to the node...the last mile to the house is a phone line and thus DSL.

 

[blackram]

Some weird issues, and this was the first time I've truly had any real problem with Teksavvy as far as I can remember. In fact, I don't think I've ever called Teksavvy's tech support yet. Even this issue got resolved before I could even call it in.

I did find some problem occurring with router, so I went and upgraded to a new one, but it looks like there were two separate problems occurring at the same time, one on Teksavvy's end, and one with my router.