Factorial Hr 中断历史

1. 2026年10月27日 UTC 09:55investigating

   一些客户在办公室网络上从Windows台式计算机装入我们的应用程序方面遇到了问题。 这个问题并不影响Apple OSX等其它操作系统,也不影响Factorial移动应用程序. 桌面设备似乎正在连接到移动热点。 我们正在调查,以了解问题的根源,并提出解决办法.

2. 2026年10月27日 UTC 10:18investigating

   我们正在继续调查这一问题.

3. 2026年10月27日 UTC 12:55identified

   我们把这个问题的范围缩小到网络供应商、公司安全措施和Windows桌面系统等非常具体的组合。 我们已经与边际网络提供商开始一个紧急支助案件,看看他们是否能够从自己方面做任何事情来缓解这个问题,即使这个问题并非源于那里。 我们还在联络福蒂盖特。 同时,我们的客户可以使用不同的工作方式访问应用程序: - 使用“因素”移动应用程序。 - 使用不同的网络连接,包括VPN或二级纤维提供商。 - 暂时关闭办公室安全系统,FortiGate似乎特别受到影响。 Cloudflare的公开事件报告:https://www.cloudflarestatus.com/incidents/dk2obcyw2aew

4. 2026年10月27日 UTC 15:22monitoring

   Cloudflare 已经执行一个固定, 错误应该解决 而无需我们的客户采取任何行动。 我们将在下一个小时内确认,然后将事件定为已解决.

5. 2026年10月27日 UTC 15:39resolved

   我们可以确认事件已经解决了, 感谢供应商的修复.

自动翻译自官方事件更新。

1. 2026年6月1日 UTC 08:13identified

   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日 UTC 13:48monitoring

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

3. 2026年6月1日 UTC 14:14resolved

   This incident has been resolved.

1. 2026年2月26日 UTC 09:05identified

   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日 UTC 13:12resolved

   This incident has been resolved.

1. 2026年2月23日 UTC 10:47investigating

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

2. 2026年2月23日 UTC 11:21monitoring

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

3. 2026年2月24日 UTC 23:33resolved

   This incident has been resolved.

1. 2026年2月20日 UTC 11:57identified

   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日 UTC 13:37monitoring

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

3. 2026年2月20日 UTC 18:06monitoring

   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日 UTC 08:55resolved

   This incident has been resolved.

1. 2026年2月18日 UTC 16:17identified

   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日 UTC 08:29monitoring

   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日 UTC 22:16resolved

   This incident has been resolved.

1. 2026年2月13日 UTC 17:37investigating

   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日 UTC 17:42identified

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

3. 2026年2月13日 UTC 17:44resolved

   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日 UTC 13:39investigating

   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日 UTC 14:14investigating

   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日 UTC 14:56identified

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

4. 2026年2月12日 UTC 15:13resolved

   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日 UTC 11:42investigating

   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日 UTC 12:07identified

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

3. 2026年1月2日 UTC 09:36monitoring

   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日 UTC 16:00resolved

   This incident has been resolved.

1. 2025年12月5日 UTC 09:04investigating

   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日 UTC 09:18monitoring

   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日 UTC 09:23resolved

   This incident has been resolved.

1. 2025年11月12日 UTC 16:15monitoring

   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日 UTC 16:39resolved

   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日 UTC 14:36resolved

   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日 UTC 07:24identified

   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日 UTC 07:29identified

   The fix has been identified and is being deployed.

3. 2025年9月23日 UTC 07:54monitoring

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

4. 2025年9月23日 UTC 08:03resolved

   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日 UTC 16:41monitoring

   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日 UTC 13:31monitoring

   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日 UTC 13:32resolved

   This incident has been resolved.

1. 2025年5月23日 UTC 22:00investigating

   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日 UTC 23:54identified

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

3. 2025年5月24日 UTC 01:22monitoring

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

4. 2025年5月24日 UTC 02:00resolved

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

1. 2025年5月16日 UTC 05:30resolved

   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日 UTC 14:03investigating

   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日 UTC 14:28resolved

   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日 UTC 18:13resolved

   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日 UTC 09:23resolved

   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日 UTC 13:23identified

   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日 UTC 17:23monitoring

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

3. 2025年2月4日 UTC 11:47investigating

   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日 UTC 11:55identified

   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日 UTC 12:05monitoring

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

6. 2025年2月4日 UTC 17:28resolved

   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