The fourth day is not present connection with project servers. More than 1000 WU-s are finished, do not go. The scheduler does not work. However on page of the status of the project all is fine. Somebody can explain, in what a problem and that to expect?

20-Feb-2010 18:47:59 [---] Project communication failed: attempting access to reference site
20-Feb-2010 18:47:59 [SETI@home] Temporarily failed upload of 09oc06aa.16872.20411.5.10.112_0_0: HTTP error
20-Feb-2010 18:47:59 [SETI@home] Backing off 1 hr 33 min 50 sec on upload of 09oc06aa.16872.20411.5.10.112_0_0
20-Feb-2010 18:48:10 [SETI@home] Temporarily failed upload of 09oc06aa.16872.20411.5.10.118_0_0: HTTP error
20-Feb-2010 18:48:10 [SETI@home] Backing off 42 min 25 sec on upload of 09oc06aa.16872.20411.5.10.118_0_0
20-Feb-2010 18:48:20 [---] Internet access OK - project servers may be temporarily down.

20-Feb-2010 19:08:49 [SETI@home] update requested by user
20-Feb-2010 19:09:01 [SETI@home] Sending scheduler request: Requested by user.
20-Feb-2010 19:09:01 [SETI@home] Reporting 54 completed tasks, not requesting new tasks
20-Feb-2010 19:09:23 [SETI@home] Started upload of 09oc06aa.16872.20411.5.10.136_1_0
20-Feb-2010 19:09:23 [SETI@home] Started upload of 09oc06aa.16872.20411.5.10.143_1_0
20-Feb-2010 19:09:38 [SETI@home] Scheduler request failed: Failure when receiving data from the peer
20-Feb-2010 19:09:49 [SETI@home] Temporarily failed upload of 09oc06aa.16872.20411.5.10.143_1_0: HTTP error
20-Feb-2010 19:09:49 [SETI@home] Backing off 1 min 0 sec on upload of 09oc06aa.16872.20411.5.10.143_1_0
20-Feb-2010 19:10:30 [---] Project communication failed: attempting access to reference site
20-Feb-2010 19:10:32 [---] Internet access OK - project servers may be temporarily down.

And here thus all four days. However 4 WU-s all the same have been sent. When goes WU, (sometimes seldom) sending reaches 100 %, but does not come to an end.

---

Pathping has been around since Windows NT and is still there in Windows 7 for those wondering about it.

Look at everyone's posts of pathping results. Notice anything common? Look at the next to last line, 208.68.243.254, they all show a loss at this node. Explanations? Hardware is failing? System is overloaded due to recent a/c caused outage?

If we had pathping data from before the a/c outage showing the same thing we might suggest hardware, but right now we all know that there's a ton of work out there trying to report in. In theory the built-in backoff will result in gradual relief. Anyone up to tracking between now and Tuesday's scheduled maintenance? If it's not hardware we should see close to zero packet loss at this node just about the time they take it down for the scheduled maintenance. IF we continue tracking after they bring it back up we should see zero packet loss by Friday UTC.

If there's a problem on campus let's give them some proof.

---

C:\Documents and Settings\Administrator>tracert 208.68.240.16

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

1 2 ms 2 ms 2 ms 1.98.79.82.static.cluj.rdsnet.ro [82.79.98.1]
2 2 ms 2 ms 2 ms qr01.cluj.rdsnet.ro [213.154.140.81]
3 4 ms 3 ms 3 ms cr01.cluj.rdsnet.ro [213.154.140.16]
4 2 ms 2 ms 1 ms 213-154-130-76.rdsnet.ro [213.154.130.76]
5 26 ms 26 ms 26 ms 213.154.128.5
6 38 ms 31 ms 31 ms de-cix.he.net [80.81.192.172]
7 39 ms 38 ms 50 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92
.89]
8 43 ms 51 ms 43 ms 10gigabitethernet1-3.core1.lon1.he.net [72.52.92
.33]
9 117 ms 126 ms 123 ms 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92
.77]
10 201 ms 195 ms 196 ms 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92
.25]
11 205 ms 202 ms 200 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
12 200 ms 199 ms 201 ms 64.71.140.42
13 201 ms 201 ms 201 ms 208.68.243.254
14 202 ms 200 ms 201 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

