Clari driftsforstyrrelser

1. 8. september 2026 kl. 19.57 UTCmonitoring

   Vores ingeniørhold er opmærksomme på dette spørgsmål i forbindelse med en tredjeparts afbrydelse og overvåger fremskridtene i dette spørgsmål. Smarte resuméer genereres ikke til Copilot-opkald. Opkaldsbehandling fungerer stadig, og der vil blive udarbejdet resuméer, når afbrydelsen er løst.

2. 9. september 2026 kl. 12.39 UTCresolved

   Vi har bekræftet, at problemet er løst for de berørte brugere. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. september 2026 kl. 15.11 UTCinvestigating

   Vi har identificeret visse dele af systemet oplever længere svartider ved indlæsning af sider. Vi er i øjeblikket ved at undersøge spørgsmålet, og vil give en opdatering snart.

2. 8. september 2026 kl. 16.11 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 8. september 2026 kl. 16.23 UTCresolved

   Vores Engineering teams har løst problemet, og som et resultat, system funktionalitet er blevet genoprettet til normal

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 15.25 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 2. september 2026 kl. 16.14 UTCresolved

   Vi har bekræftet, at problemet er løst for de berørte brugere. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. august 2026 kl. 17.56 UTCinvestigating

   Vi har modtaget rapporter fra kunder om, at deres Salesforce integration bruger bliver afbrudt på grund af token udløb. Vores ingeniørhold undersøger sagen.

2. 18. august 2026 kl. 15.24 UTCinvestigating

   Et lille antal kunder havde deres Salesforce integration bruger afbrudt på grund af token udløb. Når dette sker, er den regelmæssige datasynkronisering til Clari ude af stand til at køre. Vores ingeniørhold undersøger problemet sammen med Salesforce. Der er ikke observeret nye forstyrrelser siden 2026-0816. Hvis din integrationsbruger er blevet afbrudt, kan du tilslutte den igen for at løse sync-problemet. Hvis du har brug for hjælp, bedes du kontakte support for at få hjælp.

3. 19. august 2026 kl. 17.12 UTCmonitoring

   Problemet synes at have været en engangsbegivenhed med Salesforce. Vi fortsætter med at overvåge for enhver gentagelse og er aktivt engageret med Salesforce støtte til at forstå, hvad der skete, og hvordan man kan undgå yderligere hændelser. Vi vil efterlade denne rekord i "overvågning" tilstand, indtil vi har en tilfredsstillende forståelse om hændelsen, men forventer ikke at foretage yderligere opdateringer.

4. 25. august 2026 kl. 21.05 UTCresolved

   Vi har bekræftet fra Salesforce hvad der forårsagede udfald for de ramte brugere. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

5. 28. august 2026 kl. 16.39 UTCpostmortem

   På 2026-08- 16, en Salesforce Hyperforce migration forårsaget forbindelse afbrydelser mellem Salesforce og Clari på tværs af en lille gruppe af kundekonti. Dette spørgsmål midlertidigt pause automatiserede dataopdateringer for nogle organisationer og krævede deres brugere genautentificere med Salesforce. Der er ingen kendt måde at undgå denne situation for fremtidige Hyperforce vandringer, men vi fortsætter med at arbejde med Salesforce for at udforske muligheder.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 5. august 2026 kl. 10.50 UTCidentified

   Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading . The next status update will be after the fix has been applied.

2. 5. august 2026 kl. 12.44 UTCidentified

   Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading The next status update will be after the fix has been applied.

3. 5. august 2026 kl. 12.52 UTCmonitoring

   The underlying problem has been fixed, we are monitoring to ensure full functionality is restored.

4. 5. august 2026 kl. 13.29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 5. august 2026 kl. 13.54 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. No new errors have been observed in last 60 minutes of monitoring. All the impacted components are fully operational now. A summary of the incident will be posted within the next three US business days.

