Nope, it was a network issue between the web site and KDB - it a rare event that has actually happened before - it's been on the todo list to fix it for a while, but since it's so rare, it's below what I'm working on at the moment