Jim, where is Mieps wet Noodle.

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

I have not had any communication with SETI for several days. Other projects working fine. Is there a problem?

---

I still can't connect normally since June 16th And Now the PROXYs are not working for me.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

I have not had any communication with SETI for several days. Other projects working fine. Is there a problem?

No problems here at all as mine have been feeding very well indeed.

Cheers.

---

Wonder if Matt (or anyone) can provide an update on this Huricane Electric connection problem as it has been more than 2 weeks since his original posting.

---

Boinc....Boinc....Boinc....Boinc....

I have not had any communication with SETI for several days. Other projects working fine. Is there a problem?

No problems here at all as mine have been feeding very well indeed.

Cheers.

That's The Problem...There are Still a Few who can't.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

I have not had any communication with SETI for several days. Other projects working fine. Is there a problem?

No problems here at all as mine have been feeding very well indeed.

Cheers.

That's The Problem...There are Still a Few who can't.

This machine connected and reported this morning:

5531969

---

7/15/2011 9:03:39 AM | SETI@home | update requested by user
7/15/2011 9:03:40 AM | SETI@home | Sending scheduler request: Requested by user.
7/15/2011 9:03:40 AM | SETI@home | Requesting new tasks for CPU and ATI GPU
7/15/2011 9:04:02 AM | SETI@home | Scheduler request failed: Couldn't connect to server
7/15/2011 9:04:06 AM | | Project communication failed: attempting access to reference site
7/15/2011 9:04:07 AM | | Internet access OK - project servers may be temporarily down.

As I said, I have not been able to get through for days. Other projects working fine, Einstein, etc., no problems. Have been doing this for a long time, I'm not a newbie, although I've been away for a few years.

---

Hello yours,
I have the same problem since a few days. Other projects like einstein@home and cosmology@home are working.



1. Are you able to reach ANY of the upload, download, or scheduling servers?

bionc message:

wal-seti1

2180 SETI@home 15.07.2011 23:06:54 Started upload of 17ap11ah.11150.476.8.10.179_1_0
2181 15.07.2011 23:06:57 Project communication failed: attempting access to reference site
2182 15.07.2011 23:06:58 Internet access OK - project servers may be temporarily down.
2183 SETI@home 15.07.2011 23:07:15 Temporarily failed upload of 17ap11ah.11150.476.8.10.180_0_0: connect() failed
2184 SETI@home 15.07.2011 23:07:15 Backing off 26 min 2 sec on upload of 17ap11ah.11150.476.8.10.180_0_0
2185 15.07.2011 23:07:19 Project communication failed: attempting access to reference site
2186 15.07.2011 23:07:20 Internet access OK - project servers may be temporarily down.


2. When did you start having this problem?

since monday

3. What is your ISP?

Germany T-COM

4. What is your geographic location?

Town: Heidelberg
Country: Germany


5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?

>ping 208.68.240.13

