Who is responsible for route changes to games servers?

[Noggo]

I've just come off a games server because of intermittent lag. I've done a trace to the server and it seams that the route changes intermittently and it seams to cause a lag spike. Who is responsible for this, the network it's leaving or going to and what's the best way to get it sorted.

It happens when leaving IP: 212.250.14.42 which according to http://www.ip-adress.com/whois/ it's belongs to NTL Infrastructure - Private Peering (Virgin Media)

It will go to IP: 62.72.140.14 which is part of Pipex for a while, then suddenly switches to IP: 62.72.140.142 which is also part of Pipex. Then it switches back to the original IP after a second or two. All the other hops stay the same.

[cybernetic_tiger]

It sounds like Pipex have a flapping link. The Pipex core will advertise out the IP address range over one of it's peering links with VM, if this link drops then the route is re-learnt across another.

If it is the Pipex IP that is changing and the NTL IP that is staying the same then it's proberbly an issue with Pipex.

[eth01]

is it leaving the VM network without any problems though?

[Florence]

I've just come off a games server because of intermittent lag. I've done a trace to the server and it seams that the route changes intermittently and it seams to cause a lag spike. Who is responsible for this, the network it's leaving or going to and what's the best way to get it sorted.

It happens when leaving IP: 212.250.14.42 which according to http://www.ip-adress.com/whois/ it's belongs to NTL Infrastructure - Private Peering (Virgin Media)

It will go to IP: 62.72.140.14 which is part of Pipex for a while, then suddenly switches to IP: 62.72.140.142 which is also part of Pipex. Then it switches back to the original IP after a second or two. All the other hops stay the same.


Anything that has a pipex IP number is now tiscali which accounts for the lag. All pipex customers finished being migrated over to Tiscali infrastructure middle August, end of August all pipex staff left in Manchester office were made redundant.

[sollp]

I've just come off a games server because of intermittent lag. I've done a trace to the server and it seams that the route changes intermittently and it seams to cause a lag spike. Who is responsible for this, the network it's leaving or going to and what's the best way to get it sorted.

It happens when leaving IP: 212.250.14.42 which according to http://www.ip-adress.com/whois/ it's belongs to NTL Infrastructure - Private Peering (Virgin Media)

It will go to IP: 62.72.140.14 which is part of Pipex for a while, then suddenly switches to IP: 62.72.140.142 which is also part of Pipex. Then it switches back to the original IP after a second or two. All the other hops stay the same.

The routers within any ISP?