Azupay Status Page

Aug 27, 2026 · resolved Aug 27

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

Aug 27, 2026 · resolved Aug 27

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.

Aug 24, 2026 · resolved Aug 25

This incident has been resolved. No further issues have been observed. Summary: PayTo agreements, PayID Alias Registration and Deregistrations and Outbound Payments experienced heightened errors between 24th August 01:00 PM AEST to 05:05 PM AEST. The initial investigation identified intermittent latency and elevated error rates within our banking partner’s connectivity to the NPP network. This primarily affected PayID registration/deregistration, outbound payments, and a small volume of PaymentAgreement and PaymentInitiation events. The banking partner acknowledged the issue and worked on remediation, with Azupay redriving impacted transactions while monitoring the service until request processing returned to normal. The system health of our banking partner has recovered as of 5:05pm AEST, and 100% of requests are now being processed successfully. Azupay has confirmed that impacted transactions are being processed successfully, including PayID registration and deregistration, outbound payments, PaymentAgreement, and PaymentInitiation events. A small number of outbound payments remained in a PENDING state following the NPP service disruption. These transactions were reviewed against their corresponding NPP status were manually patched to reflect the correct final status. We apologise for any inconvenience caused and thank you for your patience and understanding.

Apr 29, 2026 · resolved Apr 29

This incident has been resolved. No further issues have been observed. Summary: PayID Alias Registration and Deregistrations exeperienced hightened errors between 29 April - 17:30 AEST to 18:09 and 18:15 to 18:29. Due to the error rate only affecting a portion of traffic and Azupay redriving paymentRequest registrations, clients may not have experienced significant impact during the incident perioid. While we initially identified a small count of hightened identified errors on outbound payment processing due to increased latency on an upstream API, these transactions were retried and did not have introduced delay in payment processing. Root Cause of Issue We have requested a root cause analysis from our Payment Accesss Gateway provider banking partner for additional information on the cause of the issue. Initial investigation and resolution indicates a degradation in a portion of their compute resources in their load balanced API responsible for PayID registrations, and cycling the unhealthy nodes resolved the issue. We will work with our banking partner to identify opportunities to improve the resiliency of these services.

Apr 15, 2026 · resolved Apr 15

**Client Post Incident Advice** The incident we experienced last night impacted the PayID registration process for our paymentRequest product between 7pm and 9pm AEST, and some PayID registrations during this incident were delayed. If you use our paymentRequest product and have a client who pays you via a payID, they may have been unable to complete a payment successfully against the PayID during this period. Azupay successfully registered all PayIDs by 10PM AEST after the incident window, with the majority of impacted paymentRequests being registered by 9:20PM AEST. You may need to contact customers who attempted payments during this period and request they re-attempt the payment if the paymentRequest is still in a WAITING status and you are expecting they should have paid by now. As the PayIDs were not registered, the customer would have not been able to successfully look up the PayID in their banking portal, and no payment would have been attempted. You should contact impacted clients, let them know the PayID is now available for payment, and they should re-attempt it. If end customers have any issues making payment to the registered PayID, please raise a request with our service desk at [https://azupay.atlassian.net/servicedesk/customer/portal/3](https://azupay.atlassian.net/servicedesk/customer/portal/3) for support. Additional information on the root cause is still pending. ----- We are awaiting a Post Incident Review from our upstream impacted connected institute, which should be supplied on the 1st of May. We will provide further details once this has been shared. --- 23/04/2026: Incident Summary Provided by Banking Partner Our banking partner has provided an initial incident summary for this incident. A more detailed Post Incident Review is still pending. The issue was caused by an unexpected problem during scheduled maintenance at one of our partner’s data centres during maintenance by one of their vendors. While the activity was intended to be isolated and low risk, it inadvertently disrupted connectivity between PayID services and their respective databases. The vendor subsequently confirmed that the disruption was due to a network protocol blocking communication between these services. To resume services, our Parter failed over all traffic to an alternate data centre link,, allowing service restoration. We are working with our banking partner to improve incident response processes with their teams to minimise impact --- 06/05/2026 We have been provided a PIR by our partner and can provide additional information relating to the cause of this incident. The ultimate cause of the incident was a networking misconfiguration that resulted in a service interruption. Steps have been taken to ensure this configuration iscorrectly set going forward to prevent a recurrence Details: During a planned maintenance window at our payment infrastructure provider's data centres, an unexpected network configuration issue disrupted PayID service connectivity. Although the maintenance was intended to be isolated and low risk, a misconfiguration caused part of the internal administration network to incorrectly classify an internal connection as external. As a protective measure, the system automatically disabled several network paths, resulting in a service interruption.  To restore services, affected systems were redirected to an alternative data centre. PayID services were restored earlier in the evening, with full restoration of all payment services later that night. Once the underlying configuration was corrected and the connection was recognised appropriately, normal network communication resumed and all services stabilised. Steps have been taken to ensure the configuration is correctly set going forward to prevent a recurrence. No further issues have been observed since restoration.

Is Azupay down right now?

No — Azupay is up. All systems operational as of Aug 28, 3:59 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.