NatWest incident
NatWest Group - Incident Notification 21/Jun/2026
NatWest experienced a major incident on June 21, 2026 affecting Natwest - Secure1t Token API and Royal Bank of Scotland - Secure1t Token API and 1 more component, lasting 7h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 21, 2026, 04:13 AM UTC
We’re currently experiencing an issue affecting for token endpoints for the following brands: NatWest, Royal Bank of Scotland, Ulster Bank (Northern IrelandI), NatWest International, and RBS International. Our technical teams are actively investigating and working to resolve this as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience while we restore normal service. If you have any concerns or need support, get in touch with us via our API Service Desk. We’ll be on hand to help.
- identified Jun 21, 2026, 07:18 AM UTC
The issue has been identified and a fix is being implemented.
- identified Jun 21, 2026, 08:44 AM UTC
We are continuing to work on resolving this issue and will provide further updates as progress is made. In the meantime, if you encounter any failures, please retry the request as the issue is intermittent and retries may succeed.
- resolved Jun 21, 2026, 12:05 PM UTC
Please note that the incident we previously notified you about—which affected token endpoints for NatWest, Royal Bank of Scotland, Ulster Bank (Northern Ireland), NatWest International and RBS International—has now been resolved. The issue impacted between 03:24 BST and 12:43 BST today We 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.