TrueLayer Outage History

TrueLayer is up right now

There were 18 TrueLayer outages since February 6, 2026 totaling 1h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.truelayer.com

Minor May 3, 2026

PLN Payments Degraded Performance

Detected by Pingoru
May 03, 2026, 02:10 AM UTC
Resolved
May 03, 2026, 02:10 AM UTC
Duration
Affected: Signup+SandboxFrom 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXFrom 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇬🇧 TRYEGB22XXXFrom 🇬🇧 TRYEGB22To 🇬🇧 TRYEGB22ConsoleFrom 🇪🇺🇩🇰 SXPYDKKKXXXTo 🇪🇺🇩🇰 SXPYDKKKXXXVerificationTo 🇪🇺🇩🇪 SXPYDEHHXXXFrom 🇪🇺🇩🇪 SXPYDEHHXXXTo 🇬🇧 TRYEGB22XXXRecurring PaymentsTo external accountsTo 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 1 update
  1. resolved May 03, 2026, 02:10 AM UTC

    Status: Resolved We experienced an issue with PLN payouts where payment settlement was delayed due to an issue with our PLN banking partner. The issue has been resolved, and payouts are settling as normal. Impact start time: 03/05/2026, 03:48 UTC Impact end time: 03/05/2026, 04:10 UTC Client actions: None Affected components To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇬🇧 TRYEGB22XXX (Operational) To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇬🇧 TRYEGB22 (Operational) Sandbox (Operational) To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational) Verification (Operational) Signup+ (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) To 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) Console (Operational) From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇬🇧 TRYEGB22 (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇬🇧 TRYEGB22XXX (Operational) Data (UK & Europe) (Operational) Recurring Payments (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) To external accounts (Operational)

Read the full incident report →

Minor April 29, 2026

EUR Payouts Degraded Performance

Detected by Pingoru
Apr 29, 2026, 10:35 AM UTC
Resolved
Apr 29, 2026, 10:35 AM UTC
Duration
Affected: Signup+SandboxFrom 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXFrom 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇬🇧 TRYEGB22XXXFrom 🇬🇧 TRYEGB22To 🇬🇧 TRYEGB22ConsoleFrom 🇪🇺🇩🇰 SXPYDKKKXXXTo 🇪🇺🇩🇰 SXPYDKKKXXXVerificationTo 🇪🇺🇩🇪 SXPYDEHHXXXFrom 🇪🇺🇩🇪 SXPYDEHHXXXTo 🇬🇧 TRYEGB22XXXRecurring PaymentsTo external accountsTo 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 1 update
  1. resolved Apr 29, 2026, 10:35 AM UTC

    Status: Resolved We experienced an issue with EUR payouts. Clients may have seen delayed creation and settlement of payouts. The issue is resolved and normal service is restored. Impact start time: 29/04/2026, 10:35 UTC Impact end time: 29/04/2026, 10:45 UTC Client actions: None Affected components Console (Operational) Signup+ (Operational) From 🇬🇧 TRYEGB22 (Operational) To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) Data (UK & Europe) (Operational) Recurring Payments (Operational) Verification (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) To 🇬🇧 TRYEGB22 (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) To 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) To 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇬🇧 TRYEGB22XXX (Operational) To external accounts (Operational) To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) Sandbox (Operational) From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇬🇧 TRYEGB22XXX (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational)

Read the full incident report →

Minor April 28, 2026

Delayed Payments and Payout Settlements

