Did any Cablecon [sic] customers have 'Net problems last night?

BeastOfBodmin · #1 09.10.2007, 08:01

I was having problems connecting to some UK and US sites last night. .CH and .DE seemed fine.

For a period I could not open any connections at all.

traceroute was giving dodgy results. I had to resort to leeching from one of the open Wi-Fi routers within range of my PC.

Seems better now, though not 100%.

These appear to be involved (I've obscured my IP address):


	$ traceroute www.expedia.co.uk 1 X.Y.Z.A (X.Y.Z.A) 6.678 ms 16.212 ms 8.153 ms 2 ch-zrh01a-ra1-ge-1-1-0.aorta.net (213.46.171.49) 8.404 ms 27.942 ms 7.734 ms 3 ch-zrh01a-ra1-ge-1-1-0.aorta.net (213.46.171.49) 7.960 ms 8.208 ms 7.684 ms 4 * 213.46.171.61 (213.46.171.61) 12.841 ms 11.890 ms 5 de-fra01a-rd1-pos-14-0.aorta.net (213.46.160.161) 36.976 ms 21.577 ms 22.138 ms 6 213.46.160.242 (213.46.160.242) 100.222 ms 96.906 ms 99.445 ms 7 us-nyc01b-ri1-10ge-0-1-0-0.aorta.net (213.46.190.178) 95.908 ms 100.538 ms 95.571 ms 8 te-8-3.car2.newyork1.level3.net (4.78.164.221) 156.951 ms 149.984 ms 128.029 ms 9 * vlan69.csw1.newyork1.level3.net (4.68.16.62) 108.835 ms 122.922 ms 10 ae-62-62.ebr2.newyork1.level3.net (4.69.134.81) 109.977 ms 121.329 ms * 11 ae-2.ebr1.chicago1.level3.net (4.69.132.65) 138.152 ms 125.270 ms 126.116 ms 12 ae-68.ebr3.chicago1.level3.net (4.69.134.58) 125.855 ms 136.289 ms 126.548 ms 13 ae-3.ebr2.denver1.level3.net (4.69.132.61) 160.721 ms 156.463 ms 180.394 ms 14 ae-22-52.car2.denver1.level3.net (4.68.107.39) 148.799 ms ae-22-54.car2.denver1.level3.net (4.68.107.103) 151.565 ms ae-22-56.car2.denver1.level3.net (4.68.107.167) 1 .104 ms 15 sungard-net.car2.denver1.level3.net (4.79.82.2) 150.578 ms 159.193 ms 149.264 ms 16 denir4-vl-1.sgns.net (216.183.125.10) 149.942 ms 148.542 ms 149.492 ms 17 thnir4-ge-4-16-0.sgns.net (216.183.96.189) 188.867 ms 187.277 ms 186.254 ms 18 thnir2-vl-2.sgns.net (216.183.96.44) 184.940 ms 187.462 ms 194.324 ms 19 * * * 20 * * * ^C #Got bored! Those packets are on a guided tour of the world, looks like!

But this one works better


	$ traceroute www.google.ch traceroute: Warning: www.google.ch has multiple addresses; using 209.85.129.99 traceroute to www.google.com (209.85.129.99), 64 hops max, 40 byte packets 1 X.Y.Z.A (X.Y.Z.A) 6.643 ms 8.051 ms 8.295 ms 2 * * * 3 * * * 4 tix.net.google.com (194.42.48.58) 7.234 ms 9.576 ms 7.930 ms 5 64.233.174.34 (64.233.174.34) 17.538 ms 17.123 ms 23.804 ms 6 72.14.232.203 (72.14.232.203) 16.104 ms 15.685 ms 72.14.232.201 (72.14.232.201) 16.722 ms 7 72.14.233.206 (72.14.233.206) 22.428 ms 16.906 ms 18.097 ms 8 fk-in-f99.google.com (209.85.129.99) 16.011 ms 15.973 ms 16.468 ms

ElJeFe · #2 09.10.2007, 08:15

yup, ditto, probably a screwy DNS server or dodgy router. All's OK now.

nqnln · #3 09.10.2007, 10:25

Yes. that's good to know! I forwarded my wireless router last weekend, and thought it may have had something to do with my IP settings. Seems not, thanks.

bozothedeathmachine · #4 09.10.2007, 10:42

Actually, I'm a Sunrise subscriber and I had issues too. It could just be coincidence....

mkkangas · #5 09.10.2007, 10:58

.... or a CONSPIRACY!

Woodsie · #6 09.10.2007, 11:00

Yep, I couldn't get through to a lot of Aussie sites (though some worked). Looked like a routing issue. But it was all good again this morning.

Polorise · #7 09.10.2007, 11:05

Indeed .... upside is I got so p***ed off I got an early night ....

#8 09.10.2007, 11:30

On Cablecom, just a minor glitch seen here, when I got a couple of "no route to server" messages.

I am however running my own DNS setup, so maybe that had enough in cache to tide me over.

I did see similar a few months ago though, when I couldn't reach any sites in North America for most of a day.