This sounds like (potentially) a data center synchronisation issue where cached data related to mentions is served from one server but not others. Twitter is an eventually-consistent system rather than a guaranteed-consistent one. Sometimes, situations like this may occur between API calls based on routing.