Detected by Pingoru
Apr 28, 2026, 10:00 PM UTC
Resolved
Apr 28, 2026, 10:00 PM UTC
Duration
Affected: From 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXFrom 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇬🇧 TRYEGB22XXXFrom 🇬🇧 TRYEGB22To 🇬🇧 TRYEGB22From 🇪🇺🇩🇰 SXPYDKKKXXXTo 🇪🇺🇩🇰 SXPYDKKKXXXTo 🇪🇺🇩🇪 SXPYDEHHXXXFrom 🇪🇺🇩🇪 SXPYDEHHXXXTo 🇬🇧 TRYEGB22XXXTo external accountsTo 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 2 updates
  1. identified Apr 28, 2026, 09:31 PM UTC

    Status: Identified We are currently investigating an issue causing delays in payment settlements and payouts. Our engineering team is working to resolve this as quickly as possible. No action needed Impact start time: 28/04/2026, 21:00 UTC Client actions: None Affected components From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇩🇰 SXPYDKKKXXX (Degraded performance) To 🇬🇧 TRYEGB22XXX (Degraded performance) From 🇪🇺🇩🇪 SXPYDEHHXXX (Degraded performance) From 🇬🇧 TRYEGB22 (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) To 🇪🇺🇩🇪 SXPYDEHHXXX (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) To 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance) From 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance) From 🇬🇧 TRYEGB22XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) To 🇬🇧 TRYEGB22 (Degraded performance) To external accounts (Degraded performance) From 🇪🇺🇩🇰 SXPYDKKKXXX (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance)

  2. resolved Apr 28, 2026, 10:00 PM UTC

    Status: Resolved You may have experienced delays in Payment and Payout settlement during the timeframe below. This has now been resolved, Payments and Payouts are settling in a timely manner. Impact start time: 28/04/2026, 21:00 UTC Impact end time: 28/04/2026, 21:40 UTC Client actions: None Affected components To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational) To external accounts (Operational) To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇬🇧 TRYEGB22XXX (Operational) From 🇬🇧 TRYEGB22 (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) To 🇬🇧 TRYEGB22 (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) To 🇬🇧 TRYEGB22XXX (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational)

Read the full incident report →

Minor April 28, 2026

Payment Providers Incorrectly Enabled/Disabled

Detected by Pingoru
Apr 28, 2026, 02:49 PM UTC
Resolved
Apr 28, 2026, 02:49 PM UTC
Duration
Affected: To 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXTo 🇪🇺🇫🇷 TRYEFRP2XXXTo 🇬🇧 TRYEGB22To 🇪🇺🇩🇰 SXPYDKKKXXXTo 🇪🇺🇩🇪 SXPYDEHHXXXTo 🇬🇧 TRYEGB22XXXTo external accountsTo 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇵🇱 PPABPLPKXXX
Timeline · 2 updates
  1. monitoring Apr 28, 2026, 02:48 PM UTC

    Status: Monitoring We identified a configuration issue that caused a small selection of banking providers to be incorrectly enabled or disabled for some clients. As a result, some end-users might have been unable to find their usual provider, or conversely, saw providers that were not previously enabled for your client_id. This issue has now been resolved, and all providers have been rectified back to their original state for your client_id. Impact start time: 13/04/2026, 13:00 UTC Impact end time: 28/04/2026, 13:00 UTC Client actions: None Affected components To 🇪🇺🇩🇪 SXPYDEHHXXX (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇬🇧 TRYEGB22XXX (Degraded performance) To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) To 🇬🇧 TRYEGB22 (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) To 🇪🇺🇩🇰 SXPYDKKKXXX (Degraded performance) To external accounts (Degraded performance) To 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance)

  2. resolved Apr 28, 2026, 02:49 PM UTC

    Status: Resolved We identified a configuration issue that caused a small selection of banking providers to be incorrectly enabled or disabled for some clients. As a result, some end-users might have been unable to find their usual provider, or conversely, saw providers that were not previously enabled for your client_id. This issue has now been resolved, and all providers have been rectified back to their original state for your client_id. Impact start time: 13/04/2026, 13:00 UTC Impact end time: 28/04/2026, 13:00 UTC Client actions: None Affected components To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) To 🇬🇧 TRYEGB22 (Operational) To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) To 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) To 🇬🇧 TRYEGB22XXX (Operational) To external accounts (Operational)

Read the full incident report →

Minor April 27, 2026

Sandbox Signup+ Degraded Performance

Detected by Pingoru
Apr 27, 2026, 09:42 AM UTC
Resolved
Apr 27, 2026, 09:42 AM UTC
Duration
Affected: Sandbox
Timeline · 2 updates
  1. investigating Apr 23, 2026, 10:07 AM UTC

    Status: Investigating We are currently experiencing issues affecting Signup+ requests in the Sandbox environment due to unexpected responses from a third-party provider. As a result, some Sandbox requests may fail or behave unexpectedly. We are actively investigating. Impact start time: 17/03/2026, 01:00 UTC Client actions: None Affected components Sandbox (Degraded performance)

  2. resolved Apr 27, 2026, 09:42 AM UTC

    Status: Resolved We experienced an issue affecting Signup+ requests in the Sandbox environment due to unexpected responses from a third-party provider. The issue has been resolved and normal service has been restored. Impact start time: 17/03/2026, 01:00 UTC Impact end time: 24/04/2026, 17:30 UTC Client actions: None Affected components Sandbox (Operational)