Ping wird ausgeführt für 208.68.240.13 mit 32 Bytes Daten:
Antwort von 208.68.240.13: Bytes=32 Zeit=291ms TTL=53
Antwort von 208.68.240.13: Bytes=32 Zeit=283ms TTL=53
Antwort von 208.68.240.13: Bytes=32 Zeit=262ms TTL=53
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.13:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1
(25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 262ms, Maximum = 291ms, Mittelwert = 278ms

>ping 208.68.240.16

Ping wird ausgeführt für 208.68.240.16 mit 32 Bytes Daten:
Antwort von 208.68.240.16: Bytes=32 Zeit=227ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=225ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=224ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=223ms TTL=53

Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 223ms, Maximum = 227ms, Mittelwert = 224ms

>ping 208.68.240.18

Ping wird ausgeführt für 208.68.240.18 mit 32 Bytes Daten:
Antwort von 208.68.240.18: Bytes=32 Zeit=225ms TTL=53
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.18:
Pakete: Gesendet = 4, Empfangen = 1, Verloren = 3
(75% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 225ms, Maximum = 225ms, Mittelwert = 225ms

>ping 208.68.240.20

Ping wird ausgeführt für 208.68.240.20 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Antwort von 208.68.240.20: Bytes=32 Zeit=225ms TTL=53
Antwort von 208.68.240.20: Bytes=32 Zeit=227ms TTL=53
Antwort von 208.68.240.20: Bytes=32 Zeit=224ms TTL=53

Ping-Statistik für 208.68.240.20:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1
(25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 224ms, Maximum = 227ms, Mittelwert = 225ms


6. How about traceroutes of the above four addresses?

C:\Users\wal>tracert 208.68.240.13

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13] über maximal 30 Absc
hnitte:

1 2 ms 3 ms 2 ms 192.168.2.1
2 9 ms * 9 ms 217.0.116.37
3 10 ms 12 ms 11 ms 217.0.66.170
4 133 ms 11 ms 11 ms f-ea5-i.F.DE.NET.DTAG.DE [62.154.16.165]
5 12 ms 11 ms 11 ms 62.156.138.94
6 11 ms 14 ms 17 ms ffm-bb1-link.telia.net [80.91.251.150]
7 107 ms 109 ms 108 ms ash-bb1-link.telia.net [80.91.246.62]
8 183 ms 185 ms 183 ms sjo-bb1-link.telia.net [213.155.130.211]
9 183 ms 185 ms 182 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 314 ms 280 ms 280 ms 64.71.140.42
11 232 ms * 224 ms 208.68.243.254
12 * 296 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
13 287 ms 293 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
14 286 ms * 309 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Ablaufverfolgung beendet.

C:\Users\wal>tracert 208.68.240.16

Routenverfolgung zu setiboincdata.ssl.berkeley.edu [208.68.240.16] über maximal
30 Abschnitte:

1 3 ms 4 ms 8 ms 192.168.2.1
2 * 9 ms 10 ms 217.0.116.37
3 11 ms 12 ms 10 ms 217.0.66.166
4 15 ms 12 ms 10 ms f-ea5-i.F.DE.NET.DTAG.DE [62.154.16.165]
5 13 ms 11 ms 10 ms 62.156.138.94
6 12 ms 11 ms 11 ms ffm-bb2-link.telia.net [80.91.251.158]
7 108 ms 107 ms 109 ms ash-bb1-link.telia.net [80.91.246.62]
8 183 ms 184 ms 182 ms sjo-bb1-link.telia.net [213.155.130.213]
9 185 ms 190 ms 182 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 183 ms 183 ms 182 ms 64.71.140.42
11 225 ms 225 ms 225 ms 208.68.243.254
12 * 231 ms 225 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Ablaufverfolgung beendet.

C:\Users\wal>tracert 208.68.240.18

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18] über maximal 30 Absc
hnitte:

1 3 ms 2 ms 3 ms 192.168.2.1
2 9 ms 10 ms 9 ms 217.0.116.37
3 11 ms 10 ms 12 ms 217.0.66.162
4 13 ms 11 ms 12 ms f-ea5-i.F.DE.NET.DTAG.DE [62.154.16.161]
5 11 ms 67 ms 11 ms 62.156.138.94
6 11 ms 11 ms 12 ms ffm-bb2-link.telia.net [80.91.251.162]
7 108 ms 107 ms 107 ms ash-bb1-link.telia.net [80.91.246.58]
8 182 ms 185 ms 182 ms sjo-bb1-link.telia.net [80.91.248.188]
9 182 ms 190 ms 183 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 183 ms 184 ms 183 ms 64.71.140.42
11 225 ms * 226 ms 208.68.243.254
12 225 ms 222 ms 225 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Ablaufverfolgung beendet.

C:\Users\wal>tracert 208.68.240.20

Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.20] über maximal 30 A
bschnitte:

