Laserfiche Outage History
21 incidents recorded over the last 365 days, 20 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 Laserfiche Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | [US] Some Users May Be Unable to Access Laserfiche CloudThe Cloudflare incident has been resolved. | 1h 41m | Resolved |
| Oct 15, 2026 | [US] Users May Be Unable to Access RepositoriesThis incident has been resolved. | 6 min | Resolved |
| Oct 13, 2026 | [CA] Users May Experience An Error When Using Laserfiche AI ServicesThe issue in which CA users experienced an error when using Laserfiche AI services has been resolved. We appreciate your patience while we worked to address the issue. | 1h 5m | Resolved |
| Oct 8, 2026 | [US] Users May Experience Performance Degradation when Running Business RulesThe reported performance degradation affecting US users when running business rules has been resolved. We appreciate your patience while we worked to address the issue. | 1h 58m | Resolved |
| Oct 7, 2026 | [US] Users May Experience Performance Degradation when Running Business RulesThis incident has been resolved. | 3h 2m | Resolved |
| Oct 1, 2026 | [US] Users May Experience Performance Degradation When Accessing Process Automation ApplicationsThe reported performance degradation affecting users when accessing Process Automation applications has been resolved. We appreciate your patience while we worked to address the issue. | 1h 37m | Resolved |
| Sep 21, 2026 | Process automation slownessThe issue has been resolved. | 1h 50m | Resolved |
| Sep 18, 2026 | AI-Assisted Form Fill is not functionalA fix has been deployed and the feature should work as designed. | 1h 33m | Resolved |
| Sep 4, 2026 | Process automation slownessThis incident has been resolved. | 2h 59m | Resolved |
| Sep 4, 2026 | [US] - Some customers may see an HTTP 403 error when browsing the repository using Public PortalThe issue has been resolved. | 2h 13m | Resolved |
| Sep 2, 2026 | Slow Performance for Some RepositoriesThis incident has been resolved. | 1h 2m | Resolved |
| Aug 21, 2026 | [US] - Users may experience slower performance in Workflow processingThe issue has been addressed. | 1h 9m | Resolved |
| Aug 5, 2026 | [US] - Users may experience intermittent performance issues navigating Laserfiche Cloud Process Automation sitesThe issue has been resolved. | 4h 10m | Resolved |
| Jul 27, 2026 | Forms Lookups and Workflow OutageThis incident has been resolved. | 2h 12m | Resolved |
| Jun 27, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Jun 12, 2026 | [US] - Some customers may experience degraded performance when browsing their repositoryThe issue has been resolved. | 2h 24m | Resolved |
| Apr 16, 2026 | [CA] - Business Process forms lookup rules may be slow to retrieve resultsThe issue has been resolved. | 1h 57m | Resolved |
| Apr 2, 2026 | [US] Laserfiche Cloud pages under the Home section may be unavailable for usersThe issue has been resolved. | 2h 23m | Resolved |
| Mar 5, 2026 | EU Cloud: Repository access impactedThis incident has been resolved. | 3h 34m | Resolved |
| Jan 9, 2026 | [US][CA] - Some customers may experience a delay in Workflow performanceThe issue has been resolved. | 5h 26m | Resolved |
| Dec 3, 2025 | [US] - Some users may encounter an issue starting workflowsThe issue has been resolved. | 1h 47m | Resolved |
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 Laserfiche 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 Laserfiche 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 Laserfiche 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 Laserfiche outage in this window ran 5h 26m, against a mean recovery of 2h 10m. If you depend on Laserfiche 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.