---------------------------------------------------------------------



C:\Documents and Settings\Administrator>tracert 208.68.240.18

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

1 2 ms 2 ms 2 ms 1.98.79.82.static.cluj.rdsnet.ro [82.79.98.1]
2 2 ms 2 ms 2 ms qr01.cluj.rdsnet.ro [213.154.140.81]
3 3 ms 3 ms 5 ms cr01.cluj.rdsnet.ro [213.154.140.16]
4 2 ms 2 ms 2 ms 213-154-130-76.rdsnet.ro [213.154.130.76]
5 22 ms 22 ms 22 ms br01.frankfurt.rdsnet.ro [213.154.126.241]
6 28 ms 31 ms 28 ms de-cix.he.net [80.81.192.172]
7 33 ms 32 ms 32 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92
.89]
8 47 ms 37 ms 49 ms 10gigabitethernet1-3.core1.lon1.he.net [72.52.92
.33]
9 111 ms 111 ms 110 ms 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92
.241]
10 136 ms 137 ms 137 ms 10gigabitethernet1-2.core1.chi1.he.net [72.52.92
.102]
11 193 ms 194 ms 194 ms 10gigabitethernet3-2.core1.sjc2.he.net [72.52.92
.73]
12 197 ms 196 ms 196 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 196 ms 195 ms 195 ms 64.71.140.42
14 197 ms 198 ms 197 ms 208.68.243.254
15 199 ms 201 ms 200 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.


wil return later on with results fro other machines/isp.

One more thing, and this is just as important: we don't want EVERYONE doing this or we will be the problem. Maybe 5 - 10 people in different geographic regions running the test at different times. Maybe the first person runs on the hour, second person at 10 minutes after and so on.

---

One more thing, and this is just as important: we don't want EVERYONE doing this or we will be the problem. Maybe 5 - 10 people in different geographic regions running the test at different times. Maybe the first person runs on the hour, second person at 10 minutes after and so on.

Here is just the last three lines from Albuquerque New Mexico:

 11   54ms     0/ 100 =  0%     0/ 100 =  0%  64.71.140.42
                                7/ 100 =  7%   |
 12   52ms     7/ 100 =  7%     0/ 100 =  0%  208.68.243.254
                                1/ 100 =  1%   |
 13   51ms     8/ 100 =  8%     0/ 100 =  0%  setiboincdata.ssl.berkeley.edu [208.68.240.16]

All the earlier lines had 0% loss. My ISP is comcast. As others have reported, I see loss at the last two lines.

[edited to add this] In a quick sanity check to see if this is just usual, I tried "pathping 74.125.19.147" (which is news.google.com). It came up with 0% at all levels. This shows that the 208.68.240.16 behavior is different, and probably that it is a problem. It does not show that it is the problem, and does not show that it differs from the situation two weeks ago.

---

Трассировка маршрута к boinc2.ssl.berkeley.edu [208.68.240.13]
с максимальным числом прыжков 30:
0 computer-24743d [192.168.1.2]
1 192.168.1.1
2 lo100.asr1006-1.a73.vsi.ru [80.82.57.58]
3 te2-0-0.818.ne40e-2.a53.hw.vsi.ru [80.82.53.18]
4 crs1-ne40e-2.vsi.ru [80.82.56.161]
5 77.51.255.97
6 ae5-222.RT.V10.MSK.RU.retn.net [87.245.253.237]
7 * ae2-6.RT.TC1.STO.SE.retn.net [87.245.233.134]
8 netnod-ix-ge-a-sth-1500.he.net [194.68.123.187]
9 10gigabitethernet3-3.core1.fra1.he.net [72.52.92.233]
10 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
11 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
12 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
13 * 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
14 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
15 64.71.140.42
16 208.68.243.254
17 boinc2.ssl.berkeley.edu [208.68.240.13]

