Subscribe to UpdatesSubscribe
Get email notifications whenever 365Tid Driftsstatus creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Visit our support site.
All Systems Operational
About This Site
Velkommen til vores driftstatusside!
Her kan I få opdateringer om den aktuelle status for 365Tid-løsningen, holde jer informeret om eventuelle driftsforstyrrelser, og se planlagte tidspunkter for kommende opdateringer og forbedringer.
Uptime over the past 90 days. View historical uptime.
365Tid
Operational
90 days ago
99.98
% uptime
Today
365Tid.dk
Operational
90 days ago
100.0
% uptime
Today
365tid App
Operational
90 days ago
100.0
% uptime
Today
365Tid API
Operational
90 days ago
99.94
% uptime
Today
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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Mar 10, 2026
No incidents reported today.
Mar 9, 2026
No incidents reported.
Mar 8, 2026
No incidents reported.
Mar 7, 2026
No incidents reported.
Mar 6, 2026
No incidents reported.
Mar 5, 2026
No incidents reported.
Mar 4, 2026
No incidents reported.
Mar 3, 2026
No incidents reported.
Mar 2, 2026
No incidents reported.
Mar 1, 2026
No incidents reported.
Feb 28, 2026
No incidents reported.
Feb 27, 2026
Resolved -
This incident has been resolved.
Feb 27, 13:12 CET
Feb 27, 13:12 CET
Monitoring -
API’et, som sender data til Business Central, er nu oppe igen med nye forbedringer og optimeringer.
Vi overvåger fortsat løsningen tæt for at sikre stabil drift.
----------------------------------
The API responsible for sending data to Business Central is now back online with new improvements and optimizations.
We continue to monitor the solution closely to ensure stable operations.
Feb 27, 09:41 CET
Vi overvåger fortsat løsningen tæt for at sikre stabil drift.
----------------------------------
The API responsible for sending data to Business Central is now back online with new improvements and optimizations.
We continue to monitor the solution closely to ensure stable operations.
Feb 27, 09:41 CET
Identified -
DK:
Synkroniserings-API’et er desværre ustabilt igen og er derfor midlertidigt taget ned.
Timeregistrering fungerer fortsat som normalt. Timer vil dog ikke blive sendt til ERP, mens vi arbejder på at løse problemet.
Vi beklager generne og opdaterer løbende.
ENG:
The synchronization API is unfortunately unstable again and has been temporarily taken offline.
Time registration is still working as normal. However, hours will not be sent to the ERP system while we are resolving the issue.
We apologize for the inconvenience and will provide ongoing updates.
Feb 27, 09:35 CET
Synkroniserings-API’et er desværre ustabilt igen og er derfor midlertidigt taget ned.
Timeregistrering fungerer fortsat som normalt. Timer vil dog ikke blive sendt til ERP, mens vi arbejder på at løse problemet.
Vi beklager generne og opdaterer løbende.
ENG:
The synchronization API is unfortunately unstable again and has been temporarily taken offline.
Time registration is still working as normal. However, hours will not be sent to the ERP system while we are resolving the issue.
We apologize for the inconvenience and will provide ongoing updates.
Feb 27, 09:35 CET
Monitoring -
DK:
Der er tilføjet et fix til API’et, så det igen kører stabilt.
Synkroniserings-API’et er nu oppe igen, og vi afmelder hændelsen, men fortsætter med at overvåge for eventuelle nye uhensigtsmæssigheder.
ENG:
A fix has been implemented in the API, and it is now running stably again.
The synchronization API is back online, and we are closing the incident while continuing to monitor for any further irregularities.
Feb 26, 15:27 CET
Der er tilføjet et fix til API’et, så det igen kører stabilt.
Synkroniserings-API’et er nu oppe igen, og vi afmelder hændelsen, men fortsætter med at overvåge for eventuelle nye uhensigtsmæssigheder.
ENG:
A fix has been implemented in the API, and it is now running stably again.
The synchronization API is back online, and we are closing the incident while continuing to monitor for any further irregularities.
Feb 26, 15:27 CET
Investigating -
DK:
Problemet med synkroniserings-API’et er desværre opstået igen. API’et er taget ned for yderligere undersøgelser.
Al synkronisering er midlertidigt stoppet i begge retninger. Det betyder, at:
- Timer registreret i 365Tid ikke bliver sendt til Business Central.
- Stamdata og øvrige opdateringer fra Business Central ikke bliver overført til 365Tid.
Timeregistrering kan fortsætte som normalt i 365Tid, men der vil ikke ske nogen dataudveksling mellem systemerne, så længe API’et er lukket.
Vi arbejder på at identificere årsagen og opdaterer løbende, så snart der er nyt.
ENG:
The issue with the synchronization API has unfortunately occurred again. The API has been taken offline for further investigation.
All synchronization has been temporarily stopped in both directions. This means that:
- Hours registered in 365Tid will not be sent to Business Central.
- Master data and other updates from Business Central will not be transferred to 365Tid.
Time registration can continue as normal in 365Tid, but no data exchange between the systems will take place while the API remains offline.
We are working to identify the root cause and will provide continuous updates as soon as more information becomes available.
Feb 26, 12:49 CET
Problemet med synkroniserings-API’et er desværre opstået igen. API’et er taget ned for yderligere undersøgelser.
Al synkronisering er midlertidigt stoppet i begge retninger. Det betyder, at:
- Timer registreret i 365Tid ikke bliver sendt til Business Central.
- Stamdata og øvrige opdateringer fra Business Central ikke bliver overført til 365Tid.
Timeregistrering kan fortsætte som normalt i 365Tid, men der vil ikke ske nogen dataudveksling mellem systemerne, så længe API’et er lukket.
Vi arbejder på at identificere årsagen og opdaterer løbende, så snart der er nyt.
ENG:
The issue with the synchronization API has unfortunately occurred again. The API has been taken offline for further investigation.
All synchronization has been temporarily stopped in both directions. This means that:
- Hours registered in 365Tid will not be sent to Business Central.
- Master data and other updates from Business Central will not be transferred to 365Tid.
Time registration can continue as normal in 365Tid, but no data exchange between the systems will take place while the API remains offline.
We are working to identify the root cause and will provide continuous updates as soon as more information becomes available.
Feb 26, 12:49 CET
Feb 26, 2026
Resolved -
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
Feb 26, 10:56 CET
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
Feb 26, 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.
Feb 26, 09:53 CET
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.
Feb 26, 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.
Feb 26, 09:34 CET
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.
Feb 26, 09:34 CET
Feb 25, 2026
Completed -
The scheduled maintenance has been completed.
Feb 25, 12:09 CET
Feb 25, 12:09 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 25, 12:00 CET
Feb 25, 12:00 CET
Scheduled -
DANSK:
Tidspunkt: I dag kl. 12:00–12:15
Varighed: Op til 15 minutter
Vi foretager en teknisk opdatering af systemets database for at forbedre ydeevne og stabilitet.
I perioden kan systemet være kortvarigt utilgængeligt, og der kan forekomme langsommere svartider eller midlertidige afbrydelser.
Vi forventer, at arbejdet er afsluttet senest kl. 12:15, og vi opdaterer status her, så snart vedligeholdelsen er gennemført.
Tak for jeres forståelse.
ENGLISH:
We are performing a Hotfix update of 365Tid, which will update the system to version [VERSION].
Time: Today from 12:00–12:15
Duration: Up to 15 minutes
We will be performing a technical update to our database to improve system performance and stability.
During this period, the system may experience temporary unavailability or slower response times.
We expect the maintenance to be completed no later than 12:15 and will update the status here as soon as the work is finished.
Thank you for your understanding.
Med venlig hilsen/Best regards
Team 365Tid
Feb 25, 10:11 CET
Tidspunkt: I dag kl. 12:00–12:15
Varighed: Op til 15 minutter
Vi foretager en teknisk opdatering af systemets database for at forbedre ydeevne og stabilitet.
I perioden kan systemet være kortvarigt utilgængeligt, og der kan forekomme langsommere svartider eller midlertidige afbrydelser.
Vi forventer, at arbejdet er afsluttet senest kl. 12:15, og vi opdaterer status her, så snart vedligeholdelsen er gennemført.
Tak for jeres forståelse.
ENGLISH:
We are performing a Hotfix update of 365Tid, which will update the system to version [VERSION].
Time: Today from 12:00–12:15
Duration: Up to 15 minutes
We will be performing a technical update to our database to improve system performance and stability.
During this period, the system may experience temporary unavailability or slower response times.
We expect the maintenance to be completed no later than 12:15 and will update the status here as soon as the work is finished.
Thank you for your understanding.
Med venlig hilsen/Best regards
Team 365Tid
Feb 25, 10:11 CET
Feb 24, 2026
Completed -
The scheduled maintenance has been completed.
Feb 24, 21:00 CET
Feb 24, 21:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 24, 17:00 CET
Feb 24, 17:00 CET
Scheduled -
DANSK:
Vi udfører en planlagt opdatering af 365Tid, hvor systemet opdateres til version 1.20.
Dato og tidspunkt
📅 24. februar
🕕 17:00 – 21:00
I opdateringsperioden vil systemet være helt eller delvist utilgængeligt, mens vi opdaterer systemfiler og database. Mod slutningen af tidsrummet kan systemet være tilgængeligt igen, men der kan forekomme korte afbrydelser.
Efter opdateringen forventes systemet at være fuldt tilgængeligt og fungere normalt.
Læs mere om opdateringen på vores blog:
https://elbekvejrup.atlassian.net/wiki/x/AYBKD
ENGLISH:
We are performing a planned update of 365Tid, upgrading the system to version 1.20.
Date and time
📅 24 February
🕕 17:00 – 21:00
During the update window, the system may be partially or fully unavailable while system files and the database are being updated. Towards the end of the window, the system may become available again, though short interruptions may still occur.
After the update, the system is expected to be fully available and operating normally.
Read more about the update on our blog:
https://elbekvejrup.atlassian.net/wiki/x/AYBKD
Med venlig hilsen/Best regards
Team 365Tid
Jan 21, 09:20 CET
Vi udfører en planlagt opdatering af 365Tid, hvor systemet opdateres til version 1.20.
Dato og tidspunkt
📅 24. februar
🕕 17:00 – 21:00
I opdateringsperioden vil systemet være helt eller delvist utilgængeligt, mens vi opdaterer systemfiler og database. Mod slutningen af tidsrummet kan systemet være tilgængeligt igen, men der kan forekomme korte afbrydelser.
Efter opdateringen forventes systemet at være fuldt tilgængeligt og fungere normalt.
Læs mere om opdateringen på vores blog:
https://elbekvejrup.atlassian.net/wiki/x/AYBKD
ENGLISH:
We are performing a planned update of 365Tid, upgrading the system to version 1.20.
Date and time
📅 24 February
🕕 17:00 – 21:00
During the update window, the system may be partially or fully unavailable while system files and the database are being updated. Towards the end of the window, the system may become available again, though short interruptions may still occur.
After the update, the system is expected to be fully available and operating normally.
Read more about the update on our blog:
https://elbekvejrup.atlassian.net/wiki/x/AYBKD
Med venlig hilsen/Best regards
Team 365Tid
Jan 21, 09:20 CET