Azupay Incident History

1. resolvedAug 27 · 06:26 UTC

   Monitoring indicates services are stable and have not had any reoccurance of issues. We are now resolving this incident.

   Post the issue, we have redriven a small percentage of transactions that were been impacted by this outage and that failed to successfully process.

   • A small amount of outbound payments may have been delayed in settlement and have been redriven and should now be settled. These will have shown a PENDING Status, and should now progress to a terminal status of SETTLED.
   • A small amount of PayID registrations for Payment Requests may have been delayed, which may have impacted the ability of customers to make payments to associated PayIDs tied to the Payment Request. These will have shown a WAITING status but may have been unresolvable in customer's banking interfaces. These should now be available to receive payments.

   Post incident monitoring indicates the degradation in services was from 3:04 PM AEST to 3:27 PM AEST.

   We are requesting additional information regarding the cause of the outage.

Reported by Azupay on their status page.

1. resolvedAug 27 · 06:26 UTC

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

Reported by Azupay on their status page.

1. postmortemSep 3 · 07:48 UTC

   Our banking partner has provided us information regarding the root cause of this issue.

   Incident Cause
   On 24th August 2026, between 12:55 pm and 4:52 pm, a power outage and associated network disruption impacted an upstream service provider utilised by our banking partner for hosting. This activity was related to an underlying infrastructure change activity that caused an unexpected fault and cascading power failure, impacting part of a redundant architecture configuration and leading to performance issues with a portion of traffic.

   The faulty hardware impacted by the issue has been replaced, and follow up actions are planned to confirm the overall resiliency of the power configuration at the impacted data centre. It is not expected to re-occur.

   Impact

   This impacted communication between application and database components across several production platforms, and impacted a portion of Azupay traffic to and from the NPP network for approximately 1/3rd of traffic during the incident window for Payment activities and PayID maintenance.

   Resolution

   Our banking partner was able to successfully recover services via a graceful failover to their secondary site, and as Azupay has redundancy patterns implemented in our system, we were able to redrive impacted transactions during the incident window.

Reported by Azupay on their status page.