Citywest routing this morning?

General Forums Tech
1

Anyone else having a problem with Citywest this morning?

$traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 173.194.33.0
traceroute to google.com (173.194.33.0), 64 hops max, 52 byte packets
1 firewall.localdomain (192.168.2.1) 1.771 ms 1.329 ms 1.161 ms
2 24.244.72.1 (24.244.72.1) 9.587 ms 11.046 ms 16.266 ms
3 65.65.244.24.scpe.citywest.ca (24.244.65.65) 11.658 ms 10.752 ms 20.008 ms
4 1.65.244.24.scpe.citywest.ca (24.244.65.1) 11.666 ms 10.993 ms 12.211 ms
5 204.244.10.233 (204.244.10.233) 36.603 ms 33.772 ms 31.823 ms
6 * * *
7 * ae1-0.vsb1.navigata.net (204.244.12.229) 32.315 ms 31.038 ms
8 six.sea01.google.com (206.81.80.17) 64.383 ms 34.332 ms 32.124 ms
9 66.249.94.212 (66.249.94.212) 40.079 ms 34.247 ms 31.980 ms
10 209.85.253.24 (209.85.253.24) 34.143 ms 40.892 ms 35.573 ms
11 sea09s01-in-f0.1e100.net (173.194.33.0) 35.750 ms 38.312 ms *

2

Looks like it’s down in Terrace. I spoke with a couple of other Terrace Citywest customers this morning and they were down too.

3

More importantly, why is it taking as much as 1.7 ms to “firewall.localdomain” : O

From Rupert the WeTel ip is on the fifth hop as well. taken @ 4:30 AM Tuesday morning. Pretty much the same, 11 hops and average 35 ms @ 173.194.33.x . What should I expect to see? google.ca is worse.

4

Looks like they’re routing common internet traffic over their Navigata link. It’s been a while but I thought their Navigata link was a seperate pipe in / out. Either that or someone messed up a routing table entry. :smile: Heavy response times from Rupert as well.

5

Navigata is Westel also.What was the other route? Still at a loss as to what is wrong with “Citywest routing” as the title suggests. Is Westel’s 204.244.10.233 a new route for Citytel? Are you on cable Meep?

6

Still on DSL. In PR I never noticed a route through Navigata before - for standard DSL.

7

Thanks. I asked cause I was curious to see why it seems to choke for you on the (69.176.191.6).
I have premium ADSL, but that shouldn’t make a difference. My route below… When I talked to a CityWest employee a couple weeks ago they said they are looking to have higher bandwidth packages available this summer. In negotiations or something like that…sorta tuned out after I heard higher bandwidth packages…off in fantasy land. Here’s to hoping…

8

Terrace issue was fixed yesterday, by reseting some equipment, apparently. There was another short outage in Terrace to update some routing info.

Still getting no reply after 204.244.10.233, but maybe that router just doesn’t do ICMP?

traceroute to google.com (173.194.33.9), 64 hops max, 40 byte packets 1 192.168.2.1 (192.168.2.1) 0.898 ms 0.318 ms 0.201 ms 2 24.244.72.1 (24.244.72.1) 8.913 ms 7.700 ms 7.891 ms 3 65.65.244.24.scpe.citywest.ca (24.244.65.65) 7.851 ms 7.840 ms 7.886 ms 4 1.65.244.24.scpe.citywest.ca (24.244.65.1) 8.015 ms 7.500 ms 7.312 ms 5 204.244.10.233 (204.244.10.233) 28.803 ms 55.503 ms 29.871 ms 6 * * * 7 ae1-0.vsb1.navigata.net (204.244.12.229) 34.980 ms 30.231 ms 32.033 ms 8 six.sea01.google.com (206.81.80.17) 36.981 ms 37.160 ms 33.504 ms 9 66.249.94.212 (66.249.94.212) 32.253 ms 34.720 ms 34.121 ms 10 209.85.253.24 (209.85.253.24) 32.710 ms 31.530 ms 36.178 ms 11 sea09s01-in-f9.1e100.net (173.194.33.9) 32.290 ms 34.981 ms 35.936 ms