> according to CF, it's not an issue...?!

Definitely not the case.

I work at CloudFlare, not in DNS or on this code, and have mentioned this incident in the all-company chat. There is a healthy conversation happening there and it turns out a fix was already in the works for the underlying issue.

adanto6840 has supplied the support ticket number (thank you), and this specific incident is also being reviewed.