azupay incident

Errors from API

Minor Resolved View vendor source →

azupay experienced a minor incident on June 10, 2022 affecting Inbound to azupay payment processing, lasting 8h 23m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2022, 12:52 AM UTC
Resolved
Jun 10, 2022, 09:15 AM UTC
Duration
8h 23m
Detected by Pingoru
Jun 10, 2022, 12:52 AM UTC

Affected components

Inbound to azupay payment processing

Update timeline

  1. investigating Jun 10, 2022, 12:28 AM UTC

    We have identified that some api's are intermittently failing altogether or timing out. We are currently investigating.

  2. investigating Jun 10, 2022, 12:29 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 10, 2022, 12:30 AM UTC

    We are continuing to investigate this issue.

  4. identified Jun 10, 2022, 12:52 AM UTC

    You may encounter timeouts or significantly longer than usual response time trying to: - Register PayID via the POST /v1/paymentRequest - Enquiring about BSB via the POST /v1/accountEnquiry - Enquiring about PayID's via the POST /v1/payIDEnquiry - Making payments out via the POST /v1/payment We are continuing to receive payments where the PayID is already registered.

  5. identified Jun 10, 2022, 02:09 AM UTC

    Our supplier has acknowledged the issue and is working to resolve it. The impact remains the same as communicated previously.

  6. identified Jun 10, 2022, 03:21 AM UTC

    Our supplier has acknowledged the issue and is working to resolve it. The impact remains the same as communicated previously.

  7. monitoring Jun 10, 2022, 05:45 AM UTC

    System response time has improved but remains on the high side. We are continuing to monitor the situation and will post updates here again shortly.

  8. monitoring Jun 10, 2022, 08:21 AM UTC

    We are now seeing consistent response times within SLAs from our NPP provider and will continue to monitor until they have confirmed the issue is closed.

  9. resolved Jun 10, 2022, 09:15 AM UTC

    Our NPP provider has confirmed the issue has been resolved. We'll continue to closely monitor the system for the next few hours.