Unstable routing causing open ended response times - previously reported.

I have screenshots, videos, traceroutes.    That should not be necessary.  Check the logs for po-400-xar01.londonderry.nh.boston.comcast.net.  The correct next hop is be-303-arsc1.needham.ma.boston.comcast.net, but the NH node takes over a minute most times to remember this.   When my response time goes open ended to YouTube, I abate my frustration by opening PingPlotter and watching the darned NH node finally discover the Needham node for the hundredth time, and as usual drop packets trying to reach it.   I cannot understand how you folks can tolerate this obvious issue over long periods of time!