I spoke with UPS tech-support yesterday evening and they confirmed that they're having issues with the 'legacy' endpoint (https://www.ups.com/using/services/rave/qcostcgi.cgi). They're working to find the 'root cause' and don't have an ETA until they know what the base issue is.
My suggestion, based on the email received from UPS earlier this week, is that anyone using the UPS shipping method (whose communication with UPS will be updated over the summer) should:
1. Register at UPS for an account: https://wwwapps.ups.com/doapp/signup?sysid=myups
2. Once you're registered, Request an Access Key using this link: https://www.ups.com/upsdeveloperkit?loc=en_US
3. Write down the XML Access Key; you will need that key to enable the UPS XML shipping module.
Note that UPS will no longer distribute new access keys after June 4, 2023! If you are using UPS to ship your products and this legacy endpoint fails again, you will be sh*t-out-of-luck!
I did put in a request to the tech-support reps that I spoke with to pretty-please provide an extension to that date, but that's going to depend on what the development group says.
Bookmarks