Factorial Hr driftsforstyrrelser

1. 27. oktober 2026 kl. 09.55 UTCinvestigating

   Nogle kunder oplever problemer med at indlæse vores program fra Windows stationære computere på kontornetværk. Spørgsmålet er ikke påvirker andre operativsystemer som Apple OSX, eller Factorial mobile ansøgning. En workout synes at være at forbinde desktop-enheden til en mobil hotspot. Vi undersøger for at forstå problemets oprindelse og komme med en beslutning.

2. 27. oktober 2026 kl. 10.18 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 27. oktober 2026 kl. 12.55 UTCidentified

   Vi har været i stand til at indsnævre omfanget af dette problem til en meget specifik kombination af netværksudbydere, corporate sikkerhedsforanstaltninger, og Windows desktop-systemer. Vi har indledt en presserende støttesag med Edge Network Provider for at se, om der er noget, de kan gøre fra deres side for at afbøde dette problem, selv om det ikke stammer fra der. Vi rækker også ud til FortiGate. I mellemtiden er der forskellige workarounds, som vores kunder kan bruge til at få adgang til programmet: - bruge Factorial mobil app. - bruge en anden netværksforbindelse, herunder en VPN eller sekundær fiber udbyder. - deaktivere midlertidigt kontor sikkerhedssystemer, FortiGate synes særligt påvirket. http: / / www.cloudflarestatus.com / hændelser / dk2obcyw2aew

4. 27. oktober 2026 kl. 15.22 UTCmonitoring

   Cloudflare har implementeret en rettelse og fejlen skal løses uden nogen handling fra vores kunder. Vi bekræfter det i den næste time før vi markerer hændelsen som løst.

5. 27. oktober 2026 kl. 15.39 UTCresolved

   Vi kan bekræfte, at hændelsen er blevet løst, takket være sælgeren fix.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juni 2026 kl. 08.13 UTCidentified

   We are currently experiencing increased latency across some of our services. Our engineering team has identified the root cause as a background processing slowdown and is actively working on a fix to restore normal performance. We apologize for the inconvenience and will provide another update as soon as we have more information.

2. 1. juni 2026 kl. 13.48 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 1. juni 2026 kl. 14.14 UTCresolved

   This incident has been resolved.

1. 26. februar 2026 kl. 09.05 UTCidentified

   We are currently experiencing an issue affecting the Advanced Reports module, causing delays in data refresh and, in some cases, preventing reports from loading. Our team is currently applying actions to mitigate the issue.

2. 26. februar 2026 kl. 13.12 UTCresolved

   This incident has been resolved.

1. 23. februar 2026 kl. 10.47 UTCinvestigating

   We are experiencing a performance degradation across the platform, which may result in occasional errors for some users.

2. 23. februar 2026 kl. 11.21 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 24. februar 2026 kl. 23.33 UTCresolved

   This incident has been resolved.

1. 20. februar 2026 kl. 11.57 UTCidentified

   We are experiencing intermittent performance degradation across the platform, which may result in occasional errors for some users. While initial mitigation efforts provided temporary relief, we are now implementing more permanent optimizations to stabilize the system.

2. 20. februar 2026 kl. 13.37 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20. februar 2026 kl. 18.06 UTCmonitoring

   Further improvements have been implemented, and they are showing promising results, but we continue to actively monitor the performance of the platform.

4. 21. februar 2026 kl. 08.55 UTCresolved

   This incident has been resolved.

1. 18. februar 2026 kl. 16.17 UTCidentified

   We are currently experiencing an issue affecting the Advanced Reports module, causing delays in data refresh and, in some cases, preventing reports from loading.

2. 19. februar 2026 kl. 08.29 UTCmonitoring

   Our efforts have mitigated the data refresh issue in Advanced Reports. We keep tuning the platform to recover full functionality on this feature during the day.

3. 19. februar 2026 kl. 22.16 UTCresolved

   This incident has been resolved.

1. 13. februar 2026 kl. 17.37 UTCinvestigating

   We are currently investigating an authentication issue affecting Factorial login services. Our engineering team is actively working on a resolution, and we will provide further updates shortly.

