I believe a number of other people have also reported this within the past month. Considering that it took 6 months for the city to replace a street lamp that I reported, good luck.

This is, again, a report of the same -- unaddressed -- problem reported as Issue I.D. 3370820 and former (now closed, even though not fixed) Issue I.D. 3340727.

What is the delay here? Is it that these signals are on state roads, rather than local roads, and it has to be the State of Connecticut that will come to fix the crossing lights? We might as well wait until the sky falls.

This is a DANGEROUS intersection, where cars are completely out of control. There is no police traffic enforcement, and now, there are no functioning pedestrian crossing signals.

Why will no one pay attention, to an issue now reported multiple times?

I don't think that anyone REALLY pays attention to the majority of the "seeclickfix" issues. It's a "feel good", "let's pretend that we're actually doing something" bit of nonsense.

Hey, out there: in Traffic and Parking, in the police department, in Public Works street maintenance -- anyone? Who will at least post some WORDS, if not actually take any action, that would indicate that someone has actually seen that this issue has been reported?

I've noticed that often there can be at least some sort of acknowledgement posted about seeclickfix issues -- why not now? Is it a matter of everyone just looking the other way? Is there a lot of buck-passing going on? Is there a refusal to get involved in what really is a State issue (if so, why can't someone at least just say so?). Or is it actually that no one even pays attention to begin with? Somehow I suspect it is one of the first three.

Looking at the stats, TT and P is actually quite responsive. This particular issue was only reported 6 hours ago.

This particular light has already been reported a NUMBER of times, although with different street addresses—Fountain vs. Forest, etc.).

Yes, if you look at my first post here, you can see that I cite two other case I.D numbers this issue has had here at seeclickfix over the past couple weeks. They're all about the same problem. At first, a crossing signal post got knocked down by a car. That DID get fixed pretty quickly, in the sense that the post got put back upright -- and then the case got closed.

But the signals themselves apparently have not been put back into working order. That is what the fuss here is about.

Can you describe what is not functioning with the light?

When you push any of the walk buttons on any of the corners, they do not trigger the walk signal. It stopped working when the walk signal at the corner of fountain and Forrest was destroyed in a traffic incident several weeks ago. The damaged signal was replaced within a couple of days. But they must not have rewired it correctly.

Stand on street corner. Push crossing button. No audible beep. Nothing happens. Big red "Stop" hand on crossing screen at opposite corner (which IS lit) remains. Doesn't change. At all.

Take life into hands and cross to the next corner. Repeat procedure. Again, no beep from the push button. And no change in the crossing sign.

Repeat multiple times, on multiple corners. Same thing, always. No beeps, and no changes in the red "Stop" hands.

All this is true at all the corners of Fountain/Dayton/Forest (I just verified, myself) -- and also at the intersection of Fountain and Vista Terrace, where I'm pretty sure the signals are tied into the same system.

Traffic lights for cars work. Crossing lights for pedestrians do not.

The signal buttons do not make a beep when you push them. The crossing screens are lit, but their display of a big red "Stop" hand does not change.

This is true at all the corners of Fountain/Dayton/Forest -- and also at the intersection of Fountain and Vista Terrace, where I'm pretty sure the signals are tied into the same system.

Traffic lights for cars do work. Crossing lights for pedestrians do not.

This issue has been resolved.