Sandbox down - No error returned

[bendiy]

Reference API isn't working:
http://developer.authorize.net/api/reference/index.html

[bendiy]

The "response" message is "The custom error module does not recognize this error.".

[bendiy]

https://status.authorize.net/ does not report any outages.

[adamsilkstart]

Yup, seeing the same thing.  As well, going to https://apitest.authorize.net/xml/v1/request.api in a browser will show the same 503 error.

[bendiy]

And it's back...

[RichardH]

@bendiy @adamsilkstart Are you still experiencing any issues connecting to the sandbox?

Richard

[bendiy]

@RichardH It started working again. See my last post above.

Is there any way you can get https://status.authorize.net/ to report outages in the Sandbox. Every time it has been down, https://status.authorize.net/ aways says it up.

In this case, https://apitest.authorize.net/xml/v1/request.api was returning a 503. Other times, that URL is up, but any API requests to it returns an error. Your https://www.statuspage.io/ config for the Sandbox needs to be reconfigured to make an actual API request, not to see if the URL is up.

[RichardH]

@bendiy

Yes.  Our operations team is investigating for a cause.

Richard

[adamsilkstart]

Yes it appears to be working now.  I second the notion that the Authorize.net status page should be updated when situations like this happen.  The fact that I had to go to a message board and search for a thread to find out that someone else was having the same problem really is not great.

[RichardH]

Hello @adamsilkstart

We agree.  In this particular case, the problem was with a network configuration change that did not trigger alerts.

Richard