Factorial Hr 장애 기록

1. 2026년 10월 27일 오전 9:55 UTCinvestigating

   몇몇 고객은 사무실 네트워크에 Windows 탁상용 컴퓨터에서 우리의 신청을 적재하는 문제점을 경험하고 있습니다. 문제는 Apple OSX 또는 Factorial 모바일 애플리케이션과 같은 다른 운영 체제에 영향을 미치지 않습니다. workaround는 모바일 핫스팟에 데스크탑 장치를 연결하는 것 같습니다. 우리는 문제를 이해하고 해결책을 제공합니다.

2. 2026년 10월 27일 오전 10:18 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 10월 27일 오후 12:55 UTCidentified

   우리는 네트워크 제공 업체, 기업 보안 조치 및 Windows 데스크톱 시스템의 매우 특정 조합에이 문제의 범위를 축소 할 수있었습니다. 우리는 Edge Network Provider와 긴급한 지원 케이스를 열어 그들이이 문제를 완화 할 수있는 모든 것이 있는지 볼 수 있습니다. 우리는 또한 FortiGate에 도달하고 있습니다. 그 사이에, 우리의 고객이 신청에 접근하기 위하여 사용할 수 있는 다른 workarounds가 있습니다: - Factorial 모바일 앱을 사용합니다. - VPN 또는 이차 파이버 공급자를 포함한 다른 네트워크 연결을 사용합니다. - 일시적으로 사무실 보안 시스템을 비활성화, FortiGate는 특히 영향을받습니다. Cloudflare에서 열린 사건 보고서 : https://www.cloudflarestatus.com/incidents/dk2obcyw2aew

4. 2026년 10월 27일 오후 3:22 UTCmonitoring

   Cloudflare는 수정을 구현하고 오류는 고객의 행동없이 해결해야합니다. 우리는 해결로 사건을 표시하기 전에 다음 시간에 확인됩니다.

5. 2026년 10월 27일 오후 3:39 UTCresolved

   우리는 사건이 해결되었습니다, 납품업자 고침 덕분에 확인할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 1일 오전 8: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. 2026년 6월 1일 오후 1:48 UTCmonitoring

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

3. 2026년 6월 1일 오후 2:14 UTCresolved

   This incident has been resolved.

1. 2026년 2월 26일 오전 9: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. 2026년 2월 26일 오후 1:12 UTCresolved

   This incident has been resolved.

1. 2026년 2월 23일 오전 10:47 UTCinvestigating

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

2. 2026년 2월 23일 오전 11:21 UTCmonitoring

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

3. 2026년 2월 24일 오후 11:33 UTCresolved

   This incident has been resolved.

1. 2026년 2월 20일 오전 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. 2026년 2월 20일 오후 1:37 UTCmonitoring

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

3. 2026년 2월 20일 오후 6: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. 2026년 2월 21일 오전 8:55 UTCresolved

   This incident has been resolved.

1. 2026년 2월 18일 오후 4: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. 2026년 2월 19일 오전 8: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. 2026년 2월 19일 오후 10:16 UTCresolved

   This incident has been resolved.

1. 2026년 2월 13일 오후 5: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. 2026년 2월 13일 오후 5:42 UTCidentified

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

3. 2026년 2월 13일 오후 5: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. 2026년 2월 12일 오후 1: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. 2026년 2월 12일 오후 2: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. 2026년 2월 12일 오후 2:56 UTCidentified

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

4. 2026년 2월 12일 오후 3: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. 2026년 1월 1일 오전 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. 2026년 1월 1일 오후 12:07 UTCidentified

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

3. 2026년 1월 2일 오전 9: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. 2026년 1월 4일 오후 4:00 UTCresolved

   This incident has been resolved.

1. 2025년 12월 5일 오전 9: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. 2025년 12월 5일 오전 9: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. 2025년 12월 5일 오전 9:23 UTCresolved

   This incident has been resolved.

1. 2025년 11월 12일 오후 4: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. 2025년 11월 12일 오후 4: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. 2025년 10월 2일 오후 2: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. 2025년 9월 23일 오전 7: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. 2025년 9월 23일 오전 7:29 UTCidentified

   The fix has been identified and is being deployed.

3. 2025년 9월 23일 오전 7:54 UTCmonitoring

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

4. 2025년 9월 23일 오전 8: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. 2025년 6월 16일 오후 4: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. 2025년 6월 17일 오후 1: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. 2025년 6월 17일 오후 1:32 UTCresolved

   This incident has been resolved.

1. 2025년 5월 23일 오후 10: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. 2025년 5월 23일 오후 11:54 UTCidentified

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

3. 2025년 5월 24일 오전 1:22 UTCmonitoring

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

4. 2025년 5월 24일 오전 2:00 UTCresolved

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

1. 2025년 5월 16일 오전 5: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. 2025년 4월 24일 오후 2: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. 2025년 4월 24일 오후 2: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. 2025년 3월 12일 오후 6: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. 2025년 2월 7일 오전 9: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. 2025년 2월 3일 오후 1: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. 2025년 2월 3일 오후 5:23 UTCmonitoring

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

3. 2025년 2월 4일 오전 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. 2025년 2월 4일 오전 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. 2025년 2월 4일 오후 12:05 UTCmonitoring

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

6. 2025년 2월 4일 오후 5: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