6. 7. august 2026 kl. 13.49 UTCpostmortem

   At approximately 2026-08-05 00:02 UTC, a subset of organizations experienced errors when attempting to access the Clari application. Affected users saw the message: "Something went wrong with loading application resources." Our engineering team identified a regression introduced in a recent deployment and issued a hotfix. Systems returned to normal operations at 2026-08-05 13:30 UTC . No customer data was at risk at any point during this incident.

1. 27. juli 2026 kl. 15.07 UTCinvestigating

   Vi undersøger i øjeblikket rapporter om intermitterende adgangsproblemer med Clari-platformen. Kunderne kan få svært ved at få adgang til programmet eller møde langsom præstation. Vores ingeniørhold arbejder aktivt på at løse dette problem. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 27. juli 2026 kl. 15.25 UTCmonitoring

   Vores ingeniørhold har løst problemet, og systemets ydeevne vender tilbage til det normale. Vi fortsætter med at overvåge løsningen.

3. 27. juli 2026 kl. 19.41 UTCresolved

   Efter at have overvåget spørgsmålet i 3 timer, har vi ikke set nogen tilfælde, og platformen har været stabil. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

4. 29. juli 2026 kl. 19.05 UTCpostmortem

   På omkring 2026-07- 27 13: 15 UTC nogle brugere oplevede lange side belastning gange og fejl, når du forsøger at bruge Clari ansøgning. Teknikerne var i stand til at afgøre, at et problem med skalering nogle af vores cloud-baserede tjenester var kilden til problemet og indsat en rettelse til at genoprette systemets ydeevne. Systemer vendte tilbage til normal drift fra 2026- 07- 27 15: 30 UTC og ingen kundedata var i fare under udfald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. juli 2026 kl. 15.18 UTCinvestigating

   Nogle kunder kan opleve problemer med Clari Copilot opkald optagelser i Zoom. Vores ingeniørhold undersøger sagen.

2. 13. juli 2026 kl. 20.19 UTCinvestigating

   Vores ingeniørhold efterforsker stadig. Problemet er at påvirke kunderne afhængig af webbaserede optagere til Zoom optagelser. Vi vil give en anden opdatering, så snart mere information er tilgængelig.

3. 14. juli 2026 kl. 08.15 UTCinvestigating

   De påvirkede kunder fortsætter med at se problemer med webbaserede optagere på Zoom. Vores ingeniørteam undersøger aktivt med Zoom support og gennemgår alternative stier for de påvirkede kunder til at genoptage optagelsen funktionalitet. Vi vil give en anden opdatering, så snart mere information er tilgængelig.

4. 14. juli 2026 kl. 17.25 UTCinvestigating

   Spørgsmålet er stadig under undersøgelse. Imponerede kunder oplever fortsat problemer med webbaserede optagere på Zoom. Vores undersøgelse tyder på, at nylige ændringer i Zooms platformsadfærd forhindrer nogle optagere i at deltage i kundemøder. Vores ingeniørteam arbejder aktivt med Zoom Support for at løse problemet. Vi vil give en anden opdatering, så snart mere information bliver tilgængelig.

5. 14. juli 2026 kl. 18.30 UTCidentified

   Vores ingeniørhold har identificeret problemet og er ved at implementere en rettelse.

6. 14. juli 2026 kl. 22.53 UTCidentified

   Vi har offentliggjort in-app vejledning instruere berørte kunder til at genforbinde deres Zoom integration i Clari Copilot, så kunderne kan genoprette Copilots evne til at optage Zoom møder.

7. 15. juli 2026 kl. 07.11 UTCmonitoring

   Vi har arbejdet med Zoom for at løse problemet med webbaserede båndoptagere. Optagelser fungerer nu som forventet. Vores ingeniørhold overvåger systemet, og vi vil give endnu en opdatering, hvis noget ændres. For berørte kunder, herunder dem, der tidligere har tilsluttet deres Zoom integration, er der ikke behov for yderligere handling. Hvis du stadig oplever problemer, bedes du kontakte vores support team.