Read the full incident report →

Minor April 25, 2026

PLN Payments Settlement Delays

Detected by Pingoru
Apr 25, 2026, 08:04 PM UTC
Resolved
Apr 25, 2026, 08:04 PM UTC
Duration
Affected: To 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇵🇱 PPABPLPKXXX
Timeline · 2 updates
  1. monitoring Apr 25, 2026, 08:04 PM UTC

    Status: Monitoring You may have experienced delayed settlement for PLN Payouts during the timeframe specified. The service has now recovered and Payouts are settling at normal rate. Impact start time: 25/04/2026, 19:30 UTC Impact end time: 25/04/2026, 20:00 UTC Client actions: None Affected components From 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance) To 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance)

  2. resolved Apr 25, 2026, 08:04 PM UTC

    Status: Resolved You may have experienced delayed settlement for PLN Payouts during the timeframe specified. The service has now recovered and Payouts are settling at normal rate. Impact start time: 25/04/2026, 19:30 UTC Impact end time: 25/04/2026, 20:00 UTC Client actions: None Affected components To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational)

Read the full incident report →

Minor April 19, 2026

EUR Payments Degraded Performance

Detected by Pingoru
Apr 19, 2026, 06:48 AM UTC
Resolved
Apr 19, 2026, 06:48 AM UTC
Duration
Affected: From 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXFrom 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇫🇷 TRYEFRP2XXXTo 🇪🇺🇮🇪 TRYEIE22From 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 4 updates
  1. investigating Apr 18, 2026, 07:43 PM UTC

    Status: Investigating We are experiencing a service degradation affecting EUR payments. Clients may be seeing delayed settlement of EUR payins and payouts. We are investigating this with our banking partner. Impact start time: 18/04/2026, 19:17 UTC Client actions: None Affected components To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance)

  2. identified Apr 18, 2026, 09:44 PM UTC

    Status: Identified Our banking partner has identified the issue causing delayed settlement of EUR payins and payouts and is working on a fix. Impact start time: 18/04/2026, 19:17 UTC Client actions: None Affected components From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance)

  3. identified Apr 18, 2026, 11:08 PM UTC

    Status: Identified Our banking partner has confirmed that as of 21:20 UTC, all payments are settling as normal. However payments initiated between 19:17 and 21:20 UTC may not have reached a final status and could take a few hours to do so. We will provide further updates once all affected payments have reached a final status. Client actions: None Affected components From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance)

  4. resolved Apr 19, 2026, 06:48 AM UTC

    Status: Resolved As of 02:50 UTC, all the remaining EUR payins and payouts affected by the delayed settlement degradation have reached a final status and payments are settling as normal. Impact start time: 18/04/2026, 19:17 UTC Impact end time: 19/04/2026, 02:50 UTC Client actions: None Affected components To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational)

Read the full incident report →

Minor April 14, 2026

Delayed Settlement for EUR Payments

Detected by Pingoru
Apr 14, 2026, 09:55 PM UTC
Resolved
Apr 14, 2026, 09:55 PM UTC
Duration
Affected: From 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇷 TRYEFRP2AAATo 🇪🇺🇪🇪 LHVBEE22XXXTo 🇪🇺🇫🇮 TRYEFIH2XXXFrom 🇪🇺🇮🇪 TRYEIE22To 🇪🇺🇫🇷 TRYEFRP2XXXTo 🇪🇺🇮🇪 TRYEIE22From 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 2 updates
  1. identified Apr 14, 2026, 09:35 PM UTC

    Status: Identified EUR payments are experiencing degraded performance, with settlement delays. We are investigating with our banking partner. Impact start time: 14/04/2026, 21:03 UTC Client actions: None Affected components To 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) To 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) To 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) To 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance)

  2. resolved Apr 14, 2026, 09:55 PM UTC

    Status: Resolved We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payment settlement. The service has recovered and payments are settling in a timely manner. Impact start time: 14/04/2026, 21:03 UTC Impact end time: 14/04/2026, 21:49 UTC Client actions: None Affected components From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) To 🇪🇺🇮🇪 TRYEIE22 (Operational) To 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) To 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) To 🇪🇺🇫🇮 TRYEFIH2XXX (Operational)

