Factorial Outage History
18 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Factorial Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Problem accessing Factorial services from Windows devicesWe can confirm the incident has been resolved, thanks to the vendor fix. | 5h 44m | Resolved |
| Oct 25, 2026 | Demo environment database upgradeScheduled maintenance is currently in progress. We will provide updates as necessary. | 1h 0m | Scheduled |
| Aug 13, 2026 | Database version upgradeThe scheduled maintenance has been completed. All systems are completely operational since 21:00 UTC. We appreciate your understanding during this brief service interruption and apologize for any inconvenience it may… | 1h 0m | Scheduled |
| Jun 1, 2026 | Degraded performanceThis incident has been resolved. | 6h 0m | Resolved |
| Feb 28, 2026 | Database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 26, 2026 | Issue refreshing advanced reportsThis incident has been resolved. | 4h 7m | Resolved |
| Feb 23, 2026 | Degraded service performanceThis incident has been resolved. | 36h 46m | Resolved |
| Feb 20, 2026 | Degraded service performanceThis incident has been resolved. | 20h 57m | Resolved |
| Feb 18, 2026 | Issue refreshing advanced reportsThis incident has been resolved. | 29h 59m | Resolved |
| Feb 13, 2026 | Login service outageService 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. | 6 min | Resolved |
| Feb 12, 2026 | Login service outageService 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. | 1h 34m | Resolved |
| Feb 4, 2026 | Scheduled maintenance on February 4th - todayThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 30, 2026 | Scheduled maintenance on Friday 30thThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 11, 2026 | Scheduled maintenance on Sunday 11th JanuaryThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 1, 2026 | Demo environment unavailableThis incident has been resolved. | 76h 18m | Resolved |
| Dec 5, 2025 | Full service is unavailable: 3rd party provider issueThis incident has been resolved. | 18 min | Resolved |
| Nov 12, 2025 | Higher error rates originating in a cache instanceThe 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… | 23 min | Resolved |
| Nov 8, 2025 | Scheduled maintenance on November 8thThe scheduled maintenance has been completed. The service has been restored in app.factorialhr.com. Thank you for your patience and understanding. | 3h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Factorial incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Factorial Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Factorial acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Factorial outage in this window ran 3d 4h, against a mean recovery of 10h 41m. If you depend on Factorial in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.