Authorize.net down for the count

Another DDoS Attack?

[joestern]

I've been on hold with them for 15 minutes now waiting for a staus update.

The first time I called, I got the credit department. They told me that all calls were accidentally routed to them. Did some hacker really get to them in two ways?

[joestern]

Yeah . . . with Verisign.

[cococure]

> Yeah . . . with Verisign.

Hilarious... We are sticking with A.NET for now, but will be using Versign as a failsafe.

[hoekda]

Once I get the 2" pile of paper off my desk I'll look for an alternative vendor for cc service myself, not because of the problems they had, but because of how they handled themselves. Obfuscate and blame don't cut it for me.

[rumirunto]

We're back up, but their service is not reliable yet. We've had a few cases of orders lost because of their server not responding.

[joestern]

I actually wanted to show them my support by sticking with them, but if they can't get operators to stay past normal hours, and lay out all the info on the table for us, then I really can't applaud their efforts here.

And why didn't they have these protocols in place beforehand to deal with this?