1. Can't reach the upload/download servers at this time.

2. Today. It worked prior to about noon CST.

3. I'd rather not say (but we're here to help).

4. Ft. Worth, TX

5.
ping 208.68.240.13: time out
ping 208.68.240.16: time out
ping 208.68.240.18: time out
ping 208.68.240.20: time out

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

1 <1 ms <1 ms <1 ms +.+.+.+
2 44 ms 42 ms 43 ms 172.25.21.65
3 44 ms 43 ms 43 ms 172.25.1.19
4 43 ms 43 ms 46 ms 172.25.224.7
5 45 ms 42 ms 43 ms 172.25.253.1
6 17 ms 16 ms 17 ms 162.58.253.7
7 45 ms 47 ms 44 ms 164.58.5.193
8 47 ms 43 ms 44 ms 164.58.15.45
9 54 ms 49 ms 51 ms 164.58.15.70
10 54 ms 58 ms 64 ms 164.58.15.114
11 51 ms 53 ms 50 ms 156.110.203.2
12 * * * Request timed out.
13 66 ms 67 ms 66 ms xe-0-0-0.0.rtr.seat.net.internet2.edu [64.57.28.
26]
14 92 ms 91 ms 91 ms 10gigabitethernet1-3.core1.sea1.he.net [206.81.8
0.40]
15 115 ms 105 ms 113 ms 10gigabitethernet9-1.core1.sjc2.he.net [72.52.92
.157]
16 110 ms 105 ms 105 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * ^C (cancelled)


U:\>tracert 208.68.240.16

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

1 <1 ms <1 ms <1 ms +.+.+.+
2 43 ms 44 ms 44 ms 172.25.21.65
3 43 ms 44 ms 42 ms 172.25.1.19
4 45 ms 44 ms 45 ms 172.25.224.7
5 43 ms 44 ms 43 ms 172.25.253.1
6 17 ms 17 ms 17 ms 162.58.253.7
7 45 ms 45 ms 43 ms 164.58.5.193
8 43 ms 43 ms 44 ms 164.58.15.45
9 46 ms 49 ms 51 ms 164.58.15.70
10 48 ms 47 ms 46 ms 164.58.15.114
11 53 ms 51 ms 50 ms 156.110.203.2
12 * * * Request timed out.
13 102 ms 66 ms 74 ms xe-0-0-0.0.rtr.seat.net.internet2.edu [64.57.28.
26]
14 92 ms 93 ms 92 ms 10gigabitethernet1-3.core1.sea1.he.net [206.81.8
0.40]
15 69 ms 71 ms 73 ms 10gigabitethernet1-2.core1.pdx1.he.net [72.52.92
.10]
16 81 ms 77 ms 77 ms 10gigabitethernet7-1.core1.sjc2.he.net [72.52.92
.13]
17 108 ms 110 ms 114 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 ^C


U:\>tracert 208.68.240.18

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

1 21 ms 2 ms <1 ms +.+.+.+
2 43 ms 43 ms 43 ms 172.25.21.65
3 43 ms 42 ms 42 ms 172.25.1.19
4 43 ms 43 ms 43 ms 172.25.224.7
5 43 ms 43 ms 42 ms 172.25.253.1
6 35 ms 35 ms 34 ms 162.58.253.7
7 44 ms 44 ms 43 ms 164.58.5.193
8 45 ms 53 ms 43 ms 164.58.15.45
9 60 ms 55 ms 49 ms 164.58.15.70
10 46 ms 46 ms 51 ms 164.58.15.114
11 51 ms 50 ms 52 ms 156.110.203.2
12 * * * Request timed out.
13 86 ms 66 ms 69 ms xe-0-0-0.0.rtr.seat.net.internet2.edu [64.57.28.
26]
14 92 ms 97 ms 100 ms 10gigabitethernet1-3.core1.sea1.he.net [206.81.8
0.40]
15 111 ms 105 ms 105 ms 10gigabitethernet9-1.core1.sjc2.he.net [72.52.92
.157]
16 105 ms 114 ms 105 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * ^C


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

