What's this then?

Hi,

Performance across the Plusnet internal network appears to be congested at one particular point :

gi0-2-32.ptc-gw1.plus.net (195.166.129.10)

Not knowing what this is, does anyone else know it's purpose?

traceroute to portal.plus.net (212.159.8.137), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 13.197 ms 4.049 ms 17.709 ms
2 lo0-plusnet.pte-ag2.plus.net (195.166.128.72) 49.228 ms 44.645 ms 44.917 ms
3 ge0-0-0-504.pte-gw1.plus.net (84.92.4.89) 41.977 ms 42.545 ms 42.870 ms
4 ge0-0-0-22.ptn-gw1.plus.net (212.159.4.1) 43.510 ms 48.448 ms 46.850 ms
5 gi0-2-32.ptc-gw1.plus.net (195.166.129.10) 253.263 ms 128.342 ms 205.391 ms
6 se3-0.pih-gw1.plus.net (195.166.129.250) 54.406 ms 74.097 ms 71.916 ms
7 vlan8.pih-gw4.plus.net (212.159.0.30) 52.494 ms 69.017 ms *
8 pih-al4.plus.net (212.159.1.36) 52.063 ms 51.736 ms 52.055 ms
9 pih-al4.plus.net (212.159.1.36) 51.520 ms 53.624 ms 51.715 ms

I've reported to Customer Support, not particularly hopeful of a sensible response to be honest....


Regards,
Alex.

Hi,

So I rebooted my router and now I'm connected to a different gateway, and get a much better result all round.

Why would that be? Luck?

traceroute to portal.plus.net (212.159.8.137), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 3.174 ms 10.003 ms 3.019 ms
2 lo0-plusnet.thn-ag1.plus.net (195.166.128.80) 44.271 ms 44.827 ms 43.732 ms
3 vl303.thn-gw1.plus.net (84.92.3.177) 54.975 ms 241.755 ms 215.382 ms
4 ge1-0-0-23.ptn-gw1.plus.net (212.159.4.17) 49.325 ms 44.063 ms 42.973 ms
5 gi0-2-32.ptc-gw1.plus.net (195.166.129.10) 43.422 ms 42.735 ms 42.506 ms
6 se3-0.pih-gw1.plus.net (195.166.129.250) 51.914 ms 50.548 ms 52.176 ms
7 vlan8.pih-gw4.plus.net (212.159.0.30) 53.004 ms 50.135 ms 52.165 ms
8 pih-al4.plus.net (212.159.1.36) 51.733 ms 52.248 ms 51.530 ms
9 pih-al4.plus.net (212.159.1.36) 49.985 ms 50.998 ms 51.023 ms

Edited by alexwaddell (Sun 17-Sep-06 09:25:14)

An ellecoya by any chance?

Hi,

Here's the thing, I'm on PAYG so why would I go through an Ellacoya? Or do Plusnet stupidly send everyone through and then not apply shaping to PAYG customers? If that's the case why stay on PAYG if the Ellacoyas are getting max'd out?

Were you being ironic with your "much better" comment there? The pings certainly don't look much better - look at hop 3 for example, a low of 54.975ms and a high of 241.755ms...?!

In comparison, mine this morning:

tracert www.plus.net

Tracing route to portal.plus.net [212.159.8.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 14 ms 12 ms lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
3 12 ms 12 ms 11 ms ge0-0-0-403.pte-gw1.plus.net [84.92.4.1]
4 12 ms 11 ms 11 ms ge0-0-0-22.ptn-gw1.plus.net [212.159.4.1]
5 13 ms 13 ms 14 ms gi0-2-32.ptc-gw1.plus.net [195.166.129.10]
6 20 ms 20 ms 20 ms se3-0.pih-gw1.plus.net [195.166.129.250]
7 21 ms 20 ms 22 ms vlan8.pih-gw4.plus.net [212.159.0.30]
8 20 ms 21 ms 20 ms pih-al4.plus.net [212.159.1.36]
9 22 ms 20 ms 21 ms portal.plus.net [212.159.8.137]

Trace complete.

Hi,

I am on a NON LLU line, BT ADSL MAX with interleaving switched on as my line was very unstable. I appreciate that interleaving can add 30-40ms onto pings, and I accept that my line is much more stable now as a result. My issue is that one particular hop seems out of step with the rest if you're coming through a particular gateway.

Regards,
Alex.

It looks like they're running traffic across the backup link to Sheffield. The primary looks to be down at the moment.

TT

Is there actually a problem to locations after their network? The traceroute doesn't indicate so. If traffic to the final destination isn't actually affected, then there is nothing to worry about. Sometimes routers respond slowly to ICMP stuff as they're busy dealing with everything else. ~7-8ms to get through the network doesn't seem that bad. I'm not hugely upto date on how it usually performs though..