More Tracert fails

Just about every site I ping or tracert returns RTO today.

The problem is at PN 195.166.128.53

Can anyone explain please.


Meldrew

Can you browse to the sites in question? Have you got any example tracerts?

The specific IP address I quoted was for iii.co.uk. It fell at the first hurdle - you!!

Meldrew

i'm having issues with facebook, google, and some parts of the bbc.... : -Z (the z was intentional)

This is an earlier trace route to the bbc

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 52 ms 98 ms 99 ms dsldevice.lan [192.168.1.254]
2 37 ms 36 ms 36 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
3 * * * Request timed out.
4 46 ms 37 ms 36 ms te2-2.pte-gw2.plus.net [212.159.1.106]
5 35 ms 35 ms 36 ms vl23.thn-gw2.plus.net [212.159.4.20]
6 * 222 ms 101 ms rt0.thdo.bbc.co.uk [212.58.239.25]
7 36 ms 35 ms 35 ms 212.58.238.133
8 40 ms 37 ms 36 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]


The symptoms are very much to the earlier incident(in july) which resulted in intermittent browsing but email and ssh working fine ..

I've tested the site here from a Plusnet connection, our internal network and a Virgin connection. We were able to browse to it on all 3, although it did take a long time on all of them to appear. The tracerts *all* timed out after step 6/7.

Can you browse to the site and is this happening on others?

Thanks, we're asking to see if anything is up internally.

Generally one can browse the sites but there is no point in having a 5Mbs connection if a basic page takes several minutes to load.

This is happening far too often. I really need to know if this is PN specific (which it looks like today) or whether I would get a more consistent connection with another (LLU?) ISP.

(Edit: And even the TB Speedtest will not connect either!)

Meldrew

Edited by deleted (Wed 12-Aug-09 17:42:32)

Some more trace routes from about 5 mins ago.

Tracing route to facebook.com [69.63.176.140]
over a maximum of 30 hops:

1 15 ms 95 ms 98 ms dsldevice.lan [192.168.1.254]
2 88 ms 40 ms 42 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
3 * * * Request timed out.
4 1939 ms 35 ms 35 ms te2-2.pte-gw2.plus.net [212.159.1.106]
5 36 ms 38 ms 43 ms 195.66.225.69
6 110 ms 110 ms 110 ms xe-x-x-x.br01.ash1.tfbnw.net [204.15.22.245]
7 190 ms 195 ms 185 ms ge-2-0-0.br01.sf2p.tfbnw.net [204.15.21.249]
8 194 ms 194 ms 196 ms te-4-0.csw05a.sf2p.tfbnw.net [204.15.20.182]
9 197 ms 206 ms 189 ms www.04.05.sf2p.facebook.com [69.63.176.140]

Trace complete.



Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 7 ms 97 ms 97 ms dsldevice.lan [192.168.1.254]
2 37 ms 37 ms 37 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * ^C


Tracing route to forums.thinkbroadband.com [80.249.99.126]
over a maximum of 30 hops:

1 85 ms 46 ms 71 ms dsldevice.lan [192.168.1.254]
2 52 ms 39 ms 35 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * 1657 ms 35 ms forums.thinkbroadband.com [80.249.99.126]

Trace complete.

ofcourse TBB is now workable for me but definitely a problem exists

<<ofcourse TBB is now workable for me but definitely a problem exists >>

I take it that nobody is particularly concerned about identifying and solving this problem?

Meldrew

I'm still having issues and again email is fine (i did a send and recieve via outlook) and that ran fine whilst this happend on a trace route to google.com

Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:

1 58 ms 99 ms 97 ms dsldevice.lan [192.168.1.254]
2 36 ms 36 ms 35 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 1572 ms 126 ms 125 ms gw-in-f100.google.com [74.125.67.100]