Strange. Can't acces a site, but proxy allows?

[kryogenik]

I can't access www.servage.net but if I use renf-cache-9.server.ntli.net 8080 there's no problems?

Could it be a routing problem?
I've never had any bother before.
Anyone on Baguley give it a go?

[Down the Pub]

no probs here with direct connection. must just be one of those things tonight.

[kryogenik]

Odd.
Thanks for the reply and checking anyway.
:)

[kryogenik]

This is still ongoing.
I can't even ping the site.
:(

[Paul]

Must be a route issue, fine here - do a tracert and see how far you get.

[kryogenik]

Losing it at the 12th hop Paul..


Tracing route to www.servage.net [77.232.66.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms XXXXXXXXXX [********]
2 10 ms 9 ms 7 ms 10.87.124.1
3 8 ms 13 ms 19 ms oldh-t2cam1-b-ge95.inet.ntl.com [80.5.164.141]
4 9 ms 16 ms 11 ms oldh-dpim1-7-coc-1-gw.service.virginmedia.net [86.28.65.34]
5 8 ms 18 ms 10 ms man-bb-b-as0-0.inet.ntl.com [213.105.242.245]
6 19 ms 14 ms 13 ms po6-0.mctbb1.Manchester.opentransit.net [193.251.250.105]
7 20 ms 17 ms 32 ms po10-0.brsbb1.Bristol.opentransit.net [193.251.242.133]
8 37 ms 20 ms 22 ms so-5-2-0-0.loncr5.London.opentransit.net [193.251.243.37]
9 47 ms 39 ms 32 ms so-6-0-0-0.loncr1.London.opentransit.net [193.251.242.170]
10 30 ms 39 ms 31 ms so-0-0-3.lon11.ip.tiscali.net [213.200.77.53]
11 39 ms 34 ms 49 ms so-0-0-0.ham10.ip.tiscali.net [213.200.81.130]
12 * * * Request timed out.
13 * * * Request timed out.

I can't even FTP into my server which is a proper nuisance.

[Hugh]

Fine from Leeds.

[kryogenik]

Fine from Leeds.

Ta FW.

[Paul]

Well the issue is well off the VM network (looks like a Tiscali issue) so I doubt there is much you can do.

[kryogenik]

Well the issue is well off the VM network (looks like a Tiscali issue) so I doubt there is much you can do.

Aye.
Support are seeing if it's a peering problem.

[kryogenik]

I resorted to changing my IP address to test.
I can now access the site via HTTP and also FTP into my server.
Ping and tracerts work too.

Tracing route to www.servage.net (http://www.servage.net) [77.232.66.127]
over a maximum of 30 hops:

1 4 ms 2 ms 1 ms ******** [*******]
2 10 ms 11 ms 22 ms 10.87.124.1
3 9 ms 11 ms 7 ms oldh-t2cam1-b-ge95.inet.ntl.com [80.5.164.141]
4 9 ms 11 ms 20 ms oldh-dpim1-7-coc-1-gw.service.virginmedia.net [86.28.65.34]
5 12 ms 10 ms 12 ms man-bb-b-as0-0.inet.ntl.com [213.105.242.245]
6 10 ms 10 ms 15 ms po6-0.mctbb1.Manchester.opentransit.net [193.251.250.105]
7 20 ms 19 ms 19 ms po10-0.brsbb1.Bristol.opentransit.net [193.251.242.133]
8 23 ms 20 ms 25 ms so-5-2-0-0.loncr5.London.opentransit.net [193.251.243.37]
9 22 ms 19 ms 31 ms so-6-0-0-0.loncr1.London.opentransit.net [193.251.242.170]
10 69 ms 70 ms 68 ms so-0-0-3.lon11.ip.tiscali.net [213.200.77.53]
11 71 ms 40 ms 41 ms so-0-0-0.ham10.ip.tiscali.net [213.200.81.130]
12 38 ms 50 ms 37 ms servage-gw.ip.tiscali.net [213.200.65.182]
13 40 ms 38 ms 38 ms cs2-if23-1000m.hhde.ip.servage.net [77.232.64.2]
14 43 ms 37 ms 36 ms www.servage.net (http://www.servage.net) [77.232.66.127]Speeds are diabolical though now lol.
Can't have everything it seems.

:p: