network SLLLLOOOOOWWWWW....

Can you post output of 'traceroute ', please?

If using a Windows machine, can try tracert instead of traceroute.

Here is the output of tracert..i don't know how to interpret these results, certainly responses are not very quickly..however, it seems that thing are getting a little bit better since yesterday:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 48 ms 45 ms 46 ms 192.168.100.1

3 47 ms 46 ms 47 ms r-fi67-vl14.opb.interbusiness.it [80.19.134.24]

4 46 ms 45 ms 46 ms r-fi63-fi67.opb.interbusiness.it [151.99.98.89]

5 51 ms 50 ms 49 ms r-rm213-fi63.opb.interbusiness.it [151.99.101.189]

6 50 ms 50 ms 51 ms r-rm83-vl3.opb.interbusiness.it [151.99.29.139]

7 152 ms 152 ms 151 ms rom3-ibs-resid-10-it.rom.seabone.net [213.144.177.165]

8 275 ms 278 ms 277 ms ash1-new2-racc1.new.seabone.net [195.22.216.139]

9 260 ms 263 ms 263 ms 208.173.51.157

10 278 ms 279 ms 280 ms cpr2-pos-4-0.VirginiaEquinix.savvis.net [206.24.227.61]

11 263 ms 291 ms 263 ms bcs1-so-0-0-0.Washington.savvis.net [208.173.52.114]

12 302 ms 299 ms 301 ms dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]

13 313 ms 353 ms 320 ms bcs1-so-3-2-0.Dallas.savvis.net [204.70.192.82]

14 307 ms 338 ms 319 ms dcr1-as0.Dallas.savvis.net [204.70.193.214]

15 332 ms 307 ms 331 ms dcr1-as0.Dallas.savvis.net [204.70.193.214]

16 323 ms 382 ms 323 ms aer1-po10.DallasEquinix.savvis.net [204.70.134.14]

17 395 ms 391 ms 390 ms 208.175.175.42

18 370 ms 392 ms 393 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

19 360 ms 375 ms 377 ms vl2.car02.dllstx2.theplanet.com [12.96.160.44]

20 363 ms 367 ms 370 ms li8-140.members.linode.com [67.18.92.140]

It looks like your biggest jumps in response time are in seabone and savvis. I'm not sure why savvis is causing delays internally, but going overseas it isn't terribly surprising. I think you're just having some bad luck in how the routing is being handled on some of those backbones from your location. Either that or it's just bad timing. :)

The other thing you might want to do is run ping for a while and see if there's any packet-loss.

370 ms is a little slow, but it's not ridiculously slow for most of the services you'd probably run (mail, web)… it'll be very noticable in SSH though, that's for sure.