PocketSmith incident

Payments provider experiencing outage, affecting all payment related actions

Minor Resolved View vendor source →

PocketSmith experienced a minor incident on February 5, 2023 affecting Web, lasting 4h 7m. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2023, 01:25 AM UTC
Resolved
Feb 05, 2023, 05:32 AM UTC
Duration
4h 7m
Detected by Pingoru
Feb 05, 2023, 01:25 AM UTC

Affected components

Web

Update timeline

  1. investigating Feb 05, 2023, 01:25 AM UTC

    Our upstream payments provider Windcave are experiencing an extended outage today, affecting our credit card payment systems. This means that you may have trouble entering your payment details into PocketSmith, when upgrading or creating a new account. We're applying mitigation techniques at the moment, while Windcave continue to work on the problem. The incident is registered with Windcave at https://status.windcave.com, and you'll be able track progress there along with this message on our own status page. This outage also affects vast numbers of point-of-sale systems throughout Australia and New Zealand - our thoughts are with all those in hospitality and retail who are affected this long weekend.

  2. identified Feb 05, 2023, 02:12 AM UTC

    We've seen a downtick in the number of these errors which are occurring, but we're currently working on the mitigation measures that will be put into place - we'll update again here once these are released. Thanks for your patience!

  3. monitoring Feb 05, 2023, 02:38 AM UTC

    Our upstream payments provider has marked this incident as resolved, but we're still seeing the occassional error crop up. We're monitoring the situation on this side, and are holding back release of our mitigation until we have more clarity on the situation. Thanks for your patience.

  4. resolved Feb 05, 2023, 05:32 AM UTC

    No errors have occurred with credit card processing for well over an hour now, and everything appears to be back to normal now. Appreciate all your patience while this problem was rectified!