1 9 ms 2 ms 4 ms 192.168.2.1
2 10 ms 11 ms 9 ms 217.0.116.37
3 12 ms 11 ms 11 ms 217.0.66.166
4 11 ms 11 ms 11 ms f-ea5-i.F.DE.NET.DTAG.DE [62.154.16.161]
5 14 ms 11 ms 11 ms ffm-b6-link.telia.net [213.248.90.129]
6 62 ms 12 ms 11 ms ffm-bb1-link.telia.net [80.91.251.154]
7 108 ms 108 ms 108 ms ash-bb1-link.telia.net [80.91.246.60]
8 182 ms 182 ms 181 ms sjo-bb1-link.telia.net [213.155.130.213]
9 183 ms 188 ms 183 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 183 ms 184 ms 183 ms 64.71.140.42
11 * 226 ms 224 ms 208.68.243.254
12 200 ms 225 ms 219 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Ablaufverfolgung beendet.




Hope you have a chance to fix it.

thanks
juergen

I have made another inquiry regarding the HE comms problems.
I am hoping some news may be forthcoming....no promises.
But I pushed the button again.

---

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

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Auser>tracert 208.68.240.13

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

1 1 ms 1 ms <1 ms <myIP>
2 9 ms 8 ms 8 ms bras1-l0.chi2ca.sbcglobal.net [151.164.185.228]

3 7 ms 7 ms 6 ms dist1-vlan50.chi2ca.sbcglobal.net [67.126.80.66]

4 8 ms 7 ms 6 ms 151.164.53.102
5 30 ms 30 ms 30 ms ppp-151-164-52-163.rcsntx.swbell.net [151.164.52
.163]
6 32 ms 31 ms 30 ms v304.core1.sjc2.he.net [64.62.158.141]
7 40 ms 30 ms 30 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
8 31 ms 31 ms 31 ms 64.71.140.42
9 72 ms 72 ms 72 ms 208.68.243.254
10 * 72 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
11 71 ms * * boinc2.ssl.berkeley.edu [208.68.240.13]
12 70 ms 79 ms 71 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Users\Auser>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 <myIP>
2 9 ms 8 ms 8 ms bras1-l0.chi2ca.sbcglobal.net [151.164.185.228]

3 7 ms 6 ms 7 ms dist1-vlan60.chi2ca.sbcglobal.net [67.126.80.130
]
4 7 ms 7 ms 7 ms 151.164.53.102
5 30 ms 30 ms 30 ms ppp-151-164-52-165.rcsntx.swbell.net [151.164.52
.165]
6 35 ms 30 ms 30 ms v304.core1.sjc2.he.net [64.62.158.141]
7 35 ms 30 ms 30 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
8 31 ms 30 ms 31 ms 64.71.140.42
9 72 ms 71 ms 71 ms 208.68.243.254
10 * * 144 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

C:\Users\Auser>tracert 208.68.240.18

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

1 1 ms <1 ms 1 ms <myIP>
2 8 ms 8 ms 8 ms bras1-l0.chi2ca.sbcglobal.net [151.164.185.228]

3 6 ms 7 ms 7 ms dist2-vlan60.chi2ca.sbcglobal.net [67.126.80.131
]
4 7 ms 7 ms 7 ms 151.164.53.104
5 30 ms 29 ms 30 ms ppp-151-164-52-165.rcsntx.swbell.net [151.164.52
.165]
6 34 ms 31 ms 30 ms v304.core1.sjc2.he.net [64.62.158.141]
7 30 ms 38 ms 30 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
8 31 ms 31 ms 30 ms 64.71.140.42
9 70 ms 72 ms 69 ms 208.68.243.254
10 71 ms 70 ms 72 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

C:\Users\Auser>tracert 208.68.240.20

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

1 <1 ms <1 ms 1 ms <myIP>
2 9 ms 10 ms 8 ms bras1-l0.chi2ca.sbcglobal.net [151.164.185.228]