Read the full incident report →

Minor March 30, 2026

Failed Smart Retry VRP Payments for GB Providers

Detected by Pingoru
Mar 30, 2026, 05:34 PM UTC
Resolved
Mar 30, 2026, 05:34 PM UTC
Duration
Affected: VerificationRecurring Payments
Timeline · 2 updates
  1. monitoring Mar 30, 2026, 05:34 PM UTC

    Status: Monitoring You may have experienced a small subset of Smart Retry for VRP payments and direct confirmation of funds fail. Impact was limited to Barclays, Lloyds, Halifax, BoS, and Bank of Ireland. The issue is now resolved. Impact start time: 26/03/2026, 11:00 UTC Impact end time: 30/03/2026, 17:40 UTC Client actions: None Affected components Verification (Degraded performance) Recurring Payments (Degraded performance)

  2. resolved Mar 30, 2026, 05:34 PM UTC

    Status: Resolved You may have experienced a small subset of Smart Retry for VRP payments and direct confirmation of funds fail. Impact was limited to Barclays, Lloyds, Halifax, BoS, and Bank of Ireland. The issue is now resolved. Impact start time: 26/03/2026, 11:00 UTC Impact end time: 30/03/2026, 17:40 UTC Client actions: None Affected components Recurring Payments (Operational) Verification (Operational)

Read the full incident report →

Minor March 13, 2026

Payouts Degraded Performance

Detected by Pingoru
Mar 13, 2026, 09:25 PM UTC
Resolved
Mar 13, 2026, 09:25 PM UTC
Duration
Affected: From 🇪🇺🇩🇰 SXPYDKKKXXXFrom 🇪🇺🇩🇪 SXPYDEHHXXX
Timeline · 2 updates
  1. investigating Mar 13, 2026, 08:53 PM UTC

    Status: Investigating We’re seeing delays in settlement for payouts via our banking partner in the EU. No action needed on your end. We’re monitoring closely. Impact start time: 13/03/2026, 18:00 UTC Client actions: None Affected components From 🇪🇺🇩🇪 SXPYDEHHXXX (Degraded performance) From 🇪🇺🇩🇰 SXPYDKKKXXX (Degraded performance)

  2. resolved Mar 13, 2026, 09:25 PM UTC

    Status: Resolved The observed behaviour was not due to degraded performance, our alerting was likely too sensitive. Payouts are processing as normal. Client actions: None Affected components From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational)

Read the full incident report →

Minor February 28, 2026

Verified Payouts, VOP and SignUp+ Product Degraded Performance

Detected by Pingoru
Feb 28, 2026, 11:07 PM UTC
Resolved
Feb 28, 2026, 11:07 PM UTC
Duration
Affected: Signup+From 🇪🇺🇪🇪 LHVBEE22XXXFrom 🇪🇺🇮🇪 TRYEIE22From 🇪🇺🇩🇰 SXPYDKKKXXXVerificationFrom 🇪🇺🇩🇪 SXPYDEHHXXXFrom 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 3 updates
  1. investigating Feb 28, 2026, 10:42 PM UTC

    Status: Investigating We are currently experiencing a service disruption affecting verified payouts, VOP and Signup+, causing payouts settlement delays in the EU. We are investigating this. Impact start time: 28/02/2026, 22:00 GMT Client actions: None Affected components From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance) From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) Signup+ (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇩🇪 SXPYDEHHXXX (Degraded performance) From 🇪🇺🇩🇰 SXPYDKKKXXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) From 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance) Verification (Degraded performance)

  2. monitoring Feb 28, 2026, 10:56 PM UTC

    Status: Monitoring The system has recovered and we are currently monitoring its activity. Clients should now see normal behaviour using verified payouts, VOP and Signup+ in th EU. Impact start time: 28/02/2026, 22:00 GMT Impact end time: 28/02/2026, 22:30 GMT Client actions: None Affected components From 🇪🇺🇮🇪 TRYEIE22 (Operational) Signup+ (Operational) From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational) Verification (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational)

  3. resolved Feb 28, 2026, 11:07 PM UTC

    Status: Resolved Normal service has been restored. Clients should now see normal behaviour using verified payouts, VOP and Signup+ in th EU. Impact start time: 28/02/2026, 22:00 GMT Impact end time: 28/02/2026, 22:30 GMT Client actions: None Affected components Verification (Operational) Signup+ (Operational) From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇩🇰 SXPYDKKKXXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇩🇪 SXPYDEHHXXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational)