Подсчет статистики за: 425 сек. ...

---

Ping from here can't resolve host target, Sounds like the connection has been severed.

That is a completely different problem.

The DNS servers are not on SETI@Home infrastructure.

---

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
6 linx.he.net [195.66.224.21]
7 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
8 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
9 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
10 64.71.140.42
11 208.68.243.254
12 boinc2.ssl.berkeley.edu [208.68.240.13]

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0/ 100 = 0% |
6 47ms 4/ 100 = 4% 1/ 100 = 1% linx.he.net [195.66.224.21]
0/ 100 = 0% |
7 116ms 4/ 100 = 4% 1/ 100 = 1% 10gigabitethernet2-3.core1.nyc4.he
.net [72.52.92.77]
0/ 100 = 0% |
8 193ms 4/ 100 = 4% 1/ 100 = 1% 10gigabitethernet3-1.core1.sjc2.he
.net [72.52.92.25]
0/ 100 = 0% |
9 195ms 3/ 100 = 3% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]
1/ 100 = 1% |
10 198ms 4/ 100 = 4% 0/ 100 = 0% 64.71.140.42
10/ 100 = 10% |
11 197ms 14/ 100 = 14% 0/ 100 = 0% 208.68.243.254
0/ 100 = 0% |
12 198ms 14/ 100 = 14% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.24
0.13]

Trace complete.

But cannot send / receive work just getting HTTP error. Im in no hurry though the work will go through eventually! Calm down people its not a race!

---

Cheers
D

Per Your Request:

C:\Documents and Settings\Kaylie ********>pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18] over a maximum of 30 hops:
0 front [***.***.***.***]
1 mygateway1.Motorola [***.***.***.***]
2 bu-10-ubr01.rutland.vt.boston.comcast.net [***.***.***.***]
3 ge-1-20-ur01.rutland.vt.boston.comcast.net [68.85.142.241]
4 po-51-ur01.bennington.vt.boston.comcast.net [68.87.146.238]
5 po-50-ar01.springfield.ma.boston.comcast.net [68.87.147.18]
6 be-10-ar01.needham.ma.boston.comcast.net [68.87.146.21]
7 pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.65]
8 67.17.193.41
9 Hurrican-Electric-LLC.TenGigabitEthernet1-4.ar2.SJC2.gblx.net [64.214.174.246]
10 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
11 64.71.140.42
12 208.68.243.254
13 boinc2.ssl.berkeley.edu [208.68.240.18]

Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 front [***.***.***.***]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% mygateway1.Motorola [***.***.***.***]

0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% bu-10-ubr01.rutland.vt.boston.comcast.net [***.***.***.***]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% ge-1-20-ur01.rutland.vt.boston.comcast.net [68.85.142.241]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% po-51-ur01.bennington.vt.boston.comcast.net [68.87.146.238]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% po-50-ar01.springfield.ma.boston.comcast.net [68.87.147.18]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% be-10-ar01.needham.ma.boston.comcast.net [68.87.146.21]
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.65]
0/ 100 = 0% |
8 32ms 0/ 100 = 0% 0/ 100 = 0% 67.17.193.41
0/ 100 = 0% |
9 114ms 0/ 100 = 0% 0/ 100 = 0% Hurrican-Electric-LLC.TenGigabitEthernet1-4.ar2.SJC2.gblx.net [64.214.174.246]
0/ 100 = 0% |
10 114ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
0/ 100 = 0% |
11 116ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
7/ 100 = 7% |
12 116ms 7/ 100 = 7% 0/ 100 = 0% 208.68.243.254
0/ 100 = 0% |
13 117ms 7/ 100 = 7% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

