We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

nwk-2-6k.nj.us routing issues


rickyday
18-12-2013, 21:51
Quote Originally Posted by Neil
Hi

Any better now?
All fixed now Neil!


Neil
17-12-2013, 18:01
Hi

Any better now?

rickyday
12-12-2013, 19:16
Quote Originally Posted by Neil
Hi

Best to send us an email with your server address and traceroute, it should not go via the US. There has been some works in LDN but still should not cause issues like this.
Thanks for reply Neil.

Going to keep an eye on it over the next few days, if it doesn't correct itself ill send an email.

Have a nice evening.

Neil
12-12-2013, 18:10
Hi

Best to send us an email with your server address and traceroute, it should not go via the US. There has been some works in LDN but still should not cause issues like this.

rickyday
12-12-2013, 14:35
Forgive me if there is a OVH incident logged somewhere regarding this!

For the past couple of days all of my servers have had extremely high pings when they normally are < 18ms.

I conducted tracerts from my Virgin Media 125Mb connection and pings are all good within VMs network and then go pearshaped when I am routed through

nwk-2-6k.nj.us on the way to my French servers.

Why would I be routed through this to reach my servers located in France?


Tracing route to [37.187.***.**]
over a maximum of 30 hops:
1 7 ms 7 ms 6 ms cpc1-heme11-2-0-gw.9-1.cable.virginm.net [81.104.44.1]
2 6 ms 7 ms 12 ms lutn-core-2a-ae5-2549.network.virginmedia.net [80.4.221.89]
3 7 ms 8 ms 6 ms popl-bb-1c-ae2-0.network.virginmedia.net [62.253.174.1]
4 10 ms 7 ms 6 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105.159.117]
5 * * * Request timed out.
6 97 ms 95 ms * nwk-2-6k.nj.us [178.32.135.232]
7 83 ms * * ldn-5-6k.uk.eu [178.32.135.165]
8 89 ms 87 ms 88 ms gra-g2-a9.fr.eu [178.33.103.218]
9 118 ms * 85 ms gra-3a-6k.fr.eu [178.33.103.226]
10 95 ms 88 ms 87 ms server [37.187.***.***]
Same for every server I have RBX and GRA

proof.ovh.net is fine.

Tracing route to proof.ovh.net [188.165.12.106]
over a maximum of 30 hops:
1 9 ms 7 ms 7 ms cpc1-heme11-2-0-gw.9-1.cable.virginm.net [81.104.44.1]
2 6 ms 7 ms 6 ms lutn-core-2b-ae5-2550.network.virginmedia.net [80.4.221.221]
3 7 ms 9 ms 8 ms nrth-bb-1c-ae12-0.network.virginmedia.net [62.253.174.5]
4 9 ms 9 ms 10 ms brhm-bb-1c-et-610-0.network.virginmedia.net [62.253.175.193]
5 * * * Request timed out.
6 * * * Request timed out.
7 16 ms 16 ms 15 ms rbx-g2-a9.fr.eu [91.121.131.181]
8 16 ms * 15 ms rbx-s3-6k.fr.eu [213.186.32.166]
9 15 ms 16 ms 14 ms proof.ovh.net [188.165.12.106]
Is this an OVH issue or Virgin Media routing issue or even LINX?

Ill conduct a reverse tracert and see what happens.

From my GRA server to VM

Tracing route to cpc1-heme11-2-0-gw.9-1.cable.virginm.net [81.104.44.1]
over a maximum of 30 hops:
1 <1 ms * 47 ms 37.187.xxx.xxx
2 <1 ms <1 ms <1 ms gra-g1-a9.fr.eu [178.33.103.229]
3 * * * Request timed out.
4 78 ms 78 ms 78 ms 195.66.236.23
5 78 ms 78 ms 78 ms popl-bb-1c-ae9-0.network.virginmedia.net [213.105.159.118]
6 80 ms 80 ms 80 ms lutn-core-2a-ae0-0.network.virginmedia.net [62.253.174.2]
7 81 ms 82 ms 81 ms cpc1-heme11-2-0-gw.9-1.cable.virginm.net [81.104.44.1]
No sign of the nj.us on the way back, but pings still horrendously high.

Is there a problem at (London Internet Exchange) LINX? (195.66.236.23)

It is not a massive problem at the moment, fingers crossed it automatically corrects itself soon, just interested to see where the fault is really, being the inquisitive chap I am

Looking at OVH status page there seem to be quite a few issues with routers, I will just put it down to that and hope it corrects itself over the next couple of days.

I find this routing stuff very very interesting, but at the same time, quite complex and hard to actually pinpoint where the fault actually lies, interesting stuff.

I will have to read the Tracert guide I feel that Myatu posted a few months ago!

One question where the routers don't respond to ICMP and timeout, is there anyway of obtaining data regarding these hops? IP addresses for instance? any other protocol or way to reveal information regarding these devices? I presume ISPs etc have these tools but what about the average Joe?