8. 15. juli 2026 kl. 11.08 UTCresolved

   Vi har bekræftet, at problemet er løst for de berørte brugere. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

9. 20. juli 2026 kl. 13.09 UTCpostmortem

   Fra omkring 2026- 07- 13 06: 30 UTC, en ændring i Zooms platform påvirket evnen til Clari Copilot Zoom web-optager til at deltage og optage møder. Som et resultat, nogle kunder var ude af stand til at registrere Zoom møder i Copilot i den ramte periode. Dette problem påvirkede kun Zoom webbaseret optagelse; andre optageplatforme blev ikke påvirket. Møder, der er planlagt til optagelse i denne periode, kan ikke være registreret. Ved at identificere problemet, Clari engineering team arbejdede tæt sammen med Zoom for at undersøge ændringen, bestemme dens indvirkning, og gennemføre de nødvendige lempelser. Zoom web-optager slutter er vendt tilbage til normal drift, og vi bekræftede fuld inddrivelse ved ca. 2026- 07- 15 11: 08 UTC. Vi fortsætter med at arbejde med Zoom for bedre at forstå ændringen og styrke vores integration, så lignende platformændringer kan håndteres mere yndefuldt i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 14.51 UTCinvestigating

   Our engineering team is actively investigating.

2. 22. juni 2026 kl. 16.03 UTCidentified

   We are observing a partial outage with Copilot recordings across all platforms. Our engineering team is actively investigating.

3. 22. juni 2026 kl. 17.40 UTCmonitoring

   We identified a few changes from the Copilot Infrastructure maintenance on Saturday June 20th that caused some recorders to fail. We have fixed the issue and are continuing to monitor the system. We will provide another update end of day tomorrow before we resolve this incident.

4. 22. juni 2026 kl. 17.56 UTCidentified

   We have identified that we are not showing the consent page during call recordings. We are working on a fix and will provide an update as soon as the issue is resolved.

5. 22. juni 2026 kl. 18.40 UTCmonitoring

   We have resolved the issue that was preventing the consent page from displaying during call recordings. We are continuing to monitor the system after the Copilot Infrastructure maintenance on Saturday June 20th and we will provide another update by the end of day tomorrow before we resolve this incident.

6. 23. juni 2026 kl. 18.20 UTCmonitoring

   We are continuing to monitor this issue and will leave this incident open until the end of the day. If no further issues are observed by that time, we will resolve the incident. If you are continuing to see any issues with the Copilot platform please reach out to the Clari customer support team.

7. 24. juni 2026 kl. 01.48 UTCresolved

   After monitoring Copilot performance throughout the day and not seeing any reoccurrence of the issues the Clari Engineering team is marking this incident as resolved.

8. 26. juni 2026 kl. 15.19 UTCpostmortem

   Beginning around 08:23 UTC on 2026-06-22 some Clari Copilot customers experienced failures across Zoom, Google Meet, and Microsoft Teams that prevented calls from being recorded. The errors were traced back to the Copilot maintenance on 2026-06-20 and configuration changes that were not fully applied. The Clari Engineering team remediated the issue by applying the configuration changes and validating the changes. Call recording functionality was restored at approximately 18:40 UTC 2026-06-22. We continued to monitor the system for the next 24 hours to ensure that there were no further issues before resolving the incident.

1. 22. juni 2026 kl. 10.39 UTCinvestigating

   Vores ingeniørhold undersøger aktivt årsagen på tværs af alle tre platforme. Vi overvåger opkald optage succesrater tæt og vil give opdateringer som vi lærer mere.

2. 22. juni 2026 kl. 11.48 UTCresolved

   Vi har bekræftet, at problemet er løst for de berørte brugere. Et resumé af hændelsen vil blive lagt inden for de næste tre amerikanske bankdage.