C:\Documents and Settings\Kaylie ********>

I am set to keep 1 days worth of work on hand and have not had problems keeping SETI work on hand.
I currently have two work units totaling 17 hours waiting to be sent in and 3 data units 30 hours of work to process. I am running a MAC and have a 50/50 split on my time with world community grid.
I am not seeing a real problem from southern California but my needs are small because I can only earn about 400 credits a day.

traceroute to 74.125.19.147 (74.125.19.147), 64 hops max, 40 byte packets
1 adsl-67-115-xxx-xxx (67.115.xxx.xxx) 19.230 ms 13.458 ms 10.874 ms
2 dist4-vlan60.irvnca.sbcglobal.net (67.114.50.66) 12.564 ms 12.016 ms 12.608 ms
3 bb2-g2-0.irvnca.sbcglobal.net (151.164.41.239) 15.716 ms 12.307 ms 18.900 ms
4 ex2-p9-1.eqlaca.sbcglobal.net (151.164.39.221) 19.676 ms 14.664 ms 12.594 ms
5 72.14.217.181 (72.14.217.181) 15.062 ms 15.306 ms 22.635 ms
6 216.239.46.180 (216.239.46.180) 12.962 ms 216.239.46.182 (216.239.46.182) 12.453 ms 216.239.46.180 (216.239.46.180) 12.716 ms
7 209.85.253.178 (209.85.253.178) 25.692 ms 24.382 ms 31.322 ms
8 209.85.251.94 (209.85.251.94) 25.583 ms 29.651 ms 36.464 ms
9 nuq04s01-in-f147.1e100.net (74.125.19.147) 27.057 ms 28.950 ms 25.157 ms

traceroute to 208.68.240.16 (208.68.240.16), 64 hops max, 40 byte packets
1 adsl-67-xxx-xxx-126 (67.115.xxx.xxx) 18.080 ms 15.273 ms 15.162 ms
2 dist1-vlan60.irvnca.pbi.net (67.114.48.130) 15.495 ms 12.441 ms 13.764 ms
3 bb1-p2-1.ksc2mo.sbcglobal.net (151.164.42.7) 15.256 ms 14.151 ms 14.948 ms
4 ex3-p6-1.eqlaca.sbcglobal.net (151.164.39.245) 30.159 ms 41.356 ms 47.643 ms
5 asn6939-he.eqlaca.sbcglobal.net (151.164.251.86) 11.512 ms 12.953 ms 19.449 ms
6 10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21) 27.885 ms 22.781 ms 27.017 ms
7 64.71.140.42 (64.71.140.42) 26.472 ms 23.123 ms 21.228 ms
8 208.68.243.254 (208.68.243.254) 26.714 ms 27.620 ms 27.648 ms
9 * * *
10 * * *
11 * *
This address is having a problem

Because I am Static IP, I blocked out part of my IP address.

---

Spaced.

Ok Folks, You heard Ranger, If You can do the following at the command line:

pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Here's the result from Finland if it helps:

Jäljitetään reitti isäntään boinc2.ssl.berkeley.edu [208.68.240.18]
käyttäen enintään 30 siirräntäväliä:

0 XXXXXXXXXXXXXXX
1 XXXXXXXXXXXXXXX
2 ge0-3-0.seisei-p1.fi.elisa.net [139.97.19.194]
3 so1-1-0.tamnal-p1.fi.elisa.net [139.97.6.49]
4 as0.helpa-p1.fi.elisa.net [139.97.6.13]
5 ae2.heltli-gw1.fi.elisa.net [139.97.6.246]
6 * ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49]
7 as0-0.bbr1.sto1.se.eunetip.net [213.192.191.210]
8 netnod-ix-ge-b-sth-1500.he.net [194.68.128.187]
9 10gigabitethernet3-3.core1.fra1.he.net [72.52.92.233]
10 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
11 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
12 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]
13 10gigabitethernet1-2.core1.chi1.he.net [72.52.92.102]
14 10gigabitethernet3-2.core1.sjc2.he.net [72.52.92.73]
15 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
16 64.71.140.42
17 208.68.243.254
18 boinc2.ssl.berkeley.edu [208.68.240.18]

