We believe this issue is now resolved.  Apologies for the inconvenience caused and IT are investigating to prevent this issue again.