Yes, this is happening again.
As we know last week, it somehow fixed itself. So it was assumed it was an Amazon site issue.
Now it seems to be happening again.
I highly doubt a fix will come this week in SF, mainly because the issue comes and goes, so if it keeps happening, users may be waiting sometime for a proper fix.
But I hope SF proves me wrong with a fix this week.