Lasketaan 450 sekunnin tietoja...

Lähde tähän kohteeseen Tämä solmu tai linkki

Kohteen RTT-arvo Kadotettu/lähetetty: prosentti Kadotettu/lähetetty: prosentti Osoite

0 XXXXXXXXXX

0/ 100 = 0% |

1 --- 100/ 100 =100% 100/ 100 =100% XXXXXXXXXX

0/ 100 = 0% |

2 0ms 0/ 100 = 0% 0/ 100 = 0% ge0-3-0.seisei-p1.fi.elisa.net [139.97.19.194]

0/ 100 = 0% |

3 0ms 0/ 100 = 0% 0/ 100 = 0% so1-1-0.tamnal-p1.fi.elisa.net [139.97.6.49]

0/ 100 = 0% |

4 0ms 0/ 100 = 0% 0/ 100 = 0% as0.helpa-p1.fi.elisa.net [139.97.6.13]

0/ 100 = 0% |

5 0ms 0/ 100 = 0% 0/ 100 = 0% ae2.heltli-gw1.fi.elisa.net [139.97.6.246]

0/ 100 = 0% |

6 0ms 0/ 100 = 0% 0/ 100 = 0% ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49]

0/ 100 = 0% |

7 0ms 0/ 100 = 0% 0/ 100 = 0% as0-0.bbr1.sto1.se.eunetip.net [213.192.191.210]

0/ 100 = 0% |

8 --- 100/ 100 =100% 100/ 100 =100% netnod-ix-ge-b-sth-1500.he.net [194.68.128.187]

0/ 100 = 0% |

9 1ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-3.core1.fra1.he.net [72.52.92.233]

0/ 100 = 0% |

10 1ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]

0/ 100 = 0% |

11 2ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]

0/ 100 = 0% |

12 4ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]

0/ 100 = 0% |

13 6ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-2.core1.chi1.he.net [72.52.92.102]

0/ 100 = 0% |

14 8ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.sjc2.he.net [72.52.92.73]

0/ 100 = 0% |

15 9ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]

0/ 100 = 0% |

16 8ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42

5/ 100 = 5% |

17 9ms 9/ 100 = 9% 4/ 100 = 4% 208.68.243.254

0/ 100 = 0% |

18 7ms 5/ 100 = 5% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.18]



Jäljitys suoritettu.

---

One more thing, and this is just as important: we don't want EVERYONE doing this or we will be the problem. Maybe 5 - 10 people in different geographic regions running the test at different times. Maybe the first person runs on the hour, second person at 10 minutes after and so on.

I agree, can't even image how many requests are trying to get in as is.

To do away with DNS resolution, can use -d on tracert for a quicker output:

C:\>tracert -d 208.68.240.18

Tracing route to 208.68.240.18 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.101.1
2 7 ms 7 ms 8 ms 10.50.96.1
3 6 ms 8 ms 11 ms 24.168.128.146
4 9 ms 9 ms 9 ms 24.29.150.97
5 10 ms 27 ms 11 ms 24.29.119.150
6 11 ms 9 ms 9 ms 66.109.6.78
7 10 ms 11 ms 12 ms 66.109.6.27
8 89 ms 89 ms 90 ms 66.109.6.10
9 92 ms 89 ms 89 ms 66.109.6.137
10 109 ms 101 ms 99 ms 216.218.135.229
11 117 ms 100 ms 100 ms 72.52.92.69
12 101 ms 101 ms 100 ms 64.71.140.42
13 111 ms 105 ms * 208.68.243.254
14 * 108 ms 106 ms 208.68.240.18

Trace complete.

Again, issue looks like 208.68.243.254.