3. 21. juli 2026 kl. 19.05 UTCpostmortem

   Begynder omkring 08: 23 UTC på 2026- 06- 22 nogle Clari Copilot kunder oplevede fejl på tværs af Zoom, Google Meet, og Microsoft Team, der forhindrede opkald fra at blive optaget. Fejlene blev sporet tilbage til Copilot vedligeholdelse på 2026- 06- 20 og konfigurationsændringer, der ikke blev anvendt fuldt ud. ClariEngineering teamet opklarede problemet ved at anvende konfigurationsændringerne og validere ændringerne. Opkaldet optagelse funktionalitet blev genoprettet på ca. 18: 40 UTC 2026- 06- 22. Vi fortsatte med at overvåge systemet i de næste 24 timer for at sikre, at der ikke var flere problemer, før løsningen af hændelsen.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. juni 2026 kl. 00.16 UTCinvestigating

   Clari is currently experiencing longer load times and errors than normal. Our engineering team is actively investigating the issue.

2. 6. juni 2026 kl. 03.15 UTCinvestigating

   The engineering team is continuing to investigate the issue. At this time users may still be experiencing longer page load times or increased errors.

3. 6. juni 2026 kl. 04.14 UTCresolved

   We have identified and fixed a problem that was overloading database queries and resulted in slow performance throughout the application. All systems should be functioning normally again.

4. 10. juni 2026 kl. 23.23 UTCpostmortem

   At approximately 23:44 on 2026-06-05 UTC some Clari users experienced long page load times and errors when trying to use the application. The Clari Engineering team was able to determine that a database operation was continually executing and overloading one of the databases. Once the database call was stopped and the stuck connections were cleared, system performance was able to return to normal at around 04:33 on 2026-06-06 UTC.

1. 4. juni 2026 kl. 15.53 UTCinvestigating

   Some customers may be seeing problems with connectivity to Salesforce CRM Integration. Our engineering team is actively investigating.

2. 4. juni 2026 kl. 16.21 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. juni 2026 kl. 05.06 UTCmonitoring

   Update: Resolution Requires Customer Action Our engineering teams have resolved the issue and we are monitoring the fix. However, customers who continue to experience an impact must take action to fully restore functionality. Required Action: Salesforce Administrators (Role: Full System Administrator) must: * Navigate to **Workspace Settings > Integrations** in Clari Copilot. * Re-authenticate the Salesforce integration. Resolution Process: After re-authentication - Our systems will automatically re-sync your Salesforce data from the impacted window. - Full functionality will be restored within the following hours. Who Should Take Action: Customers who continue to experience Salesforce CRM connectivity issues after this update. If you encounter any issues or need assistance during the re-authentication process, please reach out to our Support Team.

4. 5. juni 2026 kl. 09.14 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. 11. juni 2026 kl. 06.45 UTCpostmortem

   Starting at approximately 15:25 on 2026-06-04 UTC, a code defect in Clari Copilot's internal integration maintenance process caused Salesforce integrations to become disconnected for a subset of customers. This impacted Salesforce data sync only. All other Copilot functionality continued to operate normally. The Clari engineering team identified the cause and rolled out a fix at 18:29 on 2026-06-04 UTC. Affected customers were provided re-authentication instructions to restore their Salesforce connection, after which full functionality resumed. No customer data was lost during this incident

1. 3. juni 2026 kl. 10.27 UTCinvestigating

   Some customers using Copilot with Google Meet are not seeing their meetings recorded. Our engineering team is actively investigating.

2. 3. juni 2026 kl. 12.07 UTCidentified

   Our engineering teams have identified the issue and are implementing a fix. Due to a recent change on Google Meet copilot bots are unable to join some of the Google Meet meetings. Team has found a fix and is working on implementing it. The next status update will be after the fix has been applied.

3. 3. juni 2026 kl. 12.47 UTCmonitoring

   Our engineering teams have resolved the issue and we are monitoring the fix.

4. 3. juni 2026 kl. 12.54 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. 6. juni 2026 kl. 10.43 UTCpostmortem

   Starting at approximately 02:00 on 2026-06-02 UTC Google began rolling out a change that was incompatible with Clari Copilot Google Meet recorder bots. This impacted a subset of customers using Google Meet preventing the bots from joining calls. Clari engineering team identified the change and rolled out a fix at 12:47 2026-06-03 UTC resolving the issue.

