This has now been fixed. Thanks for your ticket submissions and confirmations in this thread.