1 <1 ms <1 ms <1 ms +.+.+.+
2 43 ms 42 ms 42 ms 172.25.21.65
3 44 ms 43 ms 45 ms 172.25.1.19
4 43 ms 43 ms 43 ms 172.25.224.7
5 42 ms 46 ms 42 ms 172.25.253.1
6 17 ms 17 ms 17 ms 162.58.253.7
7 44 ms 45 ms 44 ms 164.58.5.193
8 45 ms 46 ms 45 ms 164.58.15.45
9 52 ms 49 ms 48 ms 164.58.15.70
10 46 ms 46 ms 46 ms 164.58.15.114
11 51 ms 51 ms 51 ms 156.110.203.2
12 * * * Request timed out.
13 107 ms 66 ms 66 ms xe-0-0-0.0.rtr.seat.net.internet2.edu [64.57.28.
26]
14 92 ms 97 ms 93 ms 10gigabitethernet1-3.core1.sea1.he.net [206.81.8
0.40]
15 104 ms 105 ms 104 ms 10gigabitethernet9-1.core1.sjc2.he.net [72.52.92
.157]
16 105 ms 104 ms 105 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * ^C


7.

nslookup 208.68.240.13
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

nslookup 208.68.240.16
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

nslookup 208.68.240.18
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18

nslookup 208.68.240.20
Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20

---

See the Panic thread first. Everything went completely flat on the Cricket graph, suddenly, about half an hour ago. I think somebody is disembowelling a router as we speak.

Hey Richard,

I saw that after I posted. I'm hoping thats what the cause is. I know when I first posted my trace routes and pings that things were up, so maybe this time it is due to that. I'm keeping my fingers crossed. I'll try things again later this afternoon, and we'll see what happens! :-)

Looks like that was it. I just got home from work and some transfers here went through & I see on my computers list some of my machines at work contacted the server a few minutes ago.
Not sure if they just rolled back to the old config or did more "fixing". We will see in the next few hours how everyone start responding.

---

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

Not sure if they just rolled back to the old config or did more "fixing". We will see in the next few hours how everyone start responding.

Works perfectly now, reported my WUs waiting since tuesday and got all the credits.

Volker

---

All 4 URLs reachable again.

..everything fine again.

:-)


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

All 4 URLs reachable again.

..everything fine again.

Fine for you, I'm sure.

Or are you speaking for all 152,256 active users?

Uploads have started working again for me in NZ. Whatever they are doing, it's on the right track.

Ian

All 4 URLs reachable again.

..everything fine again.

Fine for you, I'm sure.

Or are you speaking for all 152,256 active users?

Hmm.. I spoke about my machine.

How I could speak for all S@h members?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

After rolling back to BOINC 12.33; 64BIT, had 6.13.0 running with only a few errors, nothing has changed, at all, inspite of all the warnings about using the
6.13.xx versions.

I, suddenly, appeared to be be running a 'CUDA-FERMI' version, with 2 running on each GPU (1x GTX480), 10% above stock, driven by a (INTEL)X9650, now
running 2 years on 3.5GHz, with <1600MHz. FSB.

