sent zen an email this morning about the issue, and with tracerts. they replied

"Hi,

Thank you for the trace routes. We are aware of the issue and are looking into
this matter. However this is not an issue on our network but we will endeavor to
try and resolve it.

Regards,"

got home just now and pings are back to normal, top stuff zen !

Yeah, I'm suffering too.

Tracing route to 194.146.193.203 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 18 ms 17 ms gauthier-dsl1.hq.zen.net.uk [62.3.82.17]
3 18 ms 18 ms 18 ms lotze-ge-0-0-1-136.hq.zen.net.uk [62.3.80.137]
4 18 ms 17 ms 17 ms no-dns-yet-62-3-80-78.zen.co.uk [62.3.80.78]
5 23 ms 25 ms 26 ms suarez-so-0-0-0-0.te.zen.net.uk [62.3.80.62]
6 104 ms 104 ms 104 ms ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
7 106 ms 107 ms 104 ms 194.146.193.202
8 104 ms 103 ms 106 ms 194.146.193.203

Trace complete.


It seems like hop 6 - ge3-0.pr1.lhr1.uk.above.net - is always the problem. This has been happening for 2 weeks. Is this a case of zen routing it there ?

A friend of mine on zen is having the exact same problem.

hmm spoke to soon am now getting it with above.net

Looks alright here (interleaved connection);

Tracing route to 194.146.193.203 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  cisco [192.168.1.1]

  2    30 ms    29 ms    25 ms  galen-dsl1.hq.zen.net.uk

  3    26 ms    26 ms    29 ms  deleuze-ge-0-1-0-184.hq.zen.net.uk

  4    35 ms    34 ms    36 ms  suarez-so-0-0-0-0.te.zen.net.uk

  5    47 ms    37 ms    42 ms  ge3-0.pr1.lhr1.uk.above.net

  6    38 ms    41 ms    39 ms  194.146.193.202

  7    38 ms    41 ms    41 ms  194.146.193.203

Trace complete.

Me too....

Tracing route to 194.146.193.203 over a maximum of 30 hops

1 47 ms 99 ms 99 ms 10.0.0.138
2 26 ms 26 ms 27 ms gandhi-dsl1.wh.zen.net.uk [62.3.83.5]
3 27 ms 26 ms 27 ms erazmus-ge-0-0-1-3.wh.zen.net.uk [62.3.80.197]
4 34 ms 41 ms 33 ms lorenz-so-0-1-0-0.te.zen.net.uk [62.3.80.45]
5 35 ms 34 ms 34 ms ge9-0.mpr2.lhr1.uk.above.net [195.66.226.76]
6 35 ms 34 ms 33 ms 194.146.193.202
7 35 ms 33 ms 34 ms 194.146.193.203

Trace complete.

Interleaved connection.

Well it appears not to matter whether or not we know how the internet works.
It has been fixed despite our operational ignorance.

1 * * * Request timed out.
2 27 ms 28 ms 27 ms gauthier-dsl1.hq.zen.net.uk [62.3.82.17]
3 26 ms 36 ms 28 ms lotze-ge-0-0-1-136.hq.zen.net.uk [62.3.80.137]
4 28 ms 28 ms 28 ms no-dns-yet-62-3-80-78.zen.co.uk [62.3.80.78]
5 35 ms 35 ms 35 ms suarez-so-0-0-0-0.te.zen.net.uk [62.3.80.62]
6 34 ms 35 ms 34 ms 195.66.224.185
7 35 ms 35 ms 35 ms g14-0-0.core02.lon01.atlas.cogentco.com [130.117.2.21]
8 43 ms 42 ms 42 ms p1-0.core01.ams03.atlas.cogentco.com [130.117.1.109]
9 50 ms 49 ms 49 ms p4-0.core01.fra03.atlas.cogentco.com [130.117.0.146]
10 54 ms 54 ms 54 ms p5-0.core01.muc01.atlas.cogentco.com [130.117.1.197]
11 60 ms 60 ms 59 ms p6-0.core01.vie01.atlas.cogentco.com [130.117.0.214]
12 61 ms 60 ms 60 ms inode.demarc.cogentco.com [130.117.20.190]
13 61 ms 61 ms 59 ms vie2-po-00-002.shuttle.vien.inode.at [62.99.170.214]
14 61 ms 60 ms 62 ms sel2-gb-01-002.shuttle.vien.inode.at [62.99.170.62]
15 61 ms 61 ms 60 ms 62-99-143-188.static.sh-wien.inode.at [62.99.143.188]

Trace complete.