I'm getting the same as well. It appears the event is bugged pretty badly. Hopefully there is some visibility on this problem or even an emergency maintenance.