Authorize.net outages and problems
In the past 24 hours, 10 user reports came in for Authorize.net. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 1 report, about 22 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Authorize.net in October 2026
- Problem reports in October (since 28 October)
- 10
Monthly report for October 2026
People who report a problem with Authorize.net to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Website
- Funds Transfer
- Login
- Purchases
- Payments
- App
- QR Code
Authorize.net problem spikes, last 30 days
Since 28 October, Authorize.net had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix Authorize.net not working
Authorize.net is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach authorize.net over your own connection, right now. Nothing is sent to us or stored.
Check the Authorize.net report level
The banner at the top of this page shows whether problem reports for Authorize.net are above their usual level, counted in 15-minute windows over the last 24 hours. Start there. If the level is normal, retry the checkout in a private browser window and note the exact message on the payment form; that separates a single-buyer session issue from a wider report spike.
Correct the card and billing fields
Make sure the card number, expiration date, CVV, and billing address match what the card issuer has; a mismatch in any one of those fields can decline this buyer while other payments go through. Authorize.net passes the corrected details to the issuer on the next submit. Try again.
Open the transaction in the Merchant Interface
Sign in to the Merchant Interface, open Search > Transaction Search, and find the recent attempt by transaction ID or by the last four digits of the card. Read the response reason in the transaction details. If the reason points to the issuer, ask the buyer to call the number on the back of the card; if it points to an account setting, correct that setting before you retry.
Check the API Login ID and Transaction Key
In the Merchant Interface, go to Account > Settings > Security Settings > API Login ID and Transaction Key, then confirm the API Login ID matches the integration. Generate a new Transaction Key only if the old key is unknown or rejected. Then update the gateway settings in the app or plugin and run a test transaction in the sandbox account before you take live payments.
While Authorize.net is down: what to use instead
- PayPal Send a PayPal invoice if the customer can pay outside your card form.
- Stripe If your store already holds Stripe keys, switch the card form to Stripe until the gateway responds again; a custom checkout may need a developer.
- Square For counter sales, run the card through a Square reader while the terminal cannot reach the service.
- Braintree Use Braintree if you already have an account and need a second card path for checkout while the gateway is out.
What happens when Authorize.net goes down
Authorize.net is a payment gateway businesses use to accept card and online payments. When it fails, checkout forms hang and card charges stall; the payment data your store sends has nowhere to go, so customers retry and staff field complaints.
Checkout is where you feel it first: the payment form hangs and the confirmation page never loads. If the gateway cannot reach the processor, a charge may fail outright or sit as pending until your customer gives up. Refunds and recurring billing stall too. Treat the trouble as partial until you test a small charge yourself, because a single card type, a single integration, a single storefront, or a single region can fail while another checkout completes.
Authorize.net IP address, servers and network
Checking authorize.net from our server…
Authorize.net FAQ
Is Authorize.net down right now?
Why does Authorize.net reject my API request with 'The merchant login ID or password is invalid'?
Why does the virtual terminal decline a card that goes through on my website?
Why does the Authorize.net mobile app log me out or fail to show transactions?
Why does recurring billing stop after a card expires or a payment profile changes?
Service updates from @authorizenet
No posts about problems from @authorizenet in the last 14 days. The latest is from .
Put the Authorize.net status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/authorize-net/"><img src="https://isitdownrightnow.app/badge/authorize-net.svg" alt="Authorize.net status" height="20"></a>[](https://isitdownrightnow.app/services/authorize-net/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track Authorize.net
The status on this page comes from user-submitted problem reports for Authorize.net, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Authorize.net, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Authorize.net doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.