Looks like we may have identified the issue - we're working on a fix and will be closely monitoring things in the meantime.