Azupay logo

Is Azupay Down?

FinTech & PaymentsLive status, outages, and incident history

No. Azupay is up right now.

Every monitored Azupay system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment Azupay breaks

Azupay is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Azupay status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Azupay Status Summary

As of 18:08 UTC on 14 November 2026, Azupay is operational. PulsAPI checked Azupay's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Upstream incident impacting Westpac and Bank of Melbourne NPP transactions", was on Nov 10, 2026 and lasted 6h 44m.

Cite as: PulsAPI, “Azupay status”, checked 14 November 2026, 18:08 UTC. https://www.pulsapi.com/services/azupay

Azupay Component Status

The main Azupay systems on this page. All 6 are operational right now.

6operational
api
Operational
dashboard
Operational
External NPP Network
Operational

3 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Inbound to azupay payment processing, Outbound from azupay payment processing, Service desk portal.

See all of them free

Component statuses may change independently during partial outages.

Recent Azupay Outages & Incidents

Incident history from the official Azupay status page, including resolution updates.

Upstream incident impacting Westpac and Bank of Melbourne NPP transactionsResolved Nov 10, 2026 · 6h 44mResolved

Westpac have confirmed this issue is resolved as of 23:09 aest. Failed payments can be reattempted. --- [2026-11-10T18:43:05.379+11:00] (monitoring) We are continuing to monitor the outage and will provide updates as they are available. --- [2026-11-10T18:42:09.852+11:00] (investigating) Westpac have notified NPP participants they are currently having an outage impacting NPP payments and have self suspended from the NPP network. Attempts to make payments to Westpac clients will result in errors, and attempted payments made prior to the self suspension during the incident window return a Pending status until Westpac has confirmed settlement of funds. Incident Start Date/time: 10 NOV 2026 @ 15:48 AEDT NPP Payment Self suspension Start Date/Time: 10 NOV 2026 @ 17:35 AEDT NPP Payment Self-suspension end Date/Time: TBC The issue remains ongoing, and outbound payments to Westpac and Bank of Melbourne BSB ranges will return errors until Westpac removes their self suspension. Inbound payments from NPP payers based on Westpac accounts may also be delayed. We recommended retrying outbound payments to Westpac participants once the upstream issue is resolved, and will provide updates as they are provided to us.

Upstream Payment processing issues Impacting Outbound Bendigo Bank transactions - [incident first identified 7 October 2026 20:45 in AEST/AEDT timezone])Resolved Oct 7, 2026 · 12h 30mResolved

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 --- [2026-10-07T21:17:07.979+11:00] (monitoring) We have identified a spike in failures of outbound payments impacting Bendigo Bank for their BSB range 633 stating at 20:45 and ongoing. The issue is isolated to this Bendigo Bank BSB range. These transactions are being rejected with PA04. We recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted after this issue notice is resolved. We will provide updates as they become available to Azupay.

Payment processing issues Impacting Westpac transactions - [incident first identified 7 October 2026 11:17 AEST in AEST/AEDT timezone])Resolved Oct 7, 2026 · 3h 30mResolved

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. --- [2026-10-07T11:56:03.763+11:00] (monitoring) We have identified a spike in failures of outbound payments impacting a subset of transactions for several NPP participants stating at 11:17 and resolving at 11:47 AEST. The issue appears to be concentrated to Westpac based accounts. These transactions are being rejected with PA04 or AB01 errors. While the issue appears to have resolved, we recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted.

Azupay Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Azupay incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Azupay Outage Reports

Problems reported by engineers using Azupay. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Azupay problems reported yet.

Something wrong with Azupay on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Azupay

Azupay's status page at status.azupay.com.au lists 6 components, such as External NPP Network, Inbound to azupay payment processing and Outbound from azupay payment processing. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Azupay's side or yours.

Azupay Status FAQ

Is Azupay down right now?

The verdict at the top of this page comes from the latest poll of the official Azupay status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Azupay is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Azupay recovers.

How do I check Azupay uptime history?

PulsAPI tracks Azupay uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Azupay changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Azupay outages?

PulsAPI reads the official Azupay status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Azupay components?

Yes. PulsAPI monitors 6 individual Azupay components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Azupay goes down?

Yes. Create a free account and subscribe to Azupay: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Azupay to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Azupay problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Azupay?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Azupay plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Azupay with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services