NatWest incident

NatWest Group - Incident Notification 06/02/2024. Ongoing issues with NatWest API Gateway

Major Resolved View vendor source →

NatWest experienced a major incident on February 6, 2024 affecting UBN Payment Consent and NWB Payment Consent and 1 more component, lasting 28d 22h. The incident has been resolved; the full update timeline is below.

Started
Feb 06, 2024, 03:31 PM UTC
Resolved
Mar 06, 2024, 02:01 PM UTC
Duration
28d 22h
Detected by Pingoru
Feb 06, 2024, 03:31 PM UTC

Affected components

UBN Payment ConsentNWB Payment ConsentRBS Payment ConsentNWB - Accounts API - EbankingRBS - Accounts API - EbankingUBN - Accounts API - EbankingRBSI - Accounts API - ClearSpendNWI - Accounts API - EbankingNWB Payment StatusRBS Payment Status

Update timeline

  1. investigating Feb 06, 2024, 03:31 PM UTC

    Please be aware of an ongoing incident that is affecting our APIs at the moment. Our API Gateway product is having intermittent issues that is occasionally causing around 5% of API calls to fail with a 5XX response. The impact typically lasts 10 to 20 minutes before self recovering. Our technical teams are investigating this issue and hope to have it rectified quickly. In the meantime we ask that API consumers please attempt to work around this issue by retrying requests. Please accept our apologies for any inconvenience this issue is causing. Please don’t hesitate to get in touch with us via our API Service Desk if you have any questions regarding this. We’ll be on hand to help.

  2. investigating Feb 06, 2024, 03:43 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 06, 2024, 03:45 PM UTC

    We are continuing to investigate this issue.

  4. resolved Mar 06, 2024, 02:01 PM UTC

    Resolved: Our API Gateway product was having intermittent issues, occasionally causing around 5% of API calls to fail with a 5XX response. The impact typically lasted 10 to 20 minutes before self recovering. Our API Gateway service provider has updated software versions and provisioned new hardware to resolve this issue. Last occurrence of the issue was February 10th 2024. After an extended period of monitoring and a full root cause and future prevention statement from our API Gateway vendor we are now confident that this issue is fully resolved. Please accept our apologies for any inconvenience this issue caused. Please don’t hesitate to get in touch with us via our API Service Desk if you have any questions regarding this. We’ll be on hand to help.