Tink Outage History
34 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Tink Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Issue with Risk productsWe experienced a dip in traffic for Risk products between 11:15 and 12:00 CET today. This affected Income Check, Expense Check and Risk Insights.The issue was resolved by rolling back a hotfix, and performance has… | 0 min | Resolved |
| Oct 17, 2026 | Issue with Payment Initiation & Account Information ServicesWe have experienced an outage with Payment Initiation and Account check servicices between 18:15 and 19:35 CET in Autria , Germany, Poland and Czech Republic Performance has since returned to normal. We apologize for… | 0 min | Resolved |
| Oct 13, 2026 | Scheduled Infrastructure MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 9, 2026 | Issue with Enrichment serviceThis incident has been resolved. | 21 min | Resolved |
| Oct 7, 2026 | Issue with Enrichment serviceWe apologise for the inconvenience caused. On 6 October 2026, between 09:30 CEST and 14:30 CEST, we experienced a temporary issue that resulted in delays in enrichment processing for the Data Enrichment API. The issue… | 0 min | Resolved |
| Oct 6, 2026 | Issue with Enrichment serviceWe experienced a temporary outage between 15:28 CEST and 16:49 CEST. This resulted in increased of 503 responses. Performance has since returned to normal. We apologise for the inconvenience. | 0 min | Resolved |
| Sep 25, 2026 | Issue with Payment InitiationService is back to normal. | 42 min | Resolved |
| Sep 17, 2026 | Scheduled Infrastructure MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 16, 2026 | Issue affecting several Tink products## Introduction On 16th July between 09:54 and 10:56 CEST Tink experienced a technical issue which impacted Tink Console, Tink Link, Payment Initiation Services, Account Information Services, and selected risk… | 100h 29m | Resolved |
| Jul 7, 2026 | Issue affecting several Tink products**Introduction** On 2026-07-07 between 15:26 and 15:51 CEST, Tink experienced a technical issue which impacted API availability for some of our customers. During the incident, end-users experienced issues with… | 23h 57m | Resolved |
| Jun 22, 2026 | Issue with WebhooksBetween June 20th, 02:00 CEST and June 22nd, 13:40 CET Tink has experienced degraded performance with webhooks. We have pinpointed the root cause of the issue and resolved it. We are sorry any issues this may have… | 0 min | Resolved |
| Jun 16, 2026 | Issue with Bulk PaymentsThis issue has been resolved. We apologize for the inconvenience. | 1h 16m | Resolved |
| Jun 10, 2026 | Maintenance work for NordeaThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Jun 2, 2026 | Issue with PaymentsThis issue has been resolved. We apologize for the inconvenience. | 22h 46m | Resolved |
| Jun 1, 2026 | Degraded perofrmance affecting Tink ConsoleThis incident has been resolved. | 4h 18m | Resolved |
| May 28, 2026 | Degraded performance affecting SettlementsThis incident has been resolved. | 1h 15m | Resolved |
| May 21, 2026 | Disruptions for the Payments service on the German marketThis issue has been resolved. We apologize for the inconvenience. | 55 min | Resolved |
| May 19, 2026 | Issue with SettlementsWe can confirm that the previously identified issue affecting inbound and outbound SEPA payments has now been resolved. Payments are processing as expected. We apologise for the inconvenience caused and thank you for… | 69h 46m | Resolved |
| May 11, 2026 | Account exclusion functionality is currently not working as expectedThe issue has been resolved. We apologize for the inconvenience. | 46 min | Resolved |
| Mar 25, 2026 | Issue with Bulk PaymentsThis issue has been resolved. We apologize for the inconvenience. | 49 min | Resolved |
| Mar 19, 2026 | Nordea Open Banking Bulk payments - Tink Link error screenThe issue has been resolved. We apologize for the inconvenience. | 10h 55m | Resolved |
| Mar 13, 2026 | Scheduled database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 12, 2026 | Scheduled database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 5, 2026 | Issue with Payments**Introduction** On 5 March, between 10:31 CET and 10:59 CET, Tink experienced a technical issue that impacted the Payment Initiation service across multiple markets. The issue was detected immediately, and mitigation… | 30 min | Resolved |
| Mar 3, 2026 | Transactions and Risk reporting - degraded performanceWe experienced a technical issue between 2 March 11:30 CET and 3 March 13:42 CET that caused degraded performance of Transactions and Risk reporting. During this time, some users may have experienced empty reports or… | 0 min | Resolved |
| Feb 3, 2026 | Issue with Analytics in Tink ConsoleThis incident has been resolved. | 16h 16m | Resolved |
| Feb 3, 2026 | Issue with Payment InitiationsWe experienced a technical issue between 10:43 CET and 11:18 CET that caused a degraded performance of the Payment product. During this time some users in the FI and DE markets may have experienced issues with… | 0 min | Resolved |
| Feb 2, 2026 | Issue with Payments# Introduction On 2 February 2026, between 17:48 and 19:01 CET, Tink experienced a technical issue that affected the availability of all Payments products across all markets. During this period of the incident… | 1h 1m | Resolved |
| Jan 21, 2026 | Issue with multiple Tink productsThis issue has been resolved. We apologize for the inconvenience. | 13 min | Resolved |
| Dec 8, 2025 | Issue with Enrichment service.We experienced Temporary outage on data enrichment service between 10.20 and 10:40 CET This resulted in increased of Http 503 responses. Performance has since returned to normal. We apologise for the inconvenience. | 0 min | Resolved |
| Nov 24, 2025 | Issue with multiple Tink products# Introduction On 24th November between 15:06 and 15:30 CET Tink experienced a technical issue which impacted all products in all European markets. During the time of the incident, end-users were experiencing issues… | 0 min | Resolved |
| Nov 20, 2025 | Issues with TransactionsWe experienced degraded performance between 18:00 CET and 21:00 CET. Degraded performance fetching Transactions. Affected flows: On-demand refreshes and background refreshes Performance has since returned to normal… | 0 min | Resolved |
| Nov 20, 2025 | Issue with multiple products# Introduction On 20th November between 11:50 and 12:30 CET Tink experienced a technical issue which impacted AIS and PIS products in all markets. During the time of the incident, end-users were experiencing issues… | 4h 28m | Resolved |
| Nov 5, 2025 | Full outage - Auto refreshesThis issue has been resolved. We apologize for the inconvenience. | 44 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Tink incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Tink Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Tink acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Tink outage in this window ran 4d 4h, against a mean recovery of 7h 52m. If you depend on Tink in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.