Based on the responses so far, it's looking like this might be an ISP-related issue, however we are continuing to check on our side. For those affected, please keep me in the loop!