Countingup incident

Provider outage affecting inbound and outbound account transfers

Major Resolved View vendor source →

Countingup experienced a major incident on December 10, 2022 affecting 📥 Inbound account transfers and 📤 Outbound account transfers, lasting 5h 21m. The incident has been resolved; the full update timeline is below.

Started
Dec 10, 2022, 06:33 PM UTC
Resolved
Dec 10, 2022, 11:55 PM UTC
Duration
5h 21m
Detected by Pingoru
Dec 10, 2022, 06:33 PM UTC

Affected components

📥 Inbound account transfers📤 Outbound account transfers

Update timeline

  1. investigating Dec 10, 2022, 06:33 PM UTC

    One of our providers is experiencing technical difficulties, this is affecting the processing of account transfers through the faster payments scheme. Inbound transfers will not be received, and will be returned back to the account sending them. You will still be able to initiate outbound account transfers from the Countingup app, however these are currently being delayed and will not reach their destination until the issue is resolved. We are working with our provider to resolve this as soon as possible and apologise for any inconvenience caused.

  2. identified Dec 10, 2022, 07:35 PM UTC

    Our provider has identified the issue affecting the processing of account transfers through the faster payments scheme, and is continuing to work to resolve this as soon as possible. We apologise for any inconvenience caused.

  3. identified Dec 10, 2022, 09:08 PM UTC

    Our provider continues to work to resolve the issue affecting the processing of account transfers through the faster payments scheme as soon as possible. We apologise for any inconvenience caused.

  4. monitoring Dec 10, 2022, 10:46 PM UTC

    Our provider has resolved the issue affecting the processing of account transfers through the faster payments scheme. Inbound account transfers should now be successful. The backlog of delayed outbound account transfers is now being processed. We will continue to monitor the situation and apologise for any inconvenience caused.

  5. resolved Dec 10, 2022, 11:55 PM UTC

    This incident has been resolved.