Cross River Bank incident

Cross River - PushToPay degraded performance

Major Resolved View vendor source →

Cross River Bank experienced a major incident on July 18, 2024 affecting Card Payments Authorization Service and Card Payments Push Service and 1 more component, lasting 4h 28m. The incident has been resolved; the full update timeline is below.

Started
Jul 18, 2024, 11:19 PM UTC
Resolved
Jul 19, 2024, 03:48 AM UTC
Duration
4h 28m
Detected by Pingoru
Jul 18, 2024, 11:19 PM UTC

Affected components

Card Payments Authorization ServiceCard Payments Push ServiceCard Payments Pull Service

Update timeline

  1. investigating Jul 18, 2024, 11:19 PM UTC

    Our NOC team has identified a possible degradation of performance to the web API in push/pull to card transactions and card signup. This is currently under investigation. Customers may experience some performance and availability issues.

  2. investigating Jul 18, 2024, 11:19 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 19, 2024, 12:29 AM UTC

    We have identified the root of cause for the service degradation affecting our push/pull operations. The issue is related to our third-party vendor, and we are collaborating with them to resolve it as quickly as possible. Further updates will be provided as we continue to make progress.

  4. identified Jul 19, 2024, 02:43 AM UTC

    We have identified the root cause of the degradation affecting our push/pull operations. The issue is related to our third-party vendor and we are collaborating with them to resolve as quickly as possible. In the meantime, we are actively working on a workaround to mitigate the impact. Further updates will be provided as more information becomes available.

  5. identified Jul 19, 2024, 03:11 AM UTC

    We are continuing to work on the workaround for the service degradation affecting our push/pull operations. We will provide more information as soon as it becomes available.

  6. resolved Jul 19, 2024, 03:48 AM UTC

    After a thorough investigation, we have identified that our third-party vendor was the root cause of the issue. Operations and processes have resumed, and are now back to normal.