azupay Outage History

azupay is up right now

azupay had 9 outages in the last 2 years totaling 77h 51m of downtime — averaging 0.4 incidents per month.

There were 9 azupay outages since October 15, 2025 totaling 77h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.azupay.com.au

Minor September 20, 2026

UPDATE: Payment processing issues to/from CBA accounts (incident number [AZ-19577] - [incident first 20th September 2026 @ 02:42 AEST])

Detected by Pingoru
Sep 20, 2026, 02:49 AM UTC
Resolved
Sep 20, 2026, 10:27 AM UTC
Duration
7h 38m
Affected: External NPP Network
Timeline · 4 updates
  1. identified Sep 20, 2026, 02:49 AM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Delays in processing: * Outbound payments via api to CBA accounts * Processing of inbound payments to PayID's from payer's CBA bank account Our recommendations are as follows: * Please inform your customers of delays where applicable. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

  2. monitoring Sep 20, 2026, 04:37 AM UTC

    We believe the issue is now resolved and will continue closely monitoring the performance of the system. 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.

  3. monitoring Sep 20, 2026, 10:26 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Sep 20, 2026, 10:27 AM UTC

    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.

Read the full incident report →

Minor September 19, 2026

Upstream incident impacting CBA NPP transactions

Detected by Pingoru
Sep 19, 2026, 04:45 PM UTC
Resolved
Sep 20, 2026, 12:45 AM UTC
Duration
8h
Affected: External NPP Network
Timeline · 3 updates
  1. identified Sep 19, 2026, 07:08 PM UTC

    Azupay has identified that CBA is currently experiencing an incident impacting Outbound and Inbound NPP Payments. These issues are affecting around 10% of payments. Some Outbound payments will enter a FAILED status with failure reason of AB01 or PA01. Inbound payments may be delayed.

  2. identified Sep 19, 2026, 11:34 PM UTC

    CBA is continuing to investigate the issue affecting Inbound and Outbound NPP Payments.

  3. resolved Sep 20, 2026, 12:45 AM UTC

    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.

Read the full incident report →

Minor August 27, 2026

Atlassian outage impacting service desk availability | Guidance on alternate contact channel for urgent support

Detected by Pingoru
Aug 27, 2026, 04:27 AM UTC
Resolved
Aug 27, 2026, 06:26 AM UTC
Duration
1h 59m
Affected: Service desk portal
Timeline · 3 updates
  1. investigating Aug 27, 2026, 04:27 AM UTC

    Azupay's service desk is currently being impacted by at Atlassian outage for JIRA and Confluence products, impacting Azupay's ability to view service desk requests. We have raised a support request with Atlassian to investigate the issue, and monitoring indicates it may be a wide spread issue for Atlassian customers as noted at https://status.atlassian.com/ If you require any urgent support, please instead email [email protected] while this incident is occurring as an alternate support channel.

  2. monitoring Aug 27, 2026, 04:48 AM UTC

    Atlassian have identified a potential fix and are rolling it out to impacted regions. We have now regained access to service desk functionality. We will continue to monitor until formal incident resolution is provided by Atlassian.

  3. resolved Aug 27, 2026, 06:26 AM UTC

    We are now resolving this incident, as Atlassian have confirmed full incident recovery.

Read the full incident report →

Minor January 23, 2026

Upstream incident impacting ANZ NPP transactions

Detected by Pingoru
Jan 23, 2026, 12:19 AM UTC
Resolved
Jan 23, 2026, 02:29 AM UTC
Duration
2h 10m
Affected: External NPP Network
Timeline · 5 updates
  1. investigating Jan 23, 2026, 12:19 AM UTC

    Azupay has identified that ANZ (ANZBAU3LXXX) is currently experiencing an incident impacting Outbound NPP Payments, and are investigating if inbound transactions are also impacted. Clients making outbound payments that are impacted will have recieved PA04 and AB01 error codes, and the payment will be in a FAILED status. Clients should review if they should re-attempt these transactions. Incident Start Date/time: 23 Jan 2026 - 9:40 AM AEDT Incident End Date/time: TBD A further update will be provided when more information is available.

  2. monitoring Jan 23, 2026, 12:33 AM UTC

    Our banking partner has confirmed that the ANZ bank outage has been resolved now. Azupay is currently monitoring the situation.

  3. monitoring Jan 23, 2026, 12:34 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 23, 2026, 01:18 AM UTC

    The incident has been confirmed as resolved by ANZ. We will monitor and resolve if no further updates are provided in the next few hours.

  5. resolved Jan 23, 2026, 02:29 AM UTC

    Incident has been resolved. Incident Start Date/time: 23 Jan 2026 - 9:40 AM AEDT Incident End Date/time: 23 Jan 2026 - 11:05 AM AEDT

Read the full incident report →

Minor October 15, 2025

Incident NPP Platform experiencing PayID registration issue. 15th October 2025 - 4:47 PM AEDT

Detected by Pingoru
Oct 15, 2025, 05:56 AM UTC
Resolved
Oct 15, 2025, 09:14 AM UTC
Duration
3h 18m
Affected: External NPP Network
Timeline · 4 updates
  1. investigating Oct 15, 2025, 05:56 AM UTC

    We are aware of issues in Registering and Updating PayIDs. The Inbound and Outbound payments are not affected. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. Please do subscribe to our status page for the latest and most accurate information. We apologies for the inconvenience caused.

  2. investigating Oct 15, 2025, 06:32 AM UTC

    We are currently aware of intermittent issues affecting the creation and updating of PayIDs due to a downstream provider outage. Clients creating new PayIDs for inbound payments may experience delays in PayID registration. Customers attempting to make payments to these new PayIDs via their online banking may also encounter lookup failures. This is an industry-wide outage impacting all participants. Outbound payments using BSB and account numbers remain unaffected. However, outbound payments to PayIDs may experience intermittent failures during this period. We apologise for the inconvenience caused.

  3. monitoring Oct 15, 2025, 07:06 AM UTC

    We believe the issue has now been resolved, and PayIDs are once again being registered within expected response times. The backlog of queued PayID creations has been cleared, and our systems are operating normally. We will continue to closely monitor system performance during the evening. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

  4. resolved Oct 15, 2025, 09:14 AM UTC

    This incident has been confirmed resolved. We have been monitoring our systems and no ongoing issues have been observed.

Read the full incident report →