3 7 ms 7 ms 7 ms dist1-vlan60.chi2ca.sbcglobal.net [67.126.80.130
]
4 7 ms 7 ms 6 ms 151.164.53.102
5 30 ms 30 ms 29 ms ppp-151-164-52-161.rcsntx.swbell.net [151.164.52
.161]
6 38 ms 31 ms 30 ms v304.core1.sjc2.he.net [64.62.158.141]
7 35 ms 30 ms 30 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
8 31 ms 31 ms 30 ms 64.71.140.42
9 65 ms 73 ms 72 ms 208.68.243.254
10 73 ms 72 ms 71 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Auser>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:
Reply from 208.68.240.13: bytes=32 time=73ms TTL=56
Reply from 208.68.240.13: bytes=32 time=78ms TTL=56
Reply from 208.68.240.13: bytes=32 time=68ms TTL=56
Request timed out.

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

C:\Users\Auser>ping 208.68.240.16

Pinging 208.68.240.16 with 32 bytes of data:
Reply from 208.68.240.16: bytes=32 time=69ms TTL=56
Reply from 208.68.240.16: bytes=32 time=73ms TTL=56
Reply from 208.68.240.16: bytes=32 time=71ms TTL=56
Reply from 208.68.240.16: bytes=32 time=72ms TTL=56

Ping statistics for 208.68.240.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 73ms, Average = 71ms

C:\Users\Auser>ping 208.68.240.18

Pinging 208.68.240.18 with 32 bytes of data:
Reply from 208.68.240.18: bytes=32 time=35ms TTL=56
Reply from 208.68.240.18: bytes=32 time=73ms TTL=56
Reply from 208.68.240.18: bytes=32 time=71ms TTL=56
Reply from 208.68.240.18: bytes=32 time=72ms TTL=56

Ping statistics for 208.68.240.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 73ms, Average = 62ms

C:\Users\Auser>ping 208.68.240.20

Pinging 208.68.240.20 with 32 bytes of data:
Reply from 208.68.240.20: bytes=32 time=34ms TTL=56
Reply from 208.68.240.20: bytes=32 time=72ms TTL=56
Reply from 208.68.240.20: bytes=32 time=73ms TTL=56
Reply from 208.68.240.20: bytes=32 time=72ms TTL=56

Ping statistics for 208.68.240.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 73ms, Average = 62ms

C:\Users\Auser>nslookup 208.68.240.13
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: <myIP>
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

---

Janice

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 26 ms 25 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 26 ms 25 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 26 ms 25 ms 26 ms rc-mlx8-ve31.serial.blue.net [66.38.58.169]
5 26 ms 26 ms 26 ms h1.126.55.139.static.ip.windstream.net [139.55.1
26.1]
6 29 ms 29 ms 28 ms h25.222.90.75.static.ip.windstream.net [75.90.22
2.25]
7 28 ms 29 ms 29 ms h36.254.213.151.static.ip.windstream.net [151.21
3.254.36]
8 47 ms 46 ms 47 ms h14.254.213.151.static.ip.windstream.net [151.21
3.254.14]
9 47 ms 46 ms 47 ms ip65-47-204-81.z204-47-65.customer.algx.net [65.
47.204.81]
10 47 ms 46 ms 46 ms v306.core1.dal1.he.net [64.71.189.217]
11 107 ms 101 ms 100 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
12 101 ms 100 ms 100 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
13 114 ms 110 ms 114 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

This is still where I time out on all 4 addys...Also all PINGs still time out.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

It looks like you got one to work Jim.

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

It looks like you got one to work Jim.

It was through a PROXY I had forgot to disable.
I may have to try that one on the others again.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Good luck Jim. I sure hope this get's resolved soon.

Now where is Matt with a status update?

---

Pluto will always be a planet to me.

Seti Ambassador
Not to late to order an Anni Shirt

I JUST got the rest of my work uploaded through a very slow PROXY. I hope they find an answer this problem Soon.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

I JUST got the rest of my work uploaded through a very slow PROXY. I hope they find an answer this problem Soon.

