I can't see how the problem would be at Jussi's end since there are a lot of people who have never had any problems with the server.
This doesn't mean that the problem lies on user's end either. There are several turns and knots that a little data packet will have to go through before it reaches all the way to the server and back.
In example I traced route to dsj3.net and it took 17 different addresses the packets had to go through. To medimond.fi packets go through 8 ip's. If you like to see your route Open the command prompt:
Windows 7 or Vista: From the Start menu, in the search field, type cmd , and then press Enter.
Previous versions: From the Start menu, select Run... . In the "Open:" box, type cmd , and then press Enter.
At the command prompt, enter tracert example , where example is the IP address, name, or web site of the computer you are trying to access. For example, if you enter tracert
www.mediamond.fi , you should see something similar to the following:
Tracing route to
www.mediamond.fi [81.17.202.111]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.0.254
2 11 ms 19 ms 12 ms dyn-xdsl-83-150-117-254.nebulazone.fi [83.150.117.254]
3 * * 12 ms r1-ge1.hki.nbl.fi [217.30.183.140]
4 13 ms 13 ms * rtr1-te4-3.ipo.esp.fi.nblnet.com [188.117.15.234]
5 44 ms 12 ms 12 ms academica.ficix1.ficix.fi [193.110.226.52]
6 * * * Request timed out.
7 12 ms 12 ms 12 ms ge-gw1.esp.mediateam.fi [81.17.202.2]
8 13 ms 13 ms 13 ms mail.mediamond.fi [81.17.202.111]
Trace complete.