i recently got a sagonet server but most of the time its un useable with 2-3 seconds lag when sshing to the server using putty sometimes more. does anyone know if this is a temp problem? anyone else having the same problem?

Post a traceroute and an average ping reply (with at least 10 pings). It could be because of that, or because your server's under too much load.

Tracing route to fire.voidhosting.com [66.111.59.10]
over a maximum of 30 hops:

1 16 ms 12 ms 15 ms 217.47.251.250
2 12 ms 13 ms 12 ms 217.47.251.214
3 12 ms 13 ms 12 ms 194.72.2.249
4 16 ms 15 ms 15 ms core1-pos15-2.bletchley.ukcore.bt.net [194.74.16
.230]
5 18 ms 19 ms 20 ms core1-pos13-0.ealing.ukcore.bt.net [62.6.196.245
]
6 17 ms 17 ms 16 ms transit2-pos3-0.ealing.ukcore.bt.net [194.72.17.
82]
7 19 ms 16 ms 17 ms t2c2-p8-0.uk-eal.eu.bt.net [166.49.168.33]
8 18 ms 17 ms 17 ms so-3-0.ipcolo2.London2.Level3.net [212.113.11.25
3]
9 18 ms 19 ms 17 ms ae-0-53.bbr1.London2.Level3.net [212.187.129.161
]
10 92 ms 91 ms 91 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102
]
11 122 ms 120 ms 119 ms so-2-0-0.mp1.Tampa1.Level3.net [209.247.11.201]

12 121 ms 122 ms 121 ms so-6-0-0.gar1.Tampa1.Level3.net [4.68.124.10]
13 123 ms 123 ms 123 ms 4.79.144.2
14 125 ms 123 ms 124 ms gi0-1.ds05.tpa.sagonet.net [65.110.32.12]
15 125 ms * 125 ms fire.voidhosting.com [66.111.59.10]

Trace complete.


Tracing route to fire.voidhosting.com [66.111.59.10]
over a maximum of 30 hops:

1 13 ms 12 ms 13 ms 217.47.251.250
2 13 ms 17 ms 12 ms 217.47.251.214
3 15 ms 12 ms 14 ms 194.72.2.249
4 19 ms 15 ms 15 ms core1-pos15-2.bletchley.ukcore.bt.net [194.74.16
.230]
5 17 ms 17 ms 20 ms core1-pos13-0.ealing.ukcore.bt.net [62.6.196.245
]
6 20 ms 17 ms 17 ms transit2-pos3-0.ealing.ukcore.bt.net [194.72.17.
82]
7 16 ms 17 ms 16 ms t2c2-p8-0.uk-eal.eu.bt.net [166.49.168.33]
8 18 ms 17 ms 18 ms so-3-0.ipcolo2.London2.Level3.net [212.113.11.25
3]
9 17 ms 19 ms 18 ms ae-0-53.bbr1.London2.Level3.net [212.187.129.161
]
10 92 ms 89 ms 93 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102
]
11 122 ms 121 ms 122 ms so-2-0-0.mp1.Tampa1.Level3.net [209.247.11.201]

12 121 ms 121 ms 120 ms so-6-0-0.gar1.Tampa1.Level3.net [4.68.124.10]
13 123 ms 122 ms 121 ms 4.79.144.2
14 * * * Request timed out.
15 125 ms 126 ms 126 ms fire.voidhosting.com [66.111.59.10]

Tracing route to fire.voidhosting.com [66.111.59.10]
over a maximum of 30 hops:

1 15 ms 13 ms 12 ms 217.47.251.250
2 18 ms 13 ms 15 ms 217.47.251.214
3 13 ms 12 ms 12 ms 194.72.2.249
4 15 ms 17 ms 17 ms core1-pos15-2.bletchley.ukcore.bt.net [194.74.16
.230]
5 17 ms 19 ms 21 ms core1-pos13-0.ealing.ukcore.bt.net [62.6.196.245
]
6 21 ms 20 ms 17 ms transit2-pos3-0.ealing.ukcore.bt.net [194.72.17.
82]
7 20 ms 17 ms 18 ms t2c2-p8-0.uk-eal.eu.bt.net [166.49.168.33]
8 18 ms 17 ms 17 ms so-3-0.ipcolo2.London2.Level3.net [212.113.11.25
3]
9 19 ms 18 ms 17 ms ae-0-53.bbr1.London2.Level3.net [212.187.129.161
]
10 92 ms 89 ms 92 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102
]
11 122 ms 121 ms 121 ms so-2-0-0.mp1.Tampa1.Level3.net [209.247.11.201]

12 122 ms 120 ms 121 ms so-6-0-0.gar1.Tampa1.Level3.net [4.68.124.10]
13 122 ms 123 ms 123 ms 4.79.144.2
14 * * 125 ms gi0-1.ds05.tpa.sagonet.net [65.110.32.12]
15 125 ms 128 ms * fire.voidhosting.com [66.111.59.10]
16 127 ms 131 ms 126 ms fire.voidhosting.com [66.111.59.10]

poole, i have that same problem with my sagonet box also. A lot of times a lot of the lower end network places have this problem. It's just something i've learned to live with. It doesnt even do it that bad compared to my HiVelocity box, so now the sago one seems pretty good. Get a box at a *good* place, and you'll never have that problem. Ive never once that that problem on my 15minuteservers box, or my superb box or my gnax box, or any other of the good places.

ive ordered an ezzi box to replace it

Ya, sago has been having a few network issues. They'[ve been addressing them head on and as best they can though :)

Give them a little time, things keep getting broken with all the hurricanes and such.

~Francisco

This isn't a hurricane problem. This is the result of a completely dumb decision to replace some cisco equipment and turn their all cisco network into a some cisco and some foundary and some NetIron network.