Update - Please note that we're still monitoring and investigating the incident.
Jan 27, 09:10 CET
Monitoring - The last disturbances happened between 12:28 and 12:56 CET. We are now back to monitoring the situation.
Jan 26, 14:11 CET
Investigating - Since around 12:30 CET, we're seeing the higher latencies and the higher error rates again. We've additionally reached out to AWS to find a solution.
Jan 26, 12:48 CET
Update - Please not that we're still taking care about this issue.
Jan 25, 12:34 CET
Monitoring - The following endpoint is/was also affected by this incident:
GET /data/v2/transactions

However, we're already seeing the issues go down. We'll monitor the situation for a while.
Jan 25, 09:48 CET
Update - We are doing our best to get this issue resolved as soon as possible.
Jan 25, 09:18 CET
Update - These endpoints might receive an error:

GET /api/v1/budgets/summaries
POST /api/v1/user-report-bundles/
DELETE /api/v1/credentials/{id}
PUT /api/v1/accounts/{id}
POST /api/v1/search/

These might experience high latencies:

DELETE /api/v1/credentials/{id}
POST /api/v1/search/
PUT /api/v1/accounts/{id}
POST /api/v1/user-report-bundles/
GET /api/v1/budgets/summaries
GET /api/v1/transactions/
PUT /connector/users/{externalUserId}/transactions/{externalTransactionId}
Jan 25, 09:14 CET
Investigating - The issue leads to higher latencies and higher error rates in the Transaction APIs. We're just looking into the details, an update is coming soon.
Jan 25, 08:59 CET
Monitoring - We increased the number of Aggregation Servicesto fix the issue.
Jan 21, 12:49 CET
Identified - Aggregation Service was not able to handle incoming requests fast enough during the past evening (Jan-20th) and caused delayed background refreshes delivery.
Jan 21, 12:47 CET

About This Site

Welcome Tink status!

Here you can find current information on the operational status of Tink services, as well as updates on any ongoing or historical maintenance or incidents.

For information about bank integration status, please visit the relevant page for the market you're interested in:

🇦🇹 Austria: https://tinkaustria.statuspage.io
🇪🇪🇱🇻🇱🇹 Baltics: https://tinkbaltics.statuspage.io
🇧🇪 Belgium: https://tinkbelgium.statuspage.io
🇩🇰 Denmark: https://tinkdenmark.statuspage.io
🇫🇮 Finland: https://tinkfinland.statuspage.io
🇫🇷 France: https://tinkfrance.statuspage.io
🇩🇪 Germany: https://tinkgermany.statuspage.io
🇮🇪 Ireland: https://tinkireland.statuspage.io
🇮🇹 Italy: https://tinkitaly.statuspage.io
🇳🇱 Netherlands: https://tinknetherlands.statuspage.io
🇳🇴 Norway: https://tinknorway.statuspage.io
🇵🇹 Portugal: https://tinkportugal.statuspage.io
🇪🇸 Spain: https://tinkspain.statuspage.io
🇸🇪 Sweden: https://tinksweden.statuspage.io
🇬🇧 UK: https://tinkuk.statuspage.io

Aggregation services Operational
90 days ago
99.93 % uptime
Today
Payments services Operational
90 days ago
99.95 % uptime
Today
PFM services Operational
90 days ago
100.0 % uptime
Today
Data enrichment services Operational
90 days ago
100.0 % uptime
Today
Other services Operational
Platform ? Operational
Support channels Operational
Service Desk Portal ? Operational
Email Requests ? Operational
status.tink.com: Email notifications Operational
status.tink.com: SMS Notifications Operational
status.tink.com: HTTPS Pages Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Essential maintenance work must be carried out. The Tink API will be unavailable during this time. The estimated downtime is ~2 minutes.

We thank you for your patience and understanding.
Posted on Jan 25, 14:41 CET
Past Incidents
Jan 27, 2022

Unresolved incident: Transaction Elasticsearch storage issues in the production environment.

Jan 26, 2022
Resolved - We're not seeing disturbances anymore, the incident is resolved.
Jan 26, 15:09 CET
Update - The payment service for the following banks might be affected by the issue: RBS, Ulster and Natwest
Jan 26, 14:31 CET
Investigating - We're currently experiencing issues with the credentials refreshes for several providers; 565 requests failed in the last 2 hours. The affected providers declare an empty set of capabilities which causes refreshes to fail.
We're already investigating this.
Jan 26, 13:54 CET
Jan 25, 2022
Jan 24, 2022

No incidents reported.

Jan 23, 2022

No incidents reported.

Jan 22, 2022

No incidents reported.

Jan 21, 2022
Jan 20, 2022

No incidents reported.

Jan 19, 2022

No incidents reported.

Jan 18, 2022

No incidents reported.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.