azupay incident
Intermittent errors creating PayID's using the POST /v1/paymentRequest api
azupay experienced a minor incident on April 21, 2022 affecting api, lasting 19h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 21, 2022, 11:33 AM UTC
Some customers are encountering intermittent errors registering PayID's using the POST /v1/paymentRequest api. Out of all the requests submitted across our customers over the past 2 days, 8% of these have encountered this error. There was a concentration of these errors around on the 20/04/2022 from 22:30pm to approximately 23:00 and again on the 21/04/2022 from 12:30pm to 2:30pm. This issue only affects the registration of PayID's occasionally. It does not affect the receipt of payments where the PayID is already registered. There is also no impact on any other functions of the Azupay platform. We have raised this with our supplier and will continue to provide updates.
- investigating Apr 21, 2022, 12:19 PM UTC
We are continuing to await the results of investigations on our supplier side. In the meantime, we can confirm that this error has not been encountered in the past hour.
- investigating Apr 21, 2022, 06:31 PM UTC
We are continuing to await the results of investigations on our supplier side. Monitoring shows no further degradation of the system.
- monitoring Apr 22, 2022, 01:26 AM UTC
We have not seen a repeat of the error since 10:30pm last night. We will continue to work with our supplier to identify the root cause of the issue.
- monitoring Apr 22, 2022, 06:49 AM UTC
We are continuing to monitor for any further issues.
- resolved Apr 22, 2022, 06:50 AM UTC
In the past few hours there have been no failures to register PayID's. We are continuing to monitor the system for repeat errors.