cancel
Showing results for 
Search instead for 
Did you mean: 

CIM is still down

status.authorize.net says "monitoring" a resolution

 

Pingdom (our third-party monitoring service) and our own system show that CIM is still down ... http://stats.pingdom.com/awg3t4nsnd7a/1283656/2015/05

 

Please advise

npiasecki
Regular Contributor
1 ACCEPTED SOLUTION

Accepted Solutions

As a matter of record for the community, our first failure was at 3:54 p.m. Eastern and the last failure was at 4:07 a.m., putting the total outage at just over 12 hours. It appears that the service came back up for some parts of the world earlier in the evening, but our monitoring and systems in Chicago, Phoenix, Toronto, Portland, and Las Vegas were down for nearly this full duration (this is also why our monitoring kept showing up/down/up/down/up/down behavior), though there were a few successul calls from Chicago for a brief period around 12:30 a.m.

View solution in original post

npiasecki
Regular Contributor
9 REPLIES 9

Hello @npiasecki

 

I just checked your monitoring site and it also shows that we are up, but was unavailable for you earlier. We don't have any additional information at this time. If this changes, we'll post here in the community.

 

If you continue to see issues, please contact customer service and provide as much detail as you can about the errors you are experiencing.  They are available 24x7x365 to assist you.

 

Richard

RichardH
Administrator Administrator
Administrator

Hi @RichardH,

 

If you look more closely at http://stats.pingdom.com/awg3t4nsnd7a/1283656/2015/05 you'll see it keeps reporting up/down/up/down/up/down because your response times are all over the place, and most production calls are still timing out. You really do have a problem. It is simulating an API call, not just pinging your server. I'm sure all your pings are good, but the API itself is still not functioning correctly.

 

I'll go ahead and contact Customer Support; based on past experiences, then, I don't expect CIM to come back up until someone tomorrow morning realizes that you never actually fixed the problem. Blame the customer, that's the Authorize.Net way!

npiasecki
Regular Contributor

CIM definitely not working for us.

The status of things is a bit confusing at this time. Earlier the problem was announced as fixed, now it is not ?

 

 

Customer support completely useless. Keeps repeating 'the problem is resolved'.

But CIM still not working.

Tried the live chat... not working either.

Help!

 

CIM is still down for us too. Please fix!

kisong
Member
kisong
Member

It looks like CIM is back up for us as of 1:51AM Pacific, May 27.

kisong
Member

As a matter of record for the community, our first failure was at 3:54 p.m. Eastern and the last failure was at 4:07 a.m., putting the total outage at just over 12 hours. It appears that the service came back up for some parts of the world earlier in the evening, but our monitoring and systems in Chicago, Phoenix, Toronto, Portland, and Las Vegas were down for nearly this full duration (this is also why our monitoring kept showing up/down/up/down/up/down behavior), though there were a few successul calls from Chicago for a brief period around 12:30 a.m.

npiasecki
Regular Contributor

This has been quite disruptive, but whoever worked through the night to get this fixed, should be thanked.

 

Authorize.net please post and incident report: what went wrong, and what steps will be taken to reduce the probability of this happening again.