Last night's issue was indeed fixed. This is a new one, and I've reported it as well.