I am experiencing a timeout issue on CIM as of 11 PM EST. Our last successful transaction and payment profile was created at 10:55 PM EST. Profile response, shipping address response, and payment profile response all looked normal and time for API call was 2 seconds max. However, on our next transaction at 11:41 PM EST, I am receiving time out errors as follows:
[2014-09-19 03:33:57][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received
[2014-09-19 03:34:42][----Response----]
[ Time Taken for the API CALL : 45seconds ]
[2014-09-19 03:34:42][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received
[2014-09-19 03:35:27][----Response----]
[ Time Taken for the API CALL : 45seconds ]
[2014-09-19 03:37:20][----Request----]
MASKED
[2014-09-19 03:37:58][----Response----]
<?xml version="1.0" encoding="utf-8"?><updateCustomerProfileResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ><messages><resultCode>Error</resultCode><message><code>E00014</code><text>Customer Profile ID is required.</text></message></messages></updateCustomerProfileResponse>
[ Time Taken for the API CALL : 38seconds ]
[1411097878]:Error Creating Customer profile 23454: Error: Error
Message: Customer Profile ID is required.
E00014
[2014-09-19 03:39:41][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received
[2014-09-19 03:40:26][----Response----]
[ Time Taken for the API CALL : 45seconds ]
[2014-09-19 03:40:26][----Request----]
MASKED
[2014-09-19 03:41:09][----Response----]
<?xml version="1.0" encoding="utf-8"?><ErrorResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ><messages><resultCode>Error</resultCode><message><code>E00003</code><text>The element 'profileTransAuthCapture' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'order' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'lineItems, customerProfileId' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.</text></message></messages></ErrorResponse>
[ Time Taken for the API CALL : 43seconds ]
The same errors occurred for 2 other users under different IP addresses, as well as several of my own tests. Our system has been working solidly for weeks now, and I have not uploaded any changes in over 2 weeks. Is anyone else experiencing this CIM timeout issue?
โ09-18-2014 09:49 PM
Just pinged authorize.net, and I see that my server is having an issue connecting with authorize.net
PING authorize.net (64.94.118.77) 56(84) bytes of data.
--- authorize.net ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10291ms
I am using a RackSpace cloud server. I have contacted RackSpace, and they are saying that I am getting a packet filtered response from authorize.net. Does anyone know what might be causing this?
โ09-18-2014 10:38 PM
We are hosted in 2 Rackspace datacenters and experienced the same issues with CIM around 8:10 PDT.
Operation timed out after 45001 milliseconds with 0 bytes received
โ09-18-2014 10:41 PM
I am experiencing the same issue -- please share your findings.
I can load up https://api.authorize.net/xml/v1/request.api but it takes VERY long time (more than the cURL timeout)
โ09-18-2014 10:42 PM
I just tried to ping authorize.net from my computer, and I got the same issue.
--- 64.94.118.77 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
โ09-18-2014 10:54 PM
โ09-18-2014 11:19 PM
We're experincing the same issue. There must be a number to call.. somehwere.
โ09-18-2014 11:32 PM
It is possible that issue has been resolved. I can cURL it. Although it takes 8 seconds to load!
โ09-18-2014 11:35 PM
The whole system is down. I can't even processes CIM payments manually through the authorize.net merchant interface...
CIM down for the past 4 hours, and will likely be down for about 5 hours until their offices open. Pretty sad...
โ09-19-2014 01:07 AM
I am noticing odd timeout issues on my end too... Tried to call support but they are closed. This is crazy!!
โ09-19-2014 01:21 AM