Still dead here.
No uploads and Trace routes still die at paix.he.net [198.32.176.20] :-(

T.A.

Oh, bother.
Eric does intend to attempt to upgrade the RAM in the router sometime 'soon', but that could still be a few weeks...he is out of town right now.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Still dead here.
No uploads and Trace routes still die at paix.he.net [198.32.176.20] :-(
T.A.

The Reboot also didn't help me here in NZ.

But I thought I might give the Proxy http server alternative another try.

Someone in another thread mentioned the list of proxies at
http://www.xroxy.com/
So I have tried a number of servers, and I am now managing to upload a trickle of results via annonymous servers in the UK and another in Canada.

So I am pleased to report that the proxy server solution is working for me, and I hope to get my completed units uploaded before some of them expire, but it sure isn't an ideal solution.

Martin.

---

Dead again, It was good while it lasted..

---

Have been unsuccessful all day:

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RIRR [192.168.1.1]
2 8 ms 10 ms 7 ms 10.67.128.1
3 8 ms 12 ms 8 ms gig-2-4-nycmnyu-rtr2.nyc.rr.com [24.29.139.6]
4 10 ms 22 ms 14 ms tengig-12-0-0-nycmnya-rtr2.nyc.rr.com [24.29.139
.198]
5 87 ms 48 ms 52 ms tenge-4-0-2-nwrknjmd-rtr.nyc.rr.com [24.29.97.18
]
6 18 ms 24 ms 10 ms ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
7 17 ms 17 ms 11 ms ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
8 43 ms 18 ms 33 ms nyk-b5-link.telia.net [213.248.77.177]
9 9 ms 12 ms 11 ms nyk-bb1-link.telia.net [213.155.130.248]
10 85 ms 86 ms 87 ms sjo-bb1-link.telia.net [80.91.252.153]
11 88 ms 105 ms 87 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *

---

It looks like I just got hit with the HE problem for the first time. Boinc can't connect to Seti or Seti Beta using my DSL. Luckily, my cable ISP which I normally only use when I need an extra fast download seem to have no problem connecting.

It looks like I just got hit with the HE problem for the first time. Boinc can't connect to Seti or Seti Beta using my DSL. Luckily, my cable ISP which I normally only use when I need an extra fast download seem to have no problem connecting.

Looks like the router reboot must have killed it for you.
My work machines have been out since the 22nd. Today I tried to tether my phone to a PA, but the connections via t-mobile was no joy as well. My home machines are happy campers though. Maybe I'll sneaker-net all of my finished work at home so it can be returned.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Still unable to connect from NYC with cable or T-Mobile, both methods time out at the same place. How many of users are 'black listed' from the server?

1 3 ms 3 ms 3 ms 192.168.1.1
2 52 ms 49 ms 49 ms 38.191.168.10.in-addr.arpa [10.168.191.38]
3 58 ms 53 ms 45 ms 37.191.168.10.in-addr.arpa [10.168.191.37]
4 80 ms 52 ms 45 ms 12.191.168.10.in-addr.arpa [10.168.191.12]
5 62 ms 55 ms 57 ms 2.191.168.10.in-addr.arpa [10.168.191.2]
6 54 ms 67 ms 50 ms 5.209.170.10.in-addr.arpa [10.170.209.5]
7 53 ms 54 ms 44 ms 10.209.170.10.in-addr.arpa [10.170.209.10]
8 51 ms 68 ms 50 ms 33.236.163.10.in-addr.arpa [10.163.236.33]
9 85 ms 67 ms 73 ms 117.188.176.10.in-addr.arpa [10.176.188.117]
10 50 ms 73 ms 75 ms 12.91.209.9
11 55 ms 46 ms 52 ms cr1.n54ny.ip.att.net [12.122.105.26]
12 48 ms 49 ms 41 ms gar1.lsnca.ip.att.net [12.122.81.105]
13 48 ms 46 ms 107 ms 192.205.36.110
14 42 ms 49 ms 41 ms nyk-bb1-link.telia.net [213.155.130.246]
15 120 ms 137 ms 121 ms sjo-bb1-link.telia.net [213.248.80.1]
16 117 ms 132 ms 123 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
17 * * * Request timed out.
18

---

Same here from South-Africa. Last connected on
22nd August.

---

Still unable to connect from NYC with cable or T-Mobile, both methods time out at the same place. How many of users are 'black listed' from the server?

1 3 ms 3 ms 3 ms 192.168.1.1
2 52 ms 49 ms 49 ms 38.191.168.10.in-addr.arpa [10.168.191.38]
3 58 ms 53 ms 45 ms 37.191.168.10.in-addr.arpa [10.168.191.37]
4 80 ms 52 ms 45 ms 12.191.168.10.in-addr.arpa [10.168.191.12]
5 62 ms 55 ms 57 ms 2.191.168.10.in-addr.arpa [10.168.191.2]
6 54 ms 67 ms 50 ms 5.209.170.10.in-addr.arpa [10.170.209.5]
7 53 ms 54 ms 44 ms 10.209.170.10.in-addr.arpa [10.170.209.10]
8 51 ms 68 ms 50 ms 33.236.163.10.in-addr.arpa [10.163.236.33]
9 85 ms 67 ms 73 ms 117.188.176.10.in-addr.arpa [10.176.188.117]
10 50 ms 73 ms 75 ms 12.91.209.9
11 55 ms 46 ms 52 ms cr1.n54ny.ip.att.net [12.122.105.26]
12 48 ms 49 ms 41 ms gar1.lsnca.ip.att.net [12.122.81.105]
13 48 ms 46 ms 107 ms 192.205.36.110
14 42 ms 49 ms 41 ms nyk-bb1-link.telia.net [213.155.130.246]
15 120 ms 137 ms 121 ms sjo-bb1-link.telia.net [213.248.80.1]
16 117 ms 132 ms 123 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
17 * * * Request timed out.
18

It seems to be a router table getting scrambled issue. At least from what they have seen that has occurred a few times.
It is hard to say how many users are effected. Only a small portion of us use the forums. Someone could look at the stats I suppose and try to figure it out based on # of users returning work.
Maybe one of the stat sites tracks that information already?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Router reboot hit me also. Can't upload anything to SETI Beta, and nothing coming from here on the download pipes. I'm sure it'll get fixed in due time.

[edit]
Tethering my cell phone managed to work this time, so at least I got some work on my laptop.

---

Checked Seti@homes servers and everything is ok,,,they`re up and running. But when I try to get new tasks, all I get is: "Project communication failed: attempting access to reference site. Scheduler request failed: could`nt connect to server. Internet access ok-project servers may be temporarily down." It`s been like this all day.

---

Same here, and my best cruncher is starving!! uploads on my other machines are not going through either :(

---

Same here, and my best cruncher is starving!! uploads on my other machines are not going through either :(

It was like this all day yesterday, too. I tried my other machine, also. No luck.

---

Well, some people must be getting tasks because the number of WU`s available on the Seti server status page keeps changing.

---

Well, some people must be getting tasks because the number of WU`s available on the Seti server status page keeps changing.

Think most do, the bandwidth have been maxed out since work came back. http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-250/gigabitethernet2_3&ranges=d%3Aw&view=Octets

Many, if not most, are able to transmit (in fact they are celebrating on other threads) and I can only guess at how many of us are affected by this glitch but I think it maybe significant.

Per BOINC Stats, there are currently 151,384 active users (results in last 30 days) and yesterday S@H produced 59,336,582 credits compared to "Recent Average Credit RAC of 98,162,767. Nobody was able to transmit for several days although many had WU's in their cache. I know this is all inconclusive and I may not even understand the numbers I'm citing but between down time and those of us who cannot presently transmit, it appear daily production, at least today, is down about 40%

---

24 hrs later and Boinc can use my DSL connection again, so for me it was a short hiccup.

First thank you for all your hard work, you will be missed

Not able to upload, get new work units or update my work done or average.

1. Not able to reach ANY of the upload, download, or scheduling servers.
2. Started having this problem Monday evening, Aug 22, 2011
3. My ISP is cal.net
4. My geographic location is Diamond Springs, CA 95619
5. When I ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20 all I get is "Request timed out"

---

Probs here too, one of my servers can reach:

 2  catv-89-133-254-254.catv.broadband.hu (89.133.254.254)  7.878 ms  8.218 ms  20.340 ms
 3  catv-89-135-220-46.catv.broadband.hu (89.135.220.46)  9.868 ms  9.876 ms  9.881 ms
 4  84.116.240.1 (84.116.240.1)  107.933 ms  109.890 ms  110.739 ms
 5  at-vie15a-rd1-xe-4-2-0.aorta.net (84.116.134.5)  111.757 ms at-vie15a-rd1-xe-1-0-0.aorta.net (84.116.134.1)  111.765 ms at-vie15a-rd1-xe-4-2-0.aorta.net (84.116.134.5)  111.754 ms
 6  uk-lon01b-rd1-xe-1-0-2.aorta.net (84.116.130.253)  110.341 ms uk-lon01b-rd1-xe-1-0-1.aorta.net (84.116.132.37)  107.655 ms uk-lon01b-rd1-xe-1-0-0.aorta.net (84.116.132.33)  109.041 ms
 7  84.116.132.226 (84.116.132.226)  108.997 ms 84.116.132.234 (84.116.132.234)  109.016 ms  109.004 ms
 8  us-nyc01b-rd1-pos-12-0.aorta.net (213.46.160.242)  108.993 ms  109.806 ms  108.993 ms
 9  us-nyc01b-ri1-xe-3-1-0.aorta.net (213.46.190.94)  110.992 ms  107.878 ms  107.879 ms
10  core1.nyc4.he.net (198.32.118.57)  108.115 ms  108.120 ms  108.087 ms
11  10gigabitethernet10-1.core1.sjc2.he.net (184.105.213.173)  177.703 ms  177.303 ms 10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197)  177.673 ms
12  10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69)  183.094 ms  182.394 ms  182.405 ms
13  64.71.140.42 (64.71.140.42)  186.712 ms  186.721 ms  188.548 ms
14  208.68.243.254 (208.68.243.254)  232.318 ms *  229.344 ms
15  * * *

ping 208.68.240.13
PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data.
64 bytes from 208.68.240.13: icmp_req=1 ttl=53 time=266 ms

and another one can't:

 1  GE-V25.core0.interware.hu (195.70.32.193)  1.105 ms  1.101 ms  1.094 ms
 2  GE-0-0-12.border0.interware.hu (195.70.32.4)  1.061 ms  1.059 ms  1.054 ms
 3  194.149.1.85 (194.149.1.85)  90.807 ms  90.811 ms  90.802 ms
 4  TenGE-7-2.huvie.datanet.hu (194.149.20.10)  107.804 ms  107.806 ms *
 5  194.149.19.14 (194.149.19.14)  7.627 ms  7.629 ms  7.621 ms
 6  10gigabitethernet1-1.core1.lon1.he.net (195.66.224.21)  35.718 ms  34.981 ms  43.207 ms
 7  10gigabitethernet6-3.core1.ash1.he.net (72.52.92.137)  120.001 ms  120.007 ms  119.987 ms
 8  10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177)  193.815 ms  190.656 ms  190.647 ms
 9  * * *

ping 208.68.240.13
PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data.
^C
--- 208.68.240.13 ping statistics ---
512 packets transmitted, 0 received, 100% packet loss, time 510998ms

SNAFU looks to be on 10gigabitethernet7-4.core1.pao1.he.net

To me it looks like trying to ride a dead horse.
Sorry for that...

---