DK: Problemet med Synkroniserings-API’et er nu løst, og alle systemer kører som normalt.
Hvad skete der? Årsagen var forbindelsesproblemer mellem Synkroniserings-API og database, som udløste et loop, der overbelastede databasen. Fejlen er identificeret og rettet, og synkroniserings-API’et er genstartet.
Vi beklager eventuelle gener og takker for din tålmodighed. Med venlig hilsen Team 365Tid
-----------------------------------------
ENG: The issue with the Synchronization API has now been resolved, and all systems are operating normally.
What happened? The root cause was connection issues between the Synchronization API and the database, which triggered a loop that overloaded the database. The issue has been identified and resolved, and the synchronization API has been restarted.
We apologize for any inconvenience and thank you for your patience. Kind regards, Team 365Tid
Posted Feb 26, 2026 - 10:56 CET
Update
DK: Fejlen er lokaliseret til at være relateret til synkroniserings-API’et, som midlertidigt er stoppet, mens der fejlsøges yderligere. Hermed er al timeregistrering igen fuldt kørende fra både web og app.
ENG: The issue has been identified as being related to the synchronization API, which has been temporarily stopped while further troubleshooting is being carried out. All time registration is now fully operational again from both web and app.
Posted Feb 26, 2026 - 09:53 CET
Identified
DK Der opleves i øjeblikket udfordringer med timeregistreringer fra alle registreringskilder, herunder almindelig registrering, ugeregistrering samt appen. Fejlen medfører, at der sker timeouts og registreringer ikke gemmes.
Der arbejdes intensivt på at identificere årsagen og genskabe stabil drift hurtigst muligt. Vi opdaterer igen, så snart der er nyt i sagen.
ENG We are currently experiencing issues with time registrations across all registration sources, including standard registration, weekly registration, and the mobile app. The issue is causing timeouts, and registrations are not being saved.
We are working intensively to identify the root cause and restore stable operations as quickly as possible. We will provide an update as soon as more information becomes available.
Posted Feb 26, 2026 - 09:34 CET
This incident affected: 365Tid (365Tid.dk, 365tid App, 365Tid API).