You may experience poor service during periods of rain (or even several hours after the rain has stopped), or in the spring when all the snow melts quickly. A common reason for this is that the wires carrying your telephone service are wet someplace. For example, a junction box on a pole or a manhole underground can fill with water or become damp. Or lines underground are slightly damaged with the sheathing (the covering) over the wire is broken, exposing the copper inside to moisture. When your lines get wet, service degrades greatly. Your modem is having trouble maintaining a certain level of sync, so it's dropping back to the best speed it can maintain. In some cases, your speeds might be slower than dial-up or you might lose sync completely! Over a period of time, sometimes hours or even days, the water drains away or dries out and service returns to normal.
This can be troubling to fix, since in dry conditions there is no problem. So you need to be prepared to call as soon as the problem starts. If you wait until it goes away, Bell will not be able to find the problem as easily, if at all. Use a payphone, cellphone, or neighbour's phone if you need to. If you can call using your own phone, the operator may notice your voice quality is indeed poor and (hopefully) get you help right away.
There are two ways to approach Bell about this:
•Call 310-SURF and have them dispatch a tech to investigate. They may or may not dispatch a technician, depending on workload and their opinion of your situation.
•Call 611 if your voice service is poor (static, poor signal or sound volume, etc) and have them dispatch a tech to investigate. Since the quality of voice service is regulated by the government through the CRTC, Bell has to fix these problems right away. And when they fix your voice service, often the solution will fix your internet service, too. The CRTC does not regulate the quality of service for internet.
Remember this problem will probably not get fixed with the first call. Be persistent and you'll have this problem fixed.
Feedback received on this FAQ entry: