- Detected by Pingoru
- Feb 26, 2026, 09:04 AM UTC
- Resolved
- Feb 26, 2026, 01:12 PM UTC
- Duration
- 4h 7m
Affected: Factorial website
Timeline · 3 updates
-
identified Feb 26, 2026, 09:04 AM UTC
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.
-
identified Feb 26, 2026, 09:05 AM UTC
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.
-
resolved Feb 26, 2026, 01:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 10:47 AM UTC
- Resolved
- Feb 24, 2026, 11:33 PM UTC
- Duration
- 1d 12h
Affected: API & backendFactorial website
Timeline · 3 updates
-
investigating Feb 23, 2026, 10:47 AM UTC
We are experiencing a performance degradation across the platform, which may result in occasional errors for some users.
-
monitoring Feb 23, 2026, 11:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 24, 2026, 11:33 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 13, 2026 - Detected by Pingoru
- Feb 13, 2026, 05:37 PM UTC
- Resolved
- Feb 13, 2026, 05:44 PM UTC
- Duration
- 6m
Affected: API & backendAuthentication system
Timeline · 3 updates
-
investigating Feb 13, 2026, 05:37 PM UTC
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.
-
identified Feb 13, 2026, 05:42 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Feb 13, 2026, 05:44 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 01, 2026, 11:42 AM UTC
- Resolved
- Jan 04, 2026, 04:00 PM UTC
- Duration
- 3d 4h
Affected: eu2.demo.factorial.dev
Timeline · 4 updates
-
investigating Jan 01, 2026, 11:42 AM UTC
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.
-
identified Jan 01, 2026, 12:07 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jan 02, 2026, 09:36 AM UTC
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.
-
resolved Jan 04, 2026, 04:00 PM UTC
This incident has been resolved.
Read the full incident report →
Critical December 5, 2025 - Detected by Pingoru
- Dec 05, 2025, 09:04 AM UTC
- Resolved
- Dec 05, 2025, 09:23 AM UTC
- Duration
- 18m
Affected: API & backendAuthentication systemeu2.demo.factorial.devFactorial websiteWebpageEdge networkCDN/Cache
Timeline · 3 updates
-
investigating Dec 05, 2025, 09:04 AM UTC
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.
-
monitoring Dec 05, 2025, 09:18 AM UTC
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.
-
resolved Dec 05, 2025, 09:23 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 04:15 PM UTC
- Resolved
- Nov 12, 2025, 04:39 PM UTC
- Duration
- 23m
Affected: API & backendFactorial website
Timeline · 2 updates
-
monitoring Nov 12, 2025, 04:15 PM UTC
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.
-
resolved Nov 12, 2025, 04:39 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 10:30 AM UTC
- Resolved
- Oct 02, 2025, 10:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 02, 2025, 02:36 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2025, 07:24 AM UTC
- Resolved
- Sep 23, 2025, 08:03 AM UTC
- Duration
- 38m
Affected: Factorial website
Timeline · 4 updates
-
identified Sep 23, 2025, 07:24 AM UTC
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.
-
identified Sep 23, 2025, 07:29 AM UTC
The fix has been identified and is being deployed.
-
monitoring Sep 23, 2025, 07:54 AM UTC
The fix has been deployed and we are seeing better performance metrics across the application.
-
resolved Sep 23, 2025, 08:03 AM UTC
The problem has been resolved. We apologize for the inconvenience this may have caused and hope you have a great day ahead!
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2025, 04:41 PM UTC
- Resolved
- Jun 17, 2025, 01:32 PM UTC
- Duration
- 20h 51m
Affected: Factorial website
Timeline · 3 updates
-
monitoring Jun 16, 2025, 04:41 PM UTC
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
-
monitoring Jun 17, 2025, 01:31 PM UTC
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.
-
resolved Jun 17, 2025, 01:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 10:00 PM UTC
- Resolved
- May 24, 2025, 02:00 AM UTC
- Duration
- 3h 59m
Affected: API & backendFactorial websiteWebpage
Timeline · 4 updates
-
investigating May 23, 2025, 10:00 PM UTC
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.
-
identified May 23, 2025, 11:54 PM UTC
The issue has been identified, and our Platform team is actively working on implementing a resolution.
-
monitoring May 24, 2025, 01:22 AM UTC
All systems are now back online. We're continuing to actively monitor the platform to ensure ongoing stability.
-
resolved May 24, 2025, 02:00 AM UTC
All systems are now fully operational. Thank you for your patience, and we apologize for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 05:30 AM UTC
- Resolved
- May 16, 2025, 04:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 16, 2025, 05:30 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2025, 02:03 PM UTC
- Resolved
- Apr 24, 2025, 02:28 PM UTC
- Duration
- 24m
Affected: API & backendFactorial website
Timeline · 2 updates
-
investigating Apr 24, 2025, 02:03 PM UTC
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.
-
resolved Apr 24, 2025, 02:28 PM UTC
We have identified the root of the problem and have deployed fixes to restore the service performance. We apologize for the inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2025, 06:13 PM UTC
- Resolved
- Mar 12, 2025, 06:13 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 12, 2025, 06:13 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 07, 2025, 09:23 AM UTC
- Resolved
- Feb 06, 2025, 11:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 07, 2025, 09:23 AM UTC
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.
Read the full incident report →
Critical February 3, 2025 - Detected by Pingoru
- Feb 03, 2025, 01:23 PM UTC
- Resolved
- Feb 04, 2025, 05:28 PM UTC
- Duration
- 1d 4h
Affected: API & backendFactorial website
Timeline · 6 updates
-
identified Feb 03, 2025, 01:23 PM UTC
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.
-
monitoring Feb 03, 2025, 05:23 PM UTC
A fix has been implemented and we are monitoring the results.
-
investigating Feb 04, 2025, 11:47 AM UTC
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.
-
identified Feb 04, 2025, 11:55 AM UTC
We have identified the source of the issue and we are applying a mitigation to restore service as soon as possible.
-
monitoring Feb 04, 2025, 12:05 PM UTC
We have restored the service, although the Reports functionality is currently unavailable.
-
resolved Feb 04, 2025, 05:28 PM UTC
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
Read the full incident report →
- Detected by Pingoru
- Jan 24, 2025, 11:41 AM UTC
- Resolved
- Jan 24, 2025, 03:43 PM UTC
- Duration
- 4h 1m
Affected: API & backendFactorial website
Timeline · 3 updates
-
investigating Jan 24, 2025, 11:41 AM UTC
As of 11:00 UTC / 12:00 CET, we have observed a significant increase in requests to our application, resulting in performance degradation. We are implementing mitigation measures to restore service quality while we keep investigating the root cause of the issue. We appreciate your patience and will provide further updates as we work to resolve this matter.
-
monitoring Jan 24, 2025, 12:37 PM UTC
Our actions have stabilized the system and the application is now performing normally. While the number of requests has greatly reduced, we keep investigating to understand the origin of the spike.
-
resolved Jan 24, 2025, 03:43 PM UTC
Traffic levels have been stable and back to the usual levels for a while.
Read the full incident report →
Critical January 18, 2025 - Detected by Pingoru
- Jan 18, 2025, 03:29 PM UTC
- Resolved
- Jan 18, 2025, 04:12 PM UTC
- Duration
- 43m
Affected: API & backend
Timeline · 3 updates
-
investigating Jan 18, 2025, 03:29 PM UTC
We are currently investigating this issue.
-
identified Jan 18, 2025, 03:31 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jan 18, 2025, 04:12 PM UTC
The lock has been cleared and the service has been restored. We will perform a more thorough investigation next week and set up the mechanisms and processes required to prevent this from happening again.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2025, 08:36 AM UTC
- Resolved
- Jan 13, 2025, 09:02 AM UTC
- Duration
- 26m
Affected: API & backendFactorial website
Timeline · 2 updates
-
identified Jan 13, 2025, 08:36 AM UTC
Some users are experiencing sporadic errors loading or moving around different features of the application. We have identified the potential root cause of the issue and have deployed a solution that should solve these errors.
-
resolved Jan 13, 2025, 09:02 AM UTC
The fix deployed in the previous hour has resolved the issue. The application should work normally now. We keep investigating why this errors started appearing today and how they relate to a change that was published last Thursday. Apologies for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2024, 07:45 AM UTC
- Resolved
- Nov 25, 2024, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 25, 2024, 07:45 AM UTC
Due to an issue with under-provisioned capacity the Factorial web application experienced highly increased latency resulting in very long loading times from 6:00AM to 7:00AM (UTC). Apologies for the inconvenience. - The Factorial Team
Read the full incident report →
- Detected by Pingoru
- Nov 22, 2024, 08:21 PM UTC
- Resolved
- Nov 25, 2024, 03:32 PM UTC
- Duration
- 2d 19h
Affected: Webpage
Timeline · 3 updates
-
identified Nov 22, 2024, 08:21 PM UTC
There is an issue with the German domain name (factorialhr.de). The public website and customer pages using it are currently unreachable. We have identified the problem and are working on a fix. Meanwhile, users can still access the application at https://app.factorialhr.com/ We apologize for the inconvenience caused. Next update: before Monday 25th Nov. 12:00 UTC
-
identified Nov 25, 2024, 07:44 AM UTC
The issue is still ongoing, but we expect more information today when the German DNS registry resolves our open request.
-
resolved Nov 25, 2024, 03:32 PM UTC
The issue has been resolved, factorialhr.de is now serving again our website.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2024, 03:57 PM UTC
- Resolved
- Nov 18, 2024, 03:57 PM UTC
- Duration
- —
Affected: API & backend
Timeline · 1 update
-
resolved Nov 18, 2024, 03:57 PM UTC
We experienced a brief service interruption from 03:30 PM to 03:36 PM (UTC). During this time, our database experienced unresponsiveness, which impacted the availability of our service. To mitigate the issue, our team promptly killed the suspicious process to restore the database functionality instantly. All systems are now operating normally, and we'll apply preventive measures to prevent similar occurrences in the future. We appreciate your understanding and patience as we work through this process.
Read the full incident report →
- Detected by Pingoru
- Nov 15, 2024, 12:20 PM UTC
- Resolved
- Nov 15, 2024, 12:20 PM UTC
- Duration
- —
Affected: Factorial website
Timeline · 1 update
-
resolved Nov 15, 2024, 12:20 PM UTC
Since around 11:15 CET, the sidebar in the Factorial app hasn’t been visible, making it unusable. We identified the root cause but chose to quickly reduce the impact by rolling back to a previous version at 12:00 CET. Thanks for your patience, and sorry for the inconvenience! - The Factorial Team
Read the full incident report →
- Detected by Pingoru
- Nov 08, 2024, 07:55 PM UTC
- Resolved
- Nov 09, 2024, 09:48 AM UTC
- Duration
- 13h 53m
Affected: API & backendFactorial website
Timeline · 4 updates
-
investigating Nov 08, 2024, 07:55 PM UTC
We are experiencing increased latency and higher error rates since 18:55 UTC. Our team is investigating the origin of the issue. We will provide an update as soon as we have more information.
-
investigating Nov 08, 2024, 10:33 PM UTC
We are continuing to investigate this issue.
-
identified Nov 09, 2024, 12:57 AM UTC
We have identified the root cause of the issue and are currently working on a fix.
-
resolved Nov 09, 2024, 09:48 AM UTC
For now the mitigation is working and the app is working normally. We continue investigating to find a permanent fix. Update: as of 9/11 midday UTC, the root cause has been addressed. We don't expect any further side-effects of this incident. Apologies for the inconvenience, Factorial team
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2024, 08:39 AM UTC
- Resolved
- Oct 23, 2024, 12:06 PM UTC
- Duration
- 3h 26m
Affected: Factorial website
Timeline · 3 updates
-
identified Oct 23, 2024, 08:39 AM UTC
We have been experiencing slow response times, leading to the app being unusable at times. We have identified the root of the issue and are now working on a solution. We expect it to be deployed during the next 2 hours.
-
monitoring Oct 23, 2024, 10:57 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 23, 2024, 12:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2024, 12:30 PM UTC
- Resolved
- Sep 30, 2024, 03:40 PM UTC
- Duration
- 3h 10m
Affected: API & backendFactorial website
Timeline · 5 updates
-
identified Sep 30, 2024, 12:30 PM UTC
We are currently investigating reports of laggy performance affecting some customers when using our application and API. Our teams have determined that this issue is unrelated to the earlier infrastructure problem encountered today. We have identified the specific conditions that lead to this performance degradation and are actively working on a resolution. We appreciate your patience as we address this matter and will provide updates as soon as more information becomes available. Thank you for your understanding.
-
investigating Sep 30, 2024, 01:38 PM UTC
We keep seeing intermittent service interruptions. Our team is hard at work to identify and fix the root cause of the issue. Apologies for the inconvenience.
-
identified Sep 30, 2024, 01:48 PM UTC
The application has suffered a major performance degradation at 15:25 CEST, the cause of which has been identified as well and is being tackled by our Engineering team. It should be deployed in the next 1-2 hours. The fix to the earlier issue, which only happened on certain conditions, has produced the desired results.
-
monitoring Sep 30, 2024, 02:17 PM UTC
A fix has been tested and is being currently deployed to all environments.
-
resolved Sep 30, 2024, 03:40 PM UTC
We are pleased to inform you that the fix has been successfully deployed. The application is now operating at its normal performance levels. Thank you for your patience during this incident.
Read the full incident report →