Read the full incident report →

Minor February 27, 2026

GBP Payments Degraded Performance

Detected by Pingoru
Feb 27, 2026, 01:12 PM UTC
Resolved
Feb 27, 2026, 01:12 PM UTC
Duration
Affected: From 🇬🇧 TRYEGB22XXXFrom 🇬🇧 TRYEGB22To 🇬🇧 TRYEGB22To 🇬🇧 TRYEGB22XXX
Timeline · 5 updates
  1. investigating Feb 27, 2026, 09:40 AM UTC

    Status: Investigating We are currently experiencing a service degradation with GBP payments. Clients may be seeing delayed settlement of payins and payouts. We are investigating this with our banking partner. Impact start time: 27/02/2026, 09:40 GMT Client actions: None Affected components From 🇬🇧 TRYEGB22 (Degraded performance) To 🇬🇧 TRYEGB22XXX (Degraded performance) To 🇬🇧 TRYEGB22 (Degraded performance) From 🇬🇧 TRYEGB22XXX (Degraded performance)

  2. investigating Feb 27, 2026, 10:55 AM UTC

    Status: Investigating We are currently experiencing a service degradation with GBP payments. Clients may be seeing delayed settlement of payins and payouts. A proportion of payouts are starting to settle but payins are still experiencing delayed settlement. We are continuing to investigate with our Banking Partner. Impact start time: 27/02/2026, 09:40 GMT Client actions: None Affected components From 🇬🇧 TRYEGB22XXX (Degraded performance) From 🇬🇧 TRYEGB22 (Degraded performance) To 🇬🇧 TRYEGB22XXX (Degraded performance) To 🇬🇧 TRYEGB22 (Degraded performance)

  3. identified Feb 27, 2026, 11:35 AM UTC

    Status: Identified We experienced a service degradation with GBP payments. Clients may have seen delayed settlement of payins and payouts. A proportion of payouts and payins are starting to settle and our banking partner is continuing to work through the backlog of unsettled payments. We are monitoring and will confirm full resolution once the backlog of payments has been cleared. Impact start time: 27/02/2026, 09:40 GMT Client actions: None Affected components From 🇬🇧 TRYEGB22XXX (Degraded performance) From 🇬🇧 TRYEGB22 (Degraded performance) To 🇬🇧 TRYEGB22XXX (Degraded performance) To 🇬🇧 TRYEGB22 (Degraded performance)

  4. identified Feb 27, 2026, 12:09 PM UTC

    Status: Identified We experienced a service degradation with GBP payments. Clients may have seen delayed settlement of payins and payouts. Payins settlement has returned to normal and our banking partner is continuing to work through the backlog of unsettled payouts. We are continuing to monitor and will confirm full resolution once the payouts backlog has been cleared. Client actions: None Affected components From 🇬🇧 TRYEGB22XXX (Degraded performance) From 🇬🇧 TRYEGB22 (Degraded performance) To 🇬🇧 TRYEGB22XXX (Operational) To 🇬🇧 TRYEGB22 (Operational)

  5. resolved Feb 27, 2026, 01:12 PM UTC

    Status: Resolved We experienced a service degradation with GBP payments due to an issue with our banking partner. Clients may have seen delayed settlement of payins and payouts. Normal service is resumed. Impact start time: 27/02/2026, 09:40 GMT Impact end time: 27/02/2026, 13:08 GMT Client actions: None Affected components From 🇬🇧 TRYEGB22XXX (Operational) From 🇬🇧 TRYEGB22 (Operational) To 🇬🇧 TRYEGB22XXX (Operational) To 🇬🇧 TRYEGB22 (Operational)

Read the full incident report →

Minor February 17, 2026

Payout Degraded Performance

