This issue seemed to have resolved on its own. I don’t really have an answer to why this happened. I’m going to assume it was a carrier issue limited to a small group of users.