Some users overseas seem to be having issues connecting to SETI's servers, but the problem seems to be routing issues inbetween the user and SETI, so it's mostly out of SETI's hands.
That aside, SETI@Home's network connection is very saturated because of several server issues and some downtime, now people's clients are trying to refill and top off their caches, causing a large Denial of Service from too many users pounding the system for work.
Some people have found that using BOINC v6.10.x series seems to have a better work fetch, but all of my machines are still using BOINC v6.12.3x and have had no issues.
There is currently a donation drive to help SETI@Home get some new servers to handle the 500,000 clients better, if you're interested in helping out.
But in the end, the problem is not on your side (at least at this point), and SETI has many aging servers that simply cannot handle Moore's law when it comes to multiple-CPU core and GPU computing. I find that the best advice is to attach to multiple projects if you want to keep your CPUs and GPUs busy. If other projects don't fit your fancy, then it's just a matter of patience (and lots of it).