Yes, we are aware of that. It was reported in this thread and some tickets. We are in conversation with Microsoft - they are responsive but looks like the issue is back after yesterday's successful attempt to eliminate it.
We'll keep trying to make Microsoft resolve this asap. Sorry for any inconvenience.