All Systems Operational

About This Site

Current System Status:-

Advanced Fraud Detection Suite (AFDS) Operational
API End Points Operational
Automated Recurring Billing (ARB) Operational
Customer Information Manager (CIM) Operational
Settlement/Batching Operational
Credit Cards Operational
eCheck.Net/ACH Operational
Transaction Processing Operational
Credit Cards Operational
eCheck.Net/ACH Operational
Merchant Interface (MINT) Operational
Access/Login Operational
Reports/Transaction Search Operational
Batch/File Upload Operational
Partner Interface (PINT) Operational
Access/Login Operational
Reporting Operational
Virtual Point of Sale (VPOS) Operational
Access/Login Operational
Sandbox Environment ? Operational
Corporate Web Sites Operational
Developer Center - https://developer.authorize.net/ Operational
Corporate Site - https://www.authorize.net/ Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Update - After reviewing feedback concerning the production cutoff date for the MD5 Hash, we are pushing back the production update from March 14, 2019, to June 28, 2019. We will continue to review feedback and consider further date changes as needed over the next month.

For more details, see MD5 Hash End of Life & Signature Key Replacement article - https://support.authorize.net/s/article/MD5-Hash-End-of-Life-Signature-Key-Replacement
Mar 12, 09:29 PDT
Update - The final cut off for MD5 Hash has been changed to March 28th, 2019.

For more details, see our support article, MD5 Hash End of Life & Signature Key Replacement:
https://support.authorize.net/s/article/MD5-Hash-End-of-Life-Signature-Key-Replacement
Mar 1, 08:16 PST
Scheduled - Authorize.Net is phasing out the MD5 based hash use for transaction response verification in favor of the SHA-512 based hash utilizing a Signature Key.

The end of life for MD5 Hash will be done in two phases:

Phase 1 - As of February 11, 2019 we have removed ability to configure or update MD5 Hash setting in the Merchant Interface. Merchants who had this setting configured have already been emailed/contacted.

Phase 2 - Stop sending the MD5 Hash data element in the API response. To continue verifying via hash, this will require applications to support the SHA-512 hash via signature key.

--Sandbox will be updated on March 7, 2019 to stop populating the MD5 Hash value, but the field will still be present but empty.

--Production will be updated on March 14, 2019 to stop populating the MD5 Hash value, but the field will still be present but empty.

For more details, see MD5 Hash End of Life & Signature Key Replacement article - https://support.authorize.net/s/article/MD5-Hash-End-of-Life-Signature-Key-Replacement
Feb 20, 11:17 PST
Past Incidents
Mar 18, 2019

No incidents reported today.

Mar 17, 2019

No incidents reported.

Mar 16, 2019

No incidents reported.

Mar 15, 2019

No incidents reported.

Mar 14, 2019

No incidents reported.

Mar 13, 2019

No incidents reported.

Mar 12, 2019

No incidents reported.

Mar 11, 2019
Completed - We have verified this change has been completed. We are however delaying the removal of the old ip addresses due to still seeing traffic on them and we will be reaching out to Merchants we identify still using these old IP addresses before we remove them in a future update.

For more details, see our support article, Authorize.Net Domains and IP Addresses:
https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses
Mar 11, 12:11 PDT
Verifying - DNS portion of the change has been completed and domains are now resolving to our new IP addresses. We are monitoring for any traffic still coming directly to our old IP Addresses before continuing with any removal.
Mar 11, 10:55 PDT
Update - DNS portion of the change has been completed and domains are now resolving to our new IP addresses. We are monitoring for any traffic still coming directly to our old IP Addresses before continuing with any removal.
Mar 11, 10:54 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 11, 10:08 PDT
Update - The final cut over has been changed to March 11th, 2019 starting at 9:00am PT, Authorize.Net will be disabling the old IP addresses for our API endpoints and only the new IP addresses will function.

For more details, see our support article, Authorize.Net Domains and IP Addresses:
https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses
Feb 28, 07:27 PST
Update - The final cut over has been changed to March 6th, 2019 starting at 9:00am PT, Authorize.Net will be disabling the old IP addresses for our API endpoints and only the new IP addresses will function.

For more details, see our support article, Authorize.Net Domains and IP Addresses:
https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses
Jan 28, 15:52 PST
Scheduled - We are upgrading the way we manage our network infrastructure to be more responsive to events and business need. In order to support these changes, we are changing the IP addresses used by our API endpoints. The URLs and domains for all Authorize.Net websites and services will remain the same.

On February 13th, 2019 starting at 9:00am PT, Authorize.Net will be disabling the old IP addresses for our API endpoints and only the new IP addresses will function.

For more details, see our support article, Authorize.Net Domains and IP Addresses:
https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses
Dec 7, 14:53 PST
Mar 10, 2019

No incidents reported.

Mar 9, 2019

No incidents reported.

Mar 8, 2019

No incidents reported.

Mar 7, 2019

No incidents reported.

Mar 6, 2019

No incidents reported.

Mar 5, 2019

No incidents reported.

Mar 4, 2019

No incidents reported.