DeanX wrote:so when i ring VM up tomoz, do i just say "there is a problem with one of ur gateways, then tell them 'lee-bb-b-so-220-0.inet.ntl.com (213.105.175.129) 57.304 ms 57.327 ms 57.387 ms' or just the ip"
abit of advice plz..
Try providing them with the traceroute i provided below. I know its extremely frustrating trying to deal with service providers where if the technical people dont talk to each other to diagnostically agree the location of the problem then nothing gets progressed.
As end clients on ISPs, or end users on server hostings, we have practically no tools at our disposal to help diagnose problems, yet it often seems to come down to a clients own responsibility to have to do a full network diagnosis of a service provider's network and present the results & solution before anything will get done at all. This seems the wrong way round to me.
Good luck - you will need to push them hard. You can try to get them to talk directly with RapidSwitch (UKCS's network provider) if they are still pointing the fingers. As VM and RapidSwitch are peered (ie, they have a mutual agreement and pipe between their networks), then they should be able to talk.
As VM clients, there's many of you and if as many of you can report the problem then they might listen.
This is the traceroute to DeanX. It can be seen he's caught with the same laggy NTL gateway on hop 7.
1 ge-edge.kit.sov.lon.rapidswitch.com (213.228.232.1) 29.953 ms 4.419 ms 49.460 ms
2 87.117.211.33 (87.117.211.33) 1.219 ms 0.705 ms 0.741 ms
3 10ge-1-4.tiger.thn.lon.rapidswitch.com (87.117.211.13) 1.743 ms 1.457 ms 1.489 ms
4 * * *
5 nth-bb-b-as0-0.inet.ntl.com (62.253.184.1) 17.011 ms 16.944 ms 16.965 ms
6 pop-bb-a-so-100-0.inet.ntl.com (213.105.172.14) 3.987 ms 3.720 ms 3.749 ms
7 lee-bb-b-so-220-0.inet.ntl.com (213.105.175.129) 58.451 ms 58.716 ms 58.925 ms
8 man-bb-a-so-100-0.inet.ntl.com (62.253.185.193) 61.203 ms 61.168 ms 60.427 ms
9 manc-t3core-1a-so-000-0.inet.ntl.com (213.105.175.2) 60.207 ms 61.201 ms 60.202 ms
10 oldh-t2cam1-a-ge-wan34.inet.ntl.com (195.182.178.34) 59.957 ms 61.201 ms 62.469 ms
11 ubr02asht-ge01.inet.ntl.com (80.5.164.86) 64.929 ms 63.164 ms 63.446 ms
<last line removed>