We have found the source of the issues which related to customers who use Shortest Distance checks that run via MapQuest API, not Google Maps. An issue with MapQuest authorization API caused requests to fail in a manner that was not anticipated. We are implementing changes that will, like other parts of our code, ensure that Google values are still obtained as a failsafe.
This also explains why only select customers saw this issue, and why it only applied to certain Trip Types within the system. We are going to montior the issue and ensure there are no further issues with MapQuest API calls. We will soon implement the additional changes to ensure a failsafe should such an issue happen again.