1. 11. maj 2026 kl. 19.05 UTCinvestigating

   The Clari Revenue platform is currently seeing an increase in errors in Inspection and Forecasting modules. Our engineering team is actively investigating the issue.

2. 11. maj 2026 kl. 19.36 UTCmonitoring

   Our engineering teams have implemented a fix which has addressed the observed errors. We are monitoring the system to confirm the issue has been resolved.

3. 11. maj 2026 kl. 20.25 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

4. 14. maj 2026 kl. 00.15 UTCpostmortem

   On 2026-05-11 at approximately 18:55 UTC, a number of Clari customers encountered errors connecting to the Salesforce integration within the Clari application. Engineers identified a configuration change that enabled a 30-day idle timeout for Salesforce refresh tokens, which caused integration user sessions to be invalidated and disconnected across multiple organizations. The setting was disabled at approximately 19:15 UTC, after which availability began recovering. Full service availability was confirmed for all affected organizations by approximately 20:52 UTC. Other areas of the Clari application were unaffected during this time.

1. 8. maj 2026 kl. 04.39 UTCmonitoring

   CRM syncing is showing a delay of a a few hours. we expect the delay to be caught up by 8:00 AM UTC

2. 8. maj 2026 kl. 09.32 UTCmonitoring

   Our engineering teams have resolved the issue and we are monitoring the fix.

3. 8. maj 2026 kl. 10.50 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

4. 14. maj 2026 kl. 19.04 UTCpostmortem

   On 2025-05-08 at approximately 02:52 UTC, customers experienced delays of several hours with RevDB CRM sync jobs due to an internal service connectivity issue impacting the workflow system responsible for processing syncs. The affected services were restored and the backlog was fully cleared. No data was lost or compromised during the incident. Additional monitoring and recovery safeguards have since been implemented to reduce the risk of recurrence.

1. 15. april 2026 kl. 15.48 UTCinvestigating

   Groove is currently experiencing intermittent performance issues, and you may notice some slowness. Our engineers are actively investigating and will share updates as soon as possible.

2. 15. april 2026 kl. 16.01 UTCmonitoring

   Our engineering teams have resolved the issue and we are monitoring the fix.

3. 15. april 2026 kl. 16.29 UTCresolved

   This incident has been resolved.

1. 9. april 2026 kl. 15.36 UTCinvestigating

   Our engineering team is actively investigating reported issues with the Analytics module.

2. 9. april 2026 kl. 16.21 UTCmonitoring

   We have identified and reverted the related change. Behavior is returning to normal and we will continue to monitor system health.

3. 9. april 2026 kl. 18.32 UTCresolved

   We have confirmed the issue has been resolved for all impacted users. A summary of the incident will be posted.

4. 10. april 2026 kl. 23.09 UTCpostmortem

   On 2026-04-09 at approximately 14:48 UTC, users were unable to load Analytics modules in the Clari application. Clari engineers quickly identified the cause and took action to restore the affected functionality. During this time, a small number of other areas of the application were also impacted as a result of the same underlying issue. Engineers performed rolling restarts of the affected Analytics services, restoring full Analytics module availability by approximately 16:21 UTC. Isolated issues in a small number of other dependent services were subsequently identified and resolved through additional targeted restarts, with all issues fully cleared by 17:52 UTC.

1. 8. april 2026 kl. 19.26 UTCinvestigating

   Our engineering team is actively investigating reports of the Forecasting tab not appearing for some customers.

2. 8. april 2026 kl. 19.54 UTCidentified

   We have identified the cause of the missing Forecasting tabs and are working to resolve.

3. 8. april 2026 kl. 20.32 UTCmonitoring

   We have restored the Forecasting tab and are monitoring to confirm that all users have access.

4. 8. april 2026 kl. 23.40 UTCresolved

   We have confirmed the issue has been resolved for all impacted users.