Detected by Pingoru
Feb 17, 2026, 11:00 PM UTC
Resolved
Feb 17, 2026, 11:00 PM UTC
Duration
Affected: From 🇪🇺🇪🇪 LHVBEE22XXXFrom 🇪🇺🇮🇪 TRYEIE22From 🇪🇺🇫🇷 TRYEFRP2XXXFrom 🇪🇺🇫🇷 TRYEFRP2AAAFrom 🇪🇺🇫🇮 TRYEFIH2XXX
Timeline · 2 updates
  1. identified Feb 17, 2026, 10:35 PM UTC

    Status: Identified We’re seeing degraded performance in payout. Our clients may encounter delays in settlement. We’re actively investigating. Impact Start time: 17/02/2026, 23:04 UTC Client actions: None Affected components From 🇪🇺🇫🇮 TRYEFIH2XXX (Degraded performance) From 🇪🇺🇮🇪 TRYEIE22 (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2AAA (Degraded performance) From 🇪🇺🇫🇷 TRYEFRP2XXX (Degraded performance) From 🇪🇺🇪🇪 LHVBEE22XXX (Degraded performance)

  2. resolved Feb 17, 2026, 11:00 PM UTC

    Status: Resolved Normal service has been restored. Payouts are now settling normally. Impact start time: 17/02/2026, 23:04 UTC Impact end time: 17/02/2026, 23:37 UTC Client actions: None Affected components From 🇪🇺🇫🇷 TRYEFRP2AAA (Operational) From 🇪🇺🇫🇷 TRYEFRP2XXX (Operational) From 🇪🇺🇪🇪 LHVBEE22XXX (Operational) From 🇪🇺🇫🇮 TRYEFIH2XXX (Operational) From 🇪🇺🇮🇪 TRYEIE22 (Operational)

Read the full incident report →

Minor February 16, 2026

Data Product Degraded Performance

Detected by Pingoru
Feb 16, 2026, 04:21 PM UTC
Resolved
Feb 16, 2026, 04:21 PM UTC
Duration
Timeline · 2 updates
  1. identified Feb 16, 2026, 02:53 PM UTC

    Status: Identified We’re currently experiencing degraded performance on the Data API. Clients may observe failure in Auth sessions with Starling provider and some French providers. Our engineering team is investigating the issue Start time: 02/02/2026, 4:30 UTC Client actions: None Affected components Data (UK & Europe) (Degraded performance)

  2. resolved Feb 16, 2026, 04:21 PM UTC

    Status: Resolved Upon further investigation, we have established that the impact actually began on 04/02/2026, 11:49 UTC. Please note that this is a correction to the previously communicated start time of 02/02/2026, 04:30 UTC Data API degradation has been resolved. Normal service has been restored. Impact start time: 04/02/2026, 11:49 UTC Impact end time: 16/02/2026 15:35 UTC Client actions: None Affected components Data (UK & Europe) (Operational)

Read the full incident report →

Minor February 10, 2026

PLN PIS Settlement Delays

Detected by Pingoru
Feb 10, 2026, 03:07 PM UTC
Resolved
Feb 10, 2026, 03:07 PM UTC
Duration
Affected: To 🇪🇺🇵🇱 PPABPLPKXXXFrom 🇪🇺🇵🇱 PPABPLPKXXX
Timeline · 2 updates
  1. investigating Feb 10, 2026, 12:48 PM UTC

    Status: Investigating We’re seeing delays in settlement notifications via our banking partner in the EU. No action needed on your end. We’re monitoring closely. Impact start time: 10/02/2026, 12:30 UTC Client actions: None Affected components To 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance) From 🇪🇺🇵🇱 PPABPLPKXXX (Degraded performance)

  2. resolved Feb 10, 2026, 03:07 PM UTC

    Status: Resolved Settlement delays have now been resolved. All transactions have now reached their intended terminal status. Regular processing timings have resumed. Impact start time: 10/02/2026, 12:30 UTC Impact end time: 10/02/2026, 14:39 UTC Client actions: None Affected components To 🇪🇺🇵🇱 PPABPLPKXXX (Operational) From 🇪🇺🇵🇱 PPABPLPKXXX (Operational)

Read the full incident report →

Looking to track TrueLayer downtime and outages?

Pingoru polls TrueLayer's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when TrueLayer reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track TrueLayer alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring TrueLayer for free

5 free monitors · No credit card required