2. 13. februar 2026 kl. 17.42 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 13. februar 2026 kl. 17.44 UTCresolved

   Service has been restored. We have reverted a recent deployment that caused the login issues, and users should now be able to access Factorial without interruption. Thank you for your patience.

1. 12. februar 2026 kl. 13.39 UTCinvestigating

   We are currently investigating an authentication issue affecting Factorial login services. Our engineering team is actively working on a resolution, and we will provide further updates shortly.

2. 12. februar 2026 kl. 14.14 UTCinvestigating

   We continue to investigate the origin of the issue. Meanwhile, we have decided to enable the maintenance page, so all of the application is unavailable for the time being. We are working to restore the service as soon as possible. We apologise for the inconvenience.

3. 12. februar 2026 kl. 14.56 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 12. februar 2026 kl. 15.13 UTCresolved

   Service has been restored. We have reverted a recent deployment that caused the login issues, and users should now be able to access Factorial without interruption. Thank you for your patience.

1. 1. januar 2026 kl. 11.42 UTCinvestigating

   We are currently investigating an issue affecting demos at https://eu2.demo.factorial.dev/. Due to the complexity of the underlying cause, service restoration may be delayed until Monday, Jan 5th. We are working to resolve this as quickly as possible and will provide our next update by Friday, Jan 2nd.

2. 1. januar 2026 kl. 12.07 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2. januar 2026 kl. 09.36 UTCmonitoring

   The fix is being applied, but it might still take several hours. We expect the environment to be fully available again on Monday 5th January.

4. 4. januar 2026 kl. 16.00 UTCresolved

   This incident has been resolved.

1. 5. december 2025 kl. 09.04 UTCinvestigating

   Our webpage and application is experiencing a service outage, due to a technical issue with an infrastructure provider we rely on (CloudFlare). Other web services you use might also be affected. We will contact our provider and keep offering updates during the next minutes.

2. 5. december 2025 kl. 09.18 UTCmonitoring

   Our infrastructure provider has implemented a fix and Factorial is now fully available again. We keep monitoring the situation to confirm all our users are able to access the website. Thank you for the patience.

3. 5. december 2025 kl. 09.23 UTCresolved

   This incident has been resolved.

1. 12. november 2025 kl. 16.15 UTCmonitoring

   We are seeing application and delayed background processing due to connectivity errors to a cache instance. We have already replaced the former instance with a new one, and metrics have improved, but we are seeing a remanent of errors that we are investigating.

2. 12. november 2025 kl. 16.39 UTCresolved

   The issue has been resolved. We have restarted the application instances that were causing errors, and the new cache servers are being used. We will keep monitoring the situation. We apologize for the inconvenience, although we estimate the impact to have been minor.

1. 2. oktober 2025 kl. 14.36 UTCresolved

   We had a brief 2-minute interruption (10:21-10:23 UTC) that impacted system performance. Our team has identified the issue and is actively working to prevent recurrence.

1. 23. september 2025 kl. 07.24 UTCidentified

   Our monitoring systems have detected a degradation in the application performance - some pages might take longer to render or even time out. We have identified the faulty component and are investigating a possible fix.

2. 23. september 2025 kl. 07.29 UTCidentified

   The fix has been identified and is being deployed.

3. 23. september 2025 kl. 07.54 UTCmonitoring

   The fix has been deployed and we are seeing better performance metrics across the application.

4. 23. september 2025 kl. 08.03 UTCresolved

   The problem has been resolved. We apologize for the inconvenience this may have caused and hope you have a great day ahead!

1. 16. juni 2025 kl. 16.41 UTCmonitoring

   We are currently experiencing an unexpected event that has resulted in the loss of some scheduled jobs. We are actively investigating the issue and working to restore normal operations as quickly as possible. We have identified the following impact: - Automatic Breaks: users may notice inconsistent information regarding automatic breaks. - Time Off and Expenses Reports: users may need to retrigger their time off and expenses reports to ensure accurate processing. - Other minor side-effects like missed notifications. We apologize for any inconvenience this may cause and appreciate your understanding as we work to resolve the issue. We will provide updates as more information becomes available. Thank you for your patience. Next Update: before 17/06/2025 12:00 CEST

