Is Azupay down right now?
No — Azupay is up. All systems operational as of Oct 12, 7:45 AM UTC.
Current Status
All Systems Operational
Components
Recent Incidents
Upstream Payment processing issues Impacting Outbound Bendigo Bank transactions - [incident first identified 7 October 2026 20:45 in AEST/AEDT timezone])
noneOct 7, 2026 · resolved Oct 7
The outage impacting Bendigo Bank resolved around approximatley 2026-10-07 21:50:00 Australia/Sydney last night, and on monitoring, no further issues have been experienced. We are resolving this issue. We recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted. Information on error codes are available from our developer docs at https://developer.azupay.com.au/docs/making-payments#failure-reason-codes
Payment processing issues Impacting Westpac transactions - [incident first identified 7 October 2026 11:17 AEST in AEST/AEDT timezone])
noneOct 7, 2026 · resolved Oct 7
Westpac have confirmed this issue is resolved and have published the following guidance on impact windows: Incident Start Date/time: 07 October 2026 @ 11:16 AEDT Incident End Date/time: 07 October 2026 @ 11:33 AEDT NPP Payment Self suspension Start Date/Time: 07 October 2026 @ 11:25 AEDT NPP Payment Self-suspension end Date/Time: 07 October 2026 @ 11:33 AEDT We are now resolving this issue. Information regarding the PA04 and AB01 error codes is avaialble from our developer documentation at https://developer.azupay.com.au/docs/making-payments#failure-reason-codes *Reason* Code Description *AB01* Clearing process aborted due to timeout. NPP Error. Client should retry for up to 8 hours before failing the payment and crediting the customers account. *PA04* Participant Not Available. Receiving bank is experiences problems. Client should retry for up to 8 hours before failing the payment and crediting the customers account.
UPDATE: Payment processing issues to/from CBA accounts (incident number [AZ-19577] - [incident first 20th September 2026 @ 02:42 AEST])
minorSep 20, 2026 · resolved Sep 20
We believe the issue is now resolved. The root cause of the issue was due to intermittent transaction processing errors encountered at CBA. If you are still encountering issues, please do reach out using our service desk: https://azupay.atlassian.net/servicedesk/customer/portal/3 including any pertinent information such as PayID's, bsb/account numbers, date/time stamps and amounts. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.
Upstream incident impacting CBA NPP transactions
minorSep 19, 2026 · resolved Sep 20
CBA have resolved the issue at 20th September 2026 @ 08:30 AEST. Any outbound payments affected by this degradation will have encountered a FAILED status with an AB01 or PA01 reason code. You will have to retry these payments. Any delayed inbound payments have now been processed. If you require any further assistance, please raise a support ticket through the usual channels.
Atlassian outage impacting service desk availability | Guidance on alternate contact channel for urgent support
minorAug 27, 2026 · resolved Aug 27
We are now resolving this incident, as Atlassian have confirmed full incident recovery.
Get alerted when Azupay goes down
Alert24 monitors Azupay and 3,700+ other cloud and SaaS providers. When an outage is detected, it updates your status page automatically and pages your on-call team. No manual updates at 2 AM.
Azupay status — frequently asked questions
Is Azupay down right now?
No — Azupay is up. All systems operational as of Oct 12, 7:45 AM UTC.
What is Azupay's current status?
Azupay: All Systems Operational. Alert24 checks Azupay's status page continuously and can notify you the moment it changes.
How do I get alerted when Azupay goes down?
Alert24 monitors Azupay and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.