#7 - June 25, 2016, 4:30 a.m.
Hey all,
I can confirm that we are aware of these errors and our development team is currently investigating this. While I don't have any ETA on a resolution for this we do appreciate your patience and hopefully they can identify the cause and get it resolved ASAP.