Factorial HR Outage History

Factorial HR had 7 outages in the last 2 years totaling 124h 2m of downtime — averaging 0.3 incidents per month.

There were 7 Factorial HR outages since November 12, 2025 totaling 124h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.factorialhr.com

Minor June 1, 2026

Degraded performance

Detected by Pingoru: Jun 01, 2026, 08:13 AM UTC
Resolved: Jun 01, 2026, 02:14 PM UTC
Duration: 6h

Affected: API & backendFactorial website

Timeline · 3 updates

identified Jun 01, 2026, 08:13 AM UTC

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.
monitoring Jun 01, 2026, 01:48 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Jun 01, 2026, 02:14 PM UTC

This incident has been resolved.

Read the full incident report →

Minor February 26, 2026

Issue refreshing advanced reports

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 →

Minor February 23, 2026

Degraded service performance

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

Login service outage

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 →

Major January 1, 2026

Demo environment unavailable

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

Full service is unavailable: 3rd party provider issue

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 →

Minor November 12, 2025

Higher error rates originating in a cache instance

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 →