Thanks @RichardH. It is really bizarre. I can access the file directly
from the browser, but our monitors are returning a 502 response. Looks
like its on the monitors end. Either way, the script is really slow aand
we prob should be loading it async ...
We've been experiencing outages as well with the verify.authorize.net
host. Our monitors have been alerting a 502 gateway error when
requesting http://verify.authorize.net/anetseal/seal.js for the last
couple weeks. See screenshot: http://screencast....