Hello @Nigel ,
Thanks for reporting this. Just like you've mentioned before, the suggested workaround is indeed to use Edge or Firefox if you're being affected by this.
I've actually worked on this last week with our Ops as we've detected some impact before, and that time everyone who was affected confirmed this to be resolved across the EU environment. I am curious it returned now, so I'll check with Ops once again.