Super strange. I wrote a script to test like immediate cold tunes over deep link, and it started acting up again today.
But the five minute teardowns still are clear, so I don't know. They must be two separate issues, or one must be like an AB test server side sort of thing. The readiness gate I added to the Osprey deep links script will handle that. Also, ADBTuner is pretty much immune because it already waits a few seconds before sending a deep link anyway, but I'm sure that can be extended with just a simple sleep command in the configuration. I also wrote kind of a new readiness gate that's a little bit faster if anyone wants to try it, if you're running into this issue.
$adbTarget shell 'end=$(($(date +%s)+10)); n=0; while [ $(date +%s) -lt $end ]; do dumpsys media_session 2>/dev/null | grep -q "PlaybackState {state=3" && exit 0; n=$((n+1)); [ $((n % 10)) -eq 0 ] && dumpsys audio 2>/dev/null | grep -qE "pack: com.att.tv.openvideo.*gain: GAIN " && exit 0; done; exit 1'
if [[ $? -ne 0 ]]; then
touch "$streamerNoPort/adbCommunicationFail"
echo "Readiness gate timed out for $streamerIP -- failing tune so ah4c can try the next tuner"
exit 2
fi
You know what just clicked? My DMA is the one hosting the World Cup. I'm in the New York metro, so if something is broken, I guess it kind of makes sense. I'm literally 20 minutes from the stadium. It just seems too coincidental that I'd be having issues related to digital ad insertion right around the World Cup, and I'm 20 minutes away from the World Cup, literally.
Update: I did some more debugging and figured out my tunes were all pinned to their West Coast Yospace (AWS) servers for most of the day, whereas yesterday it was East Coast. So it seems like, from what I can infer, something in Ashburn was fixed in US-East-1, and now they seem to have rolled out a patch to Oregon, US-West-2. I mean, this is what I'm getting from running tcpdump like a madman and tuning over and over. This also explains why it's only affecting me and no one else, because it seems to just be isolated to my market, and maybe some other markets that who knows about. But in our small community here, I must be the only market affected. 
I also noticed around 3:00 PM Eastern, noon Pacific, things started to get back to normal. It stopped tearing down. Everything stopped wedging again after clearing out some stuff on my boxes like I had to last time, and it started behaving normally. Then I noticed around 5:00, 6:00 PM Eastern, I started getting East Coast servers again. So super weird, but kind of makes sense that they would fix the primary AWS region and then fix the secondary AWS region a day later before the big World Cup final.
that was 25yrs ago and it still works, and the label tape is still expensive but worth it.
