Yes! The new signals have SIGNIFICANTLY less walk time. This intersection is hard to cross due to turning vehicles. With only 10-ish seconds to do it it's nearly impossible at rush house without jumping right out. We prefer to wait and make eye contact with turning cars. The walk signals used to be more like 50 seconds. There are also times now when the opposing light is red and it's a "don't walk" which just encourages jay walking.

Thank you for reporting your concern to City of Cambridge via Commonwealth Connect. We have reviewed the information you provided our staff and will be investigating this issue further.

Thanks for your report. When this intersection was swapped over to a new traffic controller the wrong timing plan was input. The correct one should be running now but please re-open if this is still an issue.

There has been no change to the timing. The previously 45 second cycle remains at 10 seconds as originally reported.

Thank you for reporting your concern to City of Cambridge via Commonwealth Connect. We have reviewed the information you provided our staff and will be investigating this issue further.

Agreed - it it still giving a 10 second walk time at the start of the light cycle. The end result is rushing across rather than having time to survey for turning cars. Just this morning a car turning left off Concord came at me while I was in the middle of Huron (with 2 seconds remaining on the walk). Please return to the full cycle walk signal. The balance of pedestrians and cars at this intersection was not broken so please revert to what was there before the new light structures went up. A change like this is going to cause an accident. I have taught my child how to cross this intersection by waiting for the walk, making eye contact with any stopped cars and then proceeding carefully while watching for turning cars. This new cycle encourages people to dash across and there are simply too many cars making turns for that to be good.

Thank you for reporting this issue to us. We are pleased to report back to you that this issue is now resolved.