5. 9. april 2026 kl. 21.08 UTCpostmortem

   On 2026-04-08 at approximately 18:53 UTC, all Clari customers lost access to the Forecast tab in the Clari application. Other areas of the application were unaffected and continued to operate normally. Clari engineers quickly identified the cause as the unintended deletion of configuration data required to display the Forecast tab, and restored the affected data. During the restoration process, there was a brief period of increased latency as service capacity scaled back up to handle returning traffic. Full access to the Forecast tab was confirmed for all affected users by 23:20 UTC.

1. 27. marts 2026 kl. 07.44 UTCinvestigating

   Clari Copilot users are currently not receiving any email notifications. Our engineering team is actively investigating the issue. The issue is only limited to the Clari Copilot product.

2. 27. marts 2026 kl. 14.26 UTCinvestigating

   We are continuing to investigate the issue. Email notifications remain impacted.

3. 27. marts 2026 kl. 15.04 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

4. 30. marts 2026 kl. 07.18 UTCpostmortem

   At 14:30 UTC on March 25, 2025, Clari Copilot experienced an interruption in email notifications due to an exhausted email delivery quota. As a result, email notifications scheduled during this period were not delivered. Clari was able to increase the delivery limit and service was fully restored as of 14:55 UTC on March 27, 2025. All systems are now performing as expected and emails are being delivered.  Please note that missed notifications from the outage window cannot be retroactively delivered. At no time during this incident was user data at risk.

1. 4. marts 2026 kl. 18.43 UTCinvestigating

   We are currently investigating an issue where Clari Copilot is not recording some Zoom calls

2. 4. marts 2026 kl. 21.07 UTCinvestigating

   Some Clari Copilot calls via Zoom continue to not be recorded. Our engineering team is currently working with Zoom to resolve this issue.

3. 5. marts 2026 kl. 05.24 UTCinvestigating

   We are continuing to work with the Zoom engineering team to resolve this issue. We will provide additional details about the progress as they become available.

4. 5. marts 2026 kl. 11.57 UTCmonitoring

   Our engineering teams have resolved the issue together with the Zoom engineering team and we are monitoring the fix.

5. 5. marts 2026 kl. 15.10 UTCresolved

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

6. 9. marts 2026 kl. 23.55 UTCpostmortem

   At approximately 2026-03-04 15:00 UTC, a subset of Clari Copilot customers experienced an issue where the recording bot was unable to join Zoom meetings. This was caused by an account authentication error within the Zoom platform that prevented the bot from successfully joining calls. This was a reoccurrence of the issue that prevented Copilot from joining Zoom calls on 2026-02-11 and was caused by Zoom not fully updating the Copilot authentication across their entire platform. The Clari engineering team worked with Zoom’s Support and Development team to correctly update the authentication process platform wide and resolve the issue. An RCA from Zoom on this issue is pending. Recording functionality was fully restored and confirmed operational at 2026-03-05 11:28 UTC.

1. 11. februar 2026 kl. 00.29 UTCmonitoring

   We’re aware of an issue affecting links in some email content, and our engineering teams are actively working to resolve it as quickly as possible.

2. 11. februar 2026 kl. 02.19 UTCmonitoring

   We've spotted that something has gone wrong. We're currently working our partners to remediate the issue, and will provide an update soon.

3. 11. februar 2026 kl. 14.38 UTCmonitoring

   We’re aware of an issue affecting links in some email content,. We're actively working with our partners to remediate the issue, and will provide an update soon.

4. 11. februar 2026 kl. 14.53 UTCresolved

   The issue affecting links in some email content, has been resolved. Thank you for your patience and understanding.

5. 13. februar 2026 kl. 21.50 UTCpostmortem

   Around 2026-02-11 09:51 UTC an issue affecting links in some email content resulted in bounced or spam-foldered emails by a third party vendor \(Google\). The team has worked closely with the vendor \(Google\) and successfully remediated the situation by 2026-02-12 06:00 UTC.