NO problems here, but my I7-2600 (stock)3.4GHz. and 2 EAH5870, won't even properly install a newer version, although, in a less, intoxicated(should b e ashamed??!!??), I reied to install BOINC, in a completely non used aerea
of the second Hard-Drive, which inhibited, proper install, inhj the right parts of the (1TByte), second hard=drive :( Kind of stupid.........
[color=green] But I'll carry on " as usual" and install the latest BOINC versions!

---

All 4 URLs reachable again.

..everything fine again.

Fine for you, I'm sure.

Or are you speaking for all 152,256 active users?

Hmm.. I spoke about my machine.

How I could speak for all S@h members?

Precisely. You couldn't.

Then please don't say that "everything" is fine in a thread started by a member of staff, for the specific purpose of gathering individual information from individual users - but which may be read by other users as a more general source of information.

Uploads and downloads have just started for me, for now....

But still slow. Pinging earlier today showed 100% loss, now it is:

Pinging 208.68.240.13 with 32 bytes of data:
Reply from 208.68.240.13: bytes=32 time=146ms TTL=50
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 146ms, Maximum = 146ms, Average = 146ms

---

All 4 URLs reachable again.

..everything fine again.

Fine for you, I'm sure.

Or are you speaking for all 152,256 active users?

Hmm.. I spoke about my machine.

How I could speak for all S@h members?

Precisely. You couldn't.

Then please don't say that "everything" is fine in a thread started by a member of staff, for the specific purpose of gathering individual information from individual users - but which may be read by other users as a more general source of information.

I don't understand you, my best friend.

I wrote in an upper message that my machine can't connect to the S@h servers.

Then I wrote later in an other message that: 'everything fine again'.

You wanted to see additional: 'for me'?

I thought this is clear for everyone, that I speak only for me.


Maybe it's time for to go back to on topic?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Working for me again too. But.....
But I'm still getting a 25% packet loss on Ping tests.

Trace routes are slow on the last couple of hops from where it enters the Hurricane system.

And, I lost contact through the German proxy I was using. Whether that is relevant or not I don't know but it could indicate that there may still be some problems from Europe.

T.A.

It is working again for me. Although slow, but thats probably due to the pipes being clogged. :-) Thank goodness, I was worried for a bit! LOL

---

Hi!
Works for me now, all three ISPs. Thanks!

During connectivity problems, I finally learned how to find free webproxies,
(thanks for this thread), how to define them and yes, it worked.

73
s52d

Another ISP from Slovenija:
No connection since 14.43 UTC Yesterday. No problems before.

BR
s52d

Whatever mean things you guys did to that router, it worked. I have no problems reaching the servers now. :) Search for ET continues.

---

How I could speak for all S@h members?

Precisely. You couldn't.

Then please don't say that "everything" is fine in a thread started by a member of staff, for the specific purpose of gathering individual information from individual users - but which may be read by other users as a more general source of information.

the average reader would know the extent of his comment applied to the systems he manages. no need to get apoplectic about the turn of a phrase.

---

For me it works again.

traceroute to 208.68.240.20 (208.68.240.20), 30 hops max, 60 byte packets
 1  a6000.noessler.lan (192.168.101.65)  0.078 ms
 2  access.de.kamp.net (195.62.99.234)  54.134 ms
 3  bbr-ob-01.de.kamp.net (195.62.99.249)  57.072 ms
 4  bbr-ob-02.de.kamp.net (212.110.97.18)  60.262 ms
 5  bbr-f-01.de.kamp.net (195.62.101.2)  65.153 ms
 6  20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172)  69.047 ms
 7  10gigabitethernet1-4.core1.par2.he.net (184.105.213.162)  80.030 ms
 8  10gigabitethernet1-1.core1.par2.he.net (184.105.213.90)  82.049 ms
 9  10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93)  168.023 ms
10  10gigabitethernet10-1.core1.sjc2.he.net (184.105.213.173)  251.004 ms
11  10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197)  243.998 ms
12  10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69)  252.984 ms
13  208.68.243.254 (208.68.243.254)  284.981 ms
14  setiboinc.ssl.berkeley.edu (208.68.240.20)  278.984 ms

We're finding our router (down at the PAIX) is continually getting corrupted routing tables in memory due to (a) lack of memory and (b) constant super-high levels of traffic. Still working on it. There may also be a bad default route in there somewhere.

I'll try to elaborate more on this in tech news later today...

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

We're finding our router (down at the PAIX) is continually getting corrupted routing tables in memory due to (a) lack of memory and (b) constant super-high levels of traffic. Still working on it. There may also be a bad default route in there somewhere.

I'll try to elaborate more on this in tech news later today...

- Matt

Thanx for the post, Matt!
Good to know you are finally finding some real issues that may be the root cause of some of the comms problems.

If you feel a new router is required to fix the situation because the current one is not up to the task, please PM me and I'll get to work on it.

Meow.

---

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

If you feel a new router is required to fix the situation because the current one is not up to the task, please PM me and I'll get to work on it.

Or you could just mention it here, I'm sure we would all be glad to help out with that.

---

PROUD MEMBER OF Team Starfire World BOINC