2. 17. juni 2025 kl. 13.31 UTCmonitoring

   Monitoring Update – Issue Resolved We have successfully resolved the issue that caused the disruption to scheduled jobs. All affected systems are now operating normally. What was impacted: Automatic Breaks: Inconsistent data has been addressed. Time Off and Expenses Reports: All processing functions have been restored. We recommend re-triggering any reports from the affected period to ensure accuracy. Notifications: Missed notifications should now be working as expected. We've implemented safeguards to help prevent this type of issue from occurring again. We sincerely apologize for any inconvenience caused and appreciate your patience and understanding during this time. If you continue to experience any issues, please don't hesitate to contact our support team.

3. 17. juni 2025 kl. 13.32 UTCresolved

   This incident has been resolved.

1. 23. maj 2025 kl. 22.00 UTCinvestigating

   We are currently experiencing a major outage affecting the Factorial application and its related services. As a result, the platform is temporarily unavailable. Our engineering team is actively investigating the issue and working to restore services as quickly as possible. We will provide updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience and understanding.

2. 23. maj 2025 kl. 23.54 UTCidentified

   The issue has been identified, and our Platform team is actively working on implementing a resolution.

3. 24. maj 2025 kl. 01.22 UTCmonitoring

   All systems are now back online. We're continuing to actively monitor the platform to ensure ongoing stability.

4. 24. maj 2025 kl. 02.00 UTCresolved

   All systems are now fully operational. Thank you for your patience, and we apologize for any inconvenience caused.

1. 16. maj 2025 kl. 05.30 UTCresolved

   Today between 04:39 and 04:50 UTC there was an incident that resulted in a temporary increase in error rates. This happened during a planned test operation. Our team has promptly identified and resolved the issue, and is investigating the root cause to ensure it is not repeteated in upcoming tests. We appreciate your understanding.

1. 24. april 2025 kl. 14.03 UTCinvestigating

   We are investigating an issue where one of our cache nodes has become unresponsive, leading to a global performance degradation. We are working on restoring the service as soon as possible.

2. 24. april 2025 kl. 14.28 UTCresolved

   We have identified the root of the problem and have deployed fixes to restore the service performance. We apologize for the inconvenience caused.

1. 12. marts 2025 kl. 18.13 UTCresolved

   We experienced a temporary outage in our demo environment between 17:52 and 18:04 UTC today, following a maintenance operation. During this time, users may have encountered issues accessing the demo environment. Our team identified the root cause of the issue and quickly implemented a fix. The demo system is now fully operational. We are conducting a thorough review of the incident to prevent future occurrences.

1. 7. februar 2025 kl. 09.23 UTCresolved

   On February 6, 2025, between 12:20 and 15:09, some components of the Factorial application may have displayed incorrect avatars due to an issue in our last release. The issue was reported at 14:48, and our internal team immediately resolved it. If you’re still experiencing issues, please refresh the page in your browser. If the issue persists you can reach us via your Customer Support Portal.

1. 3. februar 2025 kl. 13.23 UTCidentified

   Our application is experiencing slower response times than usual. This will be most noticeable at peak hours like 13:00 and 14:00 UTC, when some requests could even timeout and require re-submission. We are currently working on several fixes at both the application and infrastructure layer to restore our usual quality of service. We will update this incident as soon as they are deployed. Apologies for the inconvenience.

2. 3. februar 2025 kl. 17.23 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 4. februar 2025 kl. 11.47 UTCinvestigating

   This seems an unrelated issue, but we are currently facing a major outage in the application. We are investigating and will update as soon as we have more details on the reason and the estimated time of recovery.

4. 4. februar 2025 kl. 11.55 UTCidentified

   We have identified the source of the issue and we are applying a mitigation to restore service as soon as possible.

5. 4. februar 2025 kl. 12.05 UTCmonitoring

   We have restored the service, although the Reports functionality is currently unavailable.

6. 4. februar 2025 kl. 17.28 UTCresolved

   The performance issue we started experiencing yesterday has been resolved. Please keep in mind, advanced reports are still unavailable. We will reenable them in the next 24h. Apologies for the inconvenience. Update: Reports have been reenabled on February 5th at 8:15 UTC