Pathping results from Lincoln, NE:


pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18]
over a maximum of 30 hops:
0 yoshikis-shanty [192.168.0.181]
1 76.47.32.1
2 76.47.32.1
3 gig2-1.lnclne03-rtr1.neb.rr.com [76.85.220.89]
4 RDC-24-169-240-172.neb.rr.com [24.169.240.172]
5 ge-1-1-7.lnclne00-mx42.neb.rr.com [76.85.221.253]
6 ge-3-1-0.chcgileq-rtr1.kc.rr.com [76.85.220.133]
7 ae-4-0.cr0.chi10.tbone.rr.com [66.109.6.100]
8 ae-3-0.cr0.sjc10.tbone.rr.com [66.109.6.14]
9 ae-0-0.pr0.sjc10.tbone.rr.com [66.109.6.141]
10 gige-g5-6.core1.sjc2.he.net [216.218.135.225]
11 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 64.71.140.42
13 208.68.243.254
14 boinc2.ssl.berkeley.edu [208.68.240.18]

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 yoshikis-shanty [192.168.0.181]
0/ 100 = 0% |

1 7ms 0/ 100 = 0% 0/ 100 = 0% 76.47.32.1
0/ 100 = 0% |

2 6ms 0/ 100 = 0% 0/ 100 = 0% 76.47.32.1
0/ 100 = 0% |

3 7ms 0/ 100 = 0% 0/ 100 = 0% gig2-1.lnclne03-rtr1.neb.rr.com [76.85.220.89]
0/ 100 = 0% |

4 7ms 0/ 100 = 0% 0/ 100 = 0% RDC-24-169-240-172.neb.rr.com [24.169.240.172]
0/ 100 = 0% |

5 10ms 0/ 100 = 0% 0/ 100 = 0% ge-1-1-7.lnclne00-mx42.neb.rr.com [76.85.221.253]
0/ 100 = 0% |

6 27ms 0/ 100 = 0% 0/ 100 = 0% ge-3-1-0.chcgileq-rtr1.kc.rr.com [76.85.220.133]
0/ 100 = 0% |

7 28ms 0/ 100 = 0% 0/ 100 = 0% ae-4-0.cr0.chi10.tbone.rr.com [66.109.6.100]
0/ 100 = 0% |

8 81ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.sjc10.tbone.rr.com [66.109.6.14]
0/ 100 = 0% |

9 82ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.sjc10.tbone.rr.com [66.109.6.141]
0/ 100 = 0% |

10 91ms 0/ 100 = 0% 0/ 100 = 0% gige-g5-6.core1.sjc2.he.net [216.218.135.225]
0/ 100 = 0% |

11 89ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
0/ 100 = 0% |

12 94ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
4/ 100 = 4% |

13 94ms 8/ 100 = 8% 4/ 100 = 4% 208.68.243.254
0/ 100 = 0% |

14 95ms 4/ 100 = 4% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

Here's another from the east coast. ISP=Time Warner