While I strongly doubt it's anything to do with the problem, I find it interesting that a traceroute going the other way toward you takes a different path:

core1.pao1.he.net> traceroute 66.38.56.1 numeric
Target  66.38.56.1
Hop Start   1
Hop End 30
Hop Packet 1    Packet 2    Packet 3    Hostname
1   5 ms    <1 ms   <1 ms   10gigabitethernet4-1.core1.sjc2.he.net (72.52.92.70)
2   1 ms    <1 ms   <1 ms   206.111.6.165.ptr.us.xo.net (206.111.6.165)
3   13 ms   24 ms   25 ms   207.88.14.233.ptr.us.xo.net (207.88.14.233)
4   83 ms   79 ms   86 ms   vb15.rar3.dallas-tx.us.xo.net (207.88.12.45)
5   83 ms   79 ms   85 ms   te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1)
6   86 ms   75 ms   88 ms   216.156.0.234.ptr.us.xo.net (216.156.0.234)
7   75 ms   88 ms   68 ms   209.119.163.54
8   68 ms   112 ms  68 ms   h12.207.190.173.ip.windstream.net (173.190.207.12)
9   93 ms   87 ms   87 ms   h188.28.189.173.static.ip.windstream.net (173.189.28.188)
10  86 ms   87 ms   87 ms   h4.254.213.151.static.ip.windstream.net (151.213.254.4)
11  87 ms   79 ms   78 ms   h22.254.213.151.static.ip.windstream.net (151.213.254.22)
12  77 ms   76 ms   86 ms   h33.254.213.151.static.ip.windstream.net (151.213.254.33)
13  83 ms   79 ms   87 ms   h24.222.90.75.static.ip.windstream.net (75.90.222.24)
14  82 ms   79 ms   87 ms   h2.126.55.139.static.ip.windstream.net (139.55.126.2)
15  82 ms   79 ms   86 ms   bbtel-6500-vlan31.serial.blue.net (66.38.58.170)
16  82 ms   80 ms   86 ms   66-38-56-1.static.bbtel.com (66.38.56.1)

That was generated from http://lg.he.net by selecting "Equinix Palo Alto" as the originating router, and the first external hop in your message 1128525 as the target.

It seems everyone's trace routes reach core1.pao1.he.net most of the time, so the problem must somehow be between there and SSL. What we cannot tell is which side of the link is failing. It could be packets are not being sent on to SSL, or the answering packets from SSL are being dropped. I wonder if Matt has tried doing trace routes from the lab to check that out, though perhaps the Apache logs have enough info to distinguish those possibilities.

                                                                Joe

I JUST got the rest of my work uploaded through a very slow PROXY. I hope they find an answer this problem Soon.

The problem is since over one month ... it seems nobody work on the problem. it have only a little bit of user the connect-problem who want to connect Berkeley. that is not to heavy ..... [that is ironic]

---

I JUST got the rest of my work uploaded through a very slow PROXY. I hope they find an answer this problem Soon.

The problem is since over one month ... it seems nobody work on the problem. it have only a little bit of user the connect-problem who want to connect Berkeley. that is not to heavy ..... [that is ironic]

Since the problem isn't at SETI, who is going to work on it?

Yes, we would love to know what HE has done with the trouble ticket, but unless Matt or Jeff calls them and posts the answer here we never will.

It wouldn't surprise me to find out it is a filter at a PAIX router that is sensing a DDOS attack on SETI and attempting to deflect it. It may be very hard to debug absent a pile of timely trace routes and some good log files.

---

I suspect there is a mid-point router(that would mean in an ISP/backbone) pointing the wrong direction. Identifying between which locations is vital
in order to even report the problem. And yes this can easily be one direction that has a problem and works just fine in the opposite direction.

The reporting process is further complicated by technicians on the broadband pointing figures and say their equipment is fine, must be someone elses problem.
I would be shocked if once identified what is getting mis-routed to where, it did not take numerous reports and repeat reports to get someone to actually look into it.

---

Janice