We have workarounds, but I'd be surprised if the issue were specific to our instance.