No problems until it hits Berkeley.

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
0
1 cpe-174-097-216-001.nc.res.rr.com [174.97.216.1]
2 ten13-0-0-224.rlghnca-rtr1.nc.rr.com [66.26.32.186]
3 ge-5-3-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.0]
4 ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
5 ae-0-0.cr0.dca20.tbone.rr.com [66.109.6.31]
6 ae-3-0.cr0.nyc30.tbone.rr.com [66.109.6.29]
7 ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
8 66.109.6.10
9 ae-1-0.pr0.sjc10.tbone.rr.com [66.109.6.137]
10 gige-g5-6.core1.sjc2.he.net [216.218.135.225]
11 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 64.71.140.42
13 208.68.243.254
14 boinc2.ssl.berkeley.edu [208.68.240.13]

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 12ms 0/ 100 = 0% 0/ 100 = 0% cpe-174-097-216-001.nc.res.rr.com [174.97.216.1]
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% ten13-0-0-224.rlghnca-rtr1.nc.rr.com [66.26.32.186]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% ge-5-3-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.0]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.cr0.dca20.tbone.rr.com [66.109.6.31]
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.nyc30.tbone.rr.com [66.109.6.29]
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
0/ 100 = 0% |
8 104ms 0/ 100 = 0% 0/ 100 = 0% 66.109.6.10
0/ 100 = 0% |
9 99ms 0/ 100 = 0% 0/ 100 = 0% ae-1-0.pr0.sjc10.tbone.rr.com [66.109.6.137]
0/ 100 = 0% |
10 105ms 0/ 100 = 0% 0/ 100 = 0% gige-g5-6.core1.sjc2.he.net [216.218.135.225]
0/ 100 = 0% |
11 105ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
0/ 100 = 0% |
12 104ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
5/ 100 = 5% |
13 108ms 8/ 100 = 8% 3/ 100 = 3% 208.68.243.254
0/ 100 = 0% |
14 108ms 5/ 100 = 5% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.13]

---

Join the PACK!

If there's a problem on campus let's give them some proof.

What more proof do you need?????
The #10 cruncher in the world (me) has not been able to connect for days.

This is just simple stuff.........clear the pipe.

---

"Time is simply the mechanism that keeps everything from happening all at once."

This is mine from Daytona Beach.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
0 perry-PC [192.168.1.100]
1 192.168.1.1
2 adsl-65-161-1.dab.bellsouth.net [98.65.161.1]
3 70.159.207.25
4 ber01dab-ge-2-3.bellsouth.net [70.159.207.7]
5 12.83.22.188
6 12.83.9.73
7 74.175.192.130
8 cr1.ormfl.ip.att.net [12.122.106.6]
9 cr2.attga.ip.att.net [12.122.31.29]
10 attga01jt.ip.att.net [12.122.80.221]
11 192.205.37.82
12 Hurrican-Electric-LLC.TenGigabitEthernet1-4.ar2.SJC2.gblx.net [64.214.174.2
46]
13 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
14 64.71.140.42
15 208.68.243.254
16 boinc2.ssl.berkeley.edu [208.68.240.13]

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 perry-PC [192.168.1.100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% adsl-65-161-1.dab.bellsouth.net [9
8.65.161.1]
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% 70.159.207.25
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% ber01dab-ge-2-3.bellsouth.net [70.
159.207.7]
0/ 100 = 0% |
5 17ms 0/ 100 = 0% 0/ 100 = 0% 12.83.22.188
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 12.83.9.73
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% 74.175.192.130
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.ormfl.ip.att.net [12.122.106.6
]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.attga.ip.att.net [12.122.31.29
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% attga01jt.ip.att.net [12.122.80.22
1]
0/ 100 = 0% |
11 41ms 2/ 100 = 2% 2/ 100 = 2% 192.205.37.82
0/ 100 = 0% |
12 92ms 2/ 100 = 2% 2/ 100 = 2% Hurrican-Electric-LLC.TenGigabitEt
hernet1-4.ar2.SJC2.gblx.net [64.214.174.246]
0/ 100 = 0% |
13 109ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]
0/ 100 = 0% |
14 104ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
6/ 100 = 6% |
15 107ms 8/ 100 = 8% 2/ 100 = 2% 208.68.243.254
0/ 100 = 0% |
16 94ms 6/ 100 = 6% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.24
0.13]

Trace complete.

C:\Windows\system32>

---

PROUD MEMBER OF Team Starfire World BOINC

Just for fun, Last night at 22:44:44 UTC I was able to upload and report all mine. I also got a bunch of new work. Most of those were done again overnight. Since then I have one ready to report and around 24 waiting to upload. (BOINC did this on it's own, no button pushing on my part.)

---

PROUD MEMBER OF Team Starfire World BOINC

Here is my result from Germany:

C:\Users\Ralf>pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13]
über maximal 30 Abschnitte:
0 Keine Ressourcen.

So the pathping had no result at all due to no resources.

Regards

Ralf

Vorinezsh, Russia
Трассировка маршрута к boinc2.ssl.berkeley.edu [208.68.240.13]
с максимальным числом прыжков 30:
0 computer-24743d [192.168.1.2]
1 192.168.1.1
2 lo100.asr1006-1.a73.vsi.ru [80.82.57.58]
3 te2-0-0.818.ne40e-2.a53.hw.vsi.ru [80.82.53.18]
4 crs1-ne40e-2.vsi.ru [80.82.56.161]
5 77.51.255.97
6 ae5-222.RT.V10.MSK.RU.retn.net [87.245.253.237]
7 ae2-6.RT.TC1.STO.SE.retn.net [87.245.233.134]
8 netnod-ix-ge-a-sth-1500.he.net [194.68.123.187]
9 10gigabitethernet3-3.core1.fra1.he.net [72.52.92.233]
10 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
11 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
12 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
13 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
14 * 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
15 64.71.140.42
16 208.68.243.254
17 boinc2.ssl.berkeley.edu [208.68.240.13]

Подсчет статистики за: 425 сек. ...
Исходный узел Маршрутный узел
Прыжок RTT Утер./Отпр. % Утер./Отпр. % Адрес
0 computer-24743d [192.168.1.2]
0/ 100 = 0% |
1 1мс 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 23мс 0/ 100 = 0% 0/ 100 = 0% lo100.asr1006-1.a73.vsi.ru [80.82.
57.58]
0/ 100 = 0% |
3 24мс 0/ 100 = 0% 0/ 100 = 0% te2-0-0.818.ne40e-2.a53.hw.vsi.ru
[80.82.53.18]
10/ 100 = 10% |
4 25мс 12/ 100 = 12% 2/ 100 = 2% crs1-ne40e-2.vsi.ru [80.82.56.161]

0/ 100 = 0% |
5 40мс 18/ 100 = 18% 8/ 100 = 8% 77.51.255.97
0/ 100 = 0% |
6 42мс 16/ 100 = 16% 6/ 100 = 6% ae5-222.RT.V10.MSK.RU.retn.net [87
.245.253.237]
0/ 100 = 0% |
7 124мс 10/ 100 = 10% 0/ 100 = 0% ae2-6.RT.TC1.STO.SE.retn.net [87.2
45.233.134]
1/ 100 = 1% |
8 --- 100/ 100 =100% 89/ 100 = 89% netnod-ix-ge-a-sth-1500.he.net [19
4.68.123.187]
0/ 100 = 0% |
9 --- 100/ 100 =100% 89/ 100 = 89% 10gigabitethernet3-3.core1.fra1.he
.net [72.52.92.233]
0/ 100 = 0% |
10 97мс 11/ 100 = 11% 0/ 100 = 0% 10gigabitethernet1-2.core1.par1.he
.net [72.52.92.89]
1/ 100 = 1% |
11 95мс 12/ 100 = 12% 0/ 100 = 0% 10gigabitethernet1-3.core1.lon1.he
.net [72.52.92.33]
1/ 100 = 1% |
12 160мс 13/ 100 = 13% 0/ 100 = 0% 10gigabitethernet2-3.core1.nyc4.he
.net [72.52.92.77]
0/ 100 = 0% |
13 243мс 18/ 100 = 18% 5/ 100 = 5% 10gigabitethernet3-1.core1.sjc2.he
.net [72.52.92.25]
0/ 100 = 0% |
14 245мс 13/ 100 = 13% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]
5/ 100 = 5% |
15 252мс 18/ 100 = 18% 0/ 100 = 0% 64.71.140.42
1/ 100 = 1% |
16 250мс 20/ 100 = 20% 1/ 100 = 1% 208.68.243.254
0/ 100 = 0% |
17 259мс 19/ 100 = 19% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.24

---