So it's a visualised (guest) server? This opens up a whole load of possibilities. There will be contention going on with it then, CPU, disk and network, to name a few. All you need is some other guest running on the same physical server to be being hammered (or possibly a few) and that can detriment how your one operates. This is tricky to measure, but I've seen it happen on the VM I have.

Time to either up the spec of the VM (so it has more resources from the physical server to use) or pay your money and get a dedicated box.

its our box, frankly it could run all the vms on a quarter of its spec the vms are all setup at 3 x actual needs and never get anywhere near bottlenecking either on the conection or ram, cpu,HDD use etc. it isnt the box its now 6.30 ish am there is 0 load on the server right now yet the same result

Host Information
1, -------------- ,192.168.0.1
2,losubs.subs.llu1.mbr-roch.zen.net.uk,62.3.82.20
3,ae0-184.cr2.mbr-roch.zen.net.uk,62.3.80.185
4,ae2-0.cr2.wh-man.zen.net.uk,62.3.80.53
5,xe-1-1-0.man11.ip4.tinet.net,77.67.66.101
6,xe-1-2-0.lon10.ip4.tinet.net,89.149.187.17
7, -------------- ,213.200.77.234
8,DUOCAST.gigabitethernet3-1.ar4.AMS2.gblx.net,208.48.33.246
9,gs07.xch.nl,87.238.170.57

Sample Information
"21/10/2011 06:35:22",1,22,21,22,22,N/A,28,36,38
"21/10/2011 06:35:24",1,21,20,20,23,N/A,27,36,37
"21/10/2011 06:35:27",0,20,22,21,22,28,28,35,36
"21/10/2011 06:35:29",1,20,21,21,21,29,31,59,37
"21/10/2011 06:35:32",0,20,20,20,21,27,27,35,40
"21/10/2011 06:35:34",0,20,24,39,23,27,28,36,37
"21/10/2011 06:35:37",1,21,21,21,23,30,91,35,47
"21/10/2011 06:35:39",0,25,20,20,22,27,28,35,36
"21/10/2011 06:35:42",0,20,23,20,23,28,65,37,45
"21/10/2011 06:35:44",0,22,20,22,21,32,28,43,36
"21/10/2011 06:35:47",0,21,20,21,20,27,47,43,38
"21/10/2011 06:35:49",0,21,20,20,21,28,29,34,44
"21/10/2011 06:35:52",0,23,23,20,25,N/A,27,35,37
"21/10/2011 06:35:54",0,25,20,21,20,N/A,27,36,44
"21/10/2011 06:35:57",0,21,20,20,24,27,29,43,38
"21/10/2011 06:35:59",0,22,21,21,24,31,30,42,37
"21/10/2011 06:36:02",0,21,20,23,21,29,27,36,36

Hello

Hop 6's IP belongs to Tinet (according to a RIPE lookup https://apps.db.ripe.net/search/query.html?searchtex... who are one of Zen's transit providers

HOWEVER, the next hop looks to be a peering connection between Tinet and what was Global Crossing which would now be Level 3 which your provider appears to take a feed from so it maybe an idea to have a chat with their tech support incase there's a switch or something somewhere which maybe holding things up but wouldn't appear on a tracert.

As Zen say though it looks acceptable but I do appreicate from your point of view the performance has decreased but it would not be something Zen has control over.

hi this issue is now resolved i gave up and moved the server in NL to another host, the routing is now back to normal and pings have dropped back to 24-28ms with no PL no idea whose fault it was as both parties blamed the other but i am assured the host has no intention of changing its peers over the next 24 Months i have a trace to and from the Host so if it changes i know who to blame!

Hi

Glad its sorted.

If the problem occurs again it might be worth looking for a host with a direct connection to LINX as that would in theory shorten the route and take out a third party so that there's less to go wrong.

Edited by techguy (Sun 05-Feb-12 20:31:49)