59 Tink incidents · januar 2025 — official updates, affected components, duration and resolution details.
Vi har oplevet en afbrydelse med betaling initiering og konto check tjenester mellem 18: 15 og 19: 35 CET i Autria, Tyskland, Polen og Tjekkiet Performance er siden vendt tilbage til normal. Vi undskylder ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplever i øjeblikket forsinkelser i returneringen af berigede transaktioner. Transaktionsindtagelse fungerer som forventet.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undskylder ulejligheden. Den 6. oktober 2026, mellem 09: 30 CEST og 14: 30 CEST, oplevede vi et midlertidigt problem, der resulterede i forsinkelser i berigningsbehandling for Data Berichment API. Spørgsmålet er nu løst, og berigningsprocessen fungerer normalt.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplevede en midlertidig afbrydelse mellem 15: 28 CEST og 16: 49 CEST. Dette resulterede i en stigning i 503 responser. Performance er siden vendt tilbage til normal. Vi undskylder ulejligheden.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er i øjeblikket ved at undersøge et problem med betaling indledning.
Vi overvåger post recovery.
Tjenesten er normal igen.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er i øjeblikket ved at undersøge et problem, der påvirker flere Tink produkter. Se den fuldstændige liste over berørte produkter.
Spørgsmålet er blevet identificeret, og vi arbejder i øjeblikket på en løsning.
Vi fortsætter med at arbejde på en løsning på dette problem.
Tjenesten er i øjeblikket ved at komme sig, og vi overvåger aktivt situationen.
Dette spørgsmål er blevet løst. Vi undskylder ulejligheden.
# # Indledning Den 16. juli mellem 09: 54 og 10: 56 CEST Klokke oplevede et teknisk problem, som påvirkede Klokkekonsollen, KlokkeLink, betalingsinitieringstjenester, kontooplysningstjenester og udvalgte risikoprodukter til alle europæiske markeder. Under hændelsen oplevede slutbrugere problemer med at starte eller fuldføre autentificering, samtykke, regnskabsoplysninger og betalingsinitieringsture og var ude af stand til at logge ind på Tink Console for at styre deres integration med Tink platform. # Root Cause Analysis Efter en grundig undersøgelse, blev det fundet ud af, at en ekstern infrastruktur afhængighed, der leveres af Tink "s cloud-udbyder, der anvendes til routing customer-vender trafik funktioneret, hvilket førte til afbrydelse af Tink Link- baserede brugerrejser og midlertidig manglende adgang til Tink Console for nogle kunder. # Respiration Når problemet blev identificeret, Tink dirigeret påvirket trafik gennem en alternativ konfiguration og restaureret de ramte tjenester til normal drift. # Follow- up actions For at undgå lignende problemer i fremtiden vil Klokkeblomst gennemføre følgende foranstaltninger: 1. Forbedre overvågning og varsling for kritiske eksterne infrastruktur afhængigheder. 2. Dokument og validere inddrivelsesprocedurer for routing omkring lignende fejl. 3. Kør yderligere træning for hurtigere identifikation og håndtering af sammenlignelige infrastrukturrelaterede spørgsmål.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er i øjeblikket ved at undersøge et problem, der påvirker flere Tink produkter. Se den fuldstændige liste over berørte produkter.
Tjenesten er i øjeblikket ved at komme sig, og vi overvåger aktivt situationen.
Dette spørgsmål er blevet løst. Vi undskylder ulejligheden.
* * Indledning * * På 2026-07- 07 mellem 15: 26 og 15: 51 CEST oplevede Klokke et teknisk problem, som påvirkede API tilgængelighed for nogle af vores kunder. Under hændelsen oplevede slutbrugerne problemer med at få adgang til de berørte Tink-tjenester. * * Root årsag analyse * * Efter en grundig undersøgelse, den begivenhed, som udløste den midlertidige API tilgængelighed problem blev identificeret og løst med succes. * * genoptræning * * Når spørgsmålet blev identificeret, Klokke genoprettet service tilgængelighed og gennemført yderligere beskyttelsesforanstaltninger for at forbedre modstandsdygtigheden mod lignende begivenheder. * * Opfølgningsaktioner * * For at undgå lignende problemer i fremtiden vil Klokkeblomst gennemføre følgende foranstaltninger: 1. Styrke beskyttende kontrol på tværs af relevante produktionsmiljøer. 2. Forbedre overvågning og reaktion procedurer for høj effekt tilgængelighed begivenheder. 3. Gennemgå og forbedre tjenesten modstandsdygtighed for at reducere virkningen af lignende hændelser.
Automatisk oversat fra den officielle hændelsesopdatering.
Between 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 caused.
The issue has been identified and we are currently working on a solution.
This issue has been resolved. We apologize for the inconvenience.
We are currently investigating an issue with Payment Initiation.
Service is currently recovering and we are actively monitoring the situation.
This issue has been resolved. We apologize for the inconvenience.
The issue has been identified and we are currently working on a solution.
This incident has been resolved.
We have identified and are currently investigating an issue with our provider which is affecting inbound Faster Payments Service (FPS), which may result in delays.
This incident has been resolved.
We are currently investigating an issue with payments in German market.
This issue has been resolved. We apologize for the inconvenience.
We have identified and are currently investigating an issue with our provider which is affecting both outbound and inbound SEPA payments, which may result in delays.
We continue to monitor an issue affecting both outbound and inbound SEPA payments. While some payments are processing, we cannot yet confirm full service restoration. We are actively investigating and will provide a further update as soon as possible. We apologise for the inconvenience.
We 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 your patience.
We are currently investigating an issue with the account exclusion functionality, as accounts are not being excluded as intended. Further updates will be provided as soon as possible.
The issue has been resolved. We apologize for the inconvenience.
We are currently investigating an issue with Bulk Payments in Sweden.
This issue has been resolved. We apologize for the inconvenience.
We are currently looking into an issue with Nordea bulk payments. The initiation for the SE market has been failing for about 3 hours.
The issue has been resolved. We apologize for the inconvenience.
We are currently investigating an issue with Payment initiations across multiple markets.
This issue has been resolved. We apologize for the inconvenience.
**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 actions were taken promptly to limit the impact. During the incident window, some end users experienced difficulties when initiating payments. **Root Cause Analysis** Following a thorough investigation, it was determined that a recently introduced change contained a defect that caused unexpected request failures within the Payment Initiation service. This resulted in a temporary disruption to payment initiation flows in the affected markets. **Remediation** As soon as the issue was identified, the affected deployment was immediately rolled back. This action mitigated the impact and restored normal service functionality. **Follow-up actions** To reduce the risk of similar incidents in the future, Tink is taking the following actions: 1. **Extend test coverage for payment initiation scenarios** Further strengthen the pre-deployment validation for payment flows by expanding our end-to-end test coverage for payment flows.
We 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 missing data when viewing or downloading Transactions and Risk reports. Performance has since returned to normal. We apologize for the inconvenience.
We are currently investigating an issue with Analytics in Tink Console.
This incident has been resolved.
