A few hours later, I’m still experiencing problems with my cable internet connection, to the point I find it unusable. Downloading web pages takes up to a minute, and I can’t watch even a short YouTube video without it stopping at least a few times.
However, when I tether my iMac to my iPhone speeds are adequate and page and video load times aren’t a problem. Here are my speed tests from my iMac over my iPhone.
It feels like a router somewhere is dropping packets. While the speeds have only a minimal measurable difference, the load times when actually using the two different connections are marked. Over my Northwestel cable modem I am forcing myself to be patient as pages stutter in loading and YouTube video feeds stall regularly; over Bell, the pages and videos are loading in a smooth, consistent fashion.
(Non-geeks, stop reading now!)
A few friends who also have cable modem accounts but aren’t having problems have shared their traceroutes with me. We’ve tested to Northwestel’s web site host in San Jose, California. Most of the route is the same, save for the fifth hop. My fifth hop is an IP address that does not have reverse-lookup configured, 22.214.171.124. Their fifth hop is a different address, 126.96.36.199, which is properly configured with the correct reverse lookup of so-410-0-drt02-edtnabss.nwtel.org.
This fifth hop is a router connecting to the outside world, a router in Edmonton: 188.8.131.52 (core3-edmonton_3-0-1.net.bell.ca).
I’m not sure why Northwestel would be routing some cable customers differently than others, but this seems to be the case, and there appears to be a problem in the routing between whatever Northwestel device handles the IP address 184.108.40.206 and the device that handles 220.127.116.11 for Bell.
What’s also interesting, is that very different routing scenarios may be applied cable modems users depending on… something. And, depending on which routing scenario is applied to you, your traffic will either be routed through the IP address that’s causing me problems (18.104.22.168) or the one that’s not (22.214.171.124).
You can get new and/or different routing by plugging different devices into your modem or turning the devices on and off.
First, the problem routing scenario. This one will get you routed through 126.96.36.199. (Let’s call it the Sad IP.)
IP Address: 188.8.131.52 (for example; notice the C class difference)
Subnet Mask: 255.255.255.0
Router Address: 184.108.40.206
That’ll get you routed to http://www.nwtel.ca like so…
- 10.0.1.1 (10.0.1.1) 2.286 ms 1.113 ms 1.131 ms
- 10.130.63.254 (10.130.63.254) 8.458 ms 13.277 ms 7.430 ms
- vlan-600-crs02.nci.whthyttv.nwtel.org (220.127.116.11) 8.586 ms 10.352 ms 8.042 ms
- 18.104.22.168 (22.214.171.124) 8.556 ms 8.890 ms 8.410 ms
- 126.96.36.199 (188.8.131.52) 35.620 ms 34.291 ms 32.578 ms
- core3-edmonton_3-0-1.net.bell.ca (184.108.40.206) 40.843 ms 39.466 ms 43.286 ms
- core4-vancouverbg_pos3-0-1.net.bell.ca (220.127.116.11) 50.536 ms 51.032 ms 56.214 ms
- core2-seattle_pos3-0-0_core.net.bell.ca (18.104.22.168) 60.074 ms 61.366 ms 57.041 ms
- (it’s the same from here)
Then there’s the routing scenario that seems to work. This one will get you routed through 22.214.171.124. (Let’s call it the Happy IP.)
IP Address: 126.96.36.199 (again, compare the C class)
Subnet Mask: 255.255.240.0
Router Address: 188.8.131.52 (notice, totally different gateway)
That’ll get you to http://www.nwtel.ca like so… (I’ve bolded the only different in each route)
- 10.130.63.254 (10.130.63.254) 5.879 ms 6.186 ms 5.298 ms
- vlan-600-crs02-hfc-whthyttv.nwtel.org (184.108.40.206) 8.229 ms 11.547 ms 7.604 ms
- 220.127.116.11 (18.104.22.168) 7.968 ms 6.651 ms 9.691 ms
- so-410-0-drt02-edtnabss.nwtel.org (22.214.171.124) 31.365 ms 31.717 ms 31.468 ms
- core3-edmonton_3-0-1.net.bell.ca (126.96.36.199) 39.749 ms 37.944 ms 38.501 ms
- core4-vancouverbg_pos3-0-1.net.bell.ca (188.8.131.52) 49.958 ms 50.293 ms 50.341 ms
- core2-seattle_pos3-0-0_core.net.bell.ca (184.108.40.206) 50.319 ms 54.457 ms 47.679 ms
- (it’s the same from here)
I’ve been in contact with a very helpful Northwestel network engineer on this issue and he has confirmed that both IP addresses, 220.127.116.11 and 18.104.22.168 are different interfaces on the same router in Edmonton. He wasn’t able to identify precisely what may be causing me problems.
However, he has committed to helping me more over the next few days as I spend more time investigating the matter and collecting more data.
I’m posting this just in case anyone else is having similar problems, or can provide additional insight into what may be causing me problems when my traffic is being routed through that one network interface on that router.