O Canada! > Canadian > Bell Canada > Seeing massive connectivity problems today

Seeing massive connectivity problems today

I am also having issues with Fibe in Toronto. Connection went down twice, and there have been latency issues with many sites.

I started a smoke-ping test 5 minutes ago. Took me a few attempts - it first claimed I wasn't pingable...?

Does anyone have any idea if these hosts entries could be playing a role here?

127.0.0.1 ajax.googleapis.com
127.0.0.1 apis.google.com
127.0.0.1 clients1.google.ca
127.0.0.1 ssl.google-analytics.com
127.0.0.1 www.googletagservices.com
127.0.0.1 id.google.ca
127.0.0.1 plus.google.com

The first two of those are somewhat recent, the rest of them I've had for many weeks if not months. I have other google entries that I'm not suspecting (and are not including here) because I've had them listed for quite a while.

reply to sm5w2
Those power drains won't do nothin'. Must be the city of London just outside of Hamilton to blame. Same thing has been going on in Ottawa. Probably a warmer than usual winter but we still have plenty of snow to shovel.

reply to mclearn
Steve is still on an adsl based central office.

reply to sm5w2
Here's my smoke-ping test results page:

»/r3/smokeping.···2bb0.CA1

The results from this on-line test service are similar:

»just-ping.com/

When I started these tests around 3 pm, both were showing 100 to 200 ms ping results, and I was getting results from all 50 sites on the on-line test. Currently, I'm only getting results on 18 of those 50 - with the min - avg - max results generally in the 600 to 1200 ms time-frame.

Still have to re-load websites several times to get them to render.

Trying to open this Bell speed-test page:

»internet.bell.ca/index.cfm?metho···id=15561

And I get:

=========
Server not found
Firefox can't find the server at internet.bell.ca.
=========

My primary DNS server is 67.69.234.1, which appears to be functioning. After a few tries over 10 - 20 minutes I can bring the Bell speed-test page up. While it's loading, I see "sales.liveperson.net" appear transiently on my browser's bottom location bar. Doing a bit of searching turns up some strange things about this liveperson.net...

reply to sm5w2
I am in Chatham and having the SAME problems. Horrible connection all day. Modem lights are all green but nobody's home. Rebooted both my system and the modem THREE times, swapped cables/lines/filters. You name it. Webpages time out and I get error messages. What the hell is going on? I called technical support and we spent 45 minutes on the phone basically getting nowhere. He said everything was "fine" on their end. Glad to know I'm not the only one. I thought maybe my computer's DSL port was crapping out. Anyone know what's up? Weather related perhaps?

reply to sm5w2
Use these two dns servers 216.254.141.13 (primary)

208.67.222.222 (secondary)

reply to sm5w2
My connection seems to have gone on the fritz too. I'm thinking that it's weather related.

reply to sm5w2
I'm fairly certain this is not a DNS issue. My smoke-ping results look horrible, and that's got nothing to do with my DNS.

I've run dnsbench about a dozen times today, and have changed this PC's dns setting several times and it made no difference. I'm currently using these:

64.15.64.91 (Netelligent)
64.68.200.200 (easyDNS)
207.172.3.9 (RCN)

DNSbench measured them to be anywhere from .2 to .25 seconds and were 100% reliable. However, dnsbench tests 50 servers during the test, and after the test it says this:

------------
More than 20% of resolvers were unreliable?

Such a high percentage is suspicious: As you may have noticed, a relatively large number of the resolvers (12) benchmarked (more than one in every five) had apparent reliability problems. Since this is a suspiciously high number, it is more likely that the local network was busy and congested while the benchmark was running.
-------------

There is definately something wrong with Bell - more than the usual slowdown that I've been experiencing for a 13 months now.

reply to sm5w2
I use openDNS and it doesn't seem to help at all. I also know tons of people who are having issues today here in London, spanning a few ISP's that use Bell lines.

Things have been bad for me all day.

reply to sm5w2

reply to sm5w2
I'm in North York and have been seeing the same problems - but the Speed Test unsticks things and everything looks fine

Any http requests come back slowly, and when I used FTP I was getting about 15KB/s at best.

reply to sm5w2
Daryl in the Direct forum is still blaming "municipal approval" for the reason why they can't or haven't yet upgraded either the pipe going to or the Bell equipment in the apartment building serving my area.

This would be some sort of slam or remote located at 744 Wonderland Rd. South.

I told Daryl that Bell pulled off a big road-work project a month ago - digging a trench across the intersection of Wonderland and Commissioner's road - presumably to pull the fiber cable they laid A FRIGGIN YEAR EARLIER down commish road west. That work seems to be totally done for at least a month now.

Unless they haven't connected the other end yet to the hyde park CO (or some other point in-between) then I would really like to know what the hold up is.

I started the smoke-ping test again:

»/r3/smokeping.···2bb0.CA1

Brutal.

I have to wonder if I'm the only one on that remote or slam getting this performance. From a technical pov, how can I be? And yet, how many others would put up with performance like that before canceling and switching to cable (Rogers or TS)?

Maybe no one else in the apartment complex has internet service except you. The fact that dsl only works marginally doesn't help matters. The failing economy, the onset of a worldwide depression and the like just add to the factors stalling Bell's forward progress.