Failed workflow calls
Timeline · 1 update
- resolved Oct 06, 2026, 06:42 PM UTC
Workflows, such as virus scans, etc. This resulted in workflow processes becoming hung and then failing. Status checks also failed. - ISSUE RESOLVED 15:11:32 UTC
Filestack had 12 outages in the last 2 years totaling 178h 52m of downtime — averaging 0.5 incidents per month.
There were 12 Filestack outages since November 8, 2024 totaling 178h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
Workflows, such as virus scans, etc. This resulted in workflow processes becoming hung and then failing. Status checks also failed. - ISSUE RESOLVED 15:11:32 UTC
We are currently investigating this issue.
We continue to research this issue. As a temporary solution, we recommend using the 4.x.x picker versions.
This incident has been resolved.
We have identified an issue affecting the Filestack Antivirus service. Users may experience intermittent errors and increased response times when processing workflow requests for virus detection. Our engineering team is actively working to resolve the issue and restore normal performance. Updates will be provided as more information becomes available
The issue with the degradation of the Virus scan has been resolved. All queued items have been processed, and the service performance is now back to normal.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some may experience high CPU utilization when using the Digital Asset Manager in the Filestack Dev Portal. The issue has been identified and our teams are working to release a fix as soon as possible.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Filestack experienced a partial degradation with the conversion service for less than 2 hours. The issue has been resolved. We apologize for the inconvenience.
Some customers have reported SSL related errors on cdn.filestackcontent.com. At this time, the issue appears to be regional. We are urgently investigating and will follow up as soon as more information is available.
We are continuing to investigate this issue.
The issue has been identified and our teams are working urgently to correct it. CDN service continues to be degraded for some customers. As a temporary workaround, you may use cdn.filepicker.io instead of cdn.filestackcontent.com. We apologize for the inconvenience.
We are continuing to work on a resolution for this issue. We apologize for the inconvenience.
A limited number of customers have been impacted by a misclassification of the Filestack domain by a phishing information provider. Filestack has not in fact been impacted by any phishing scheme and this misclassification is in error. We are actively working to remove Filestack from this list. Until that is done, certain services may be impacted for certain customers. Although our efforts to correct the issue will eventually propagate out, you may achieve a faster solution by contacting your ISP or security application provider to request that https://cdn.filestackcontent.com be unblocked. As soon as we confirm that the Filestack domain has been removed from the reporting services' list, we will inform you. Thank you for your patience. We apologize for the inconvenience.
We are in contact with the few customers who are still experiencing this issue and working with them directly on a resolution. At this time, over 99.9% of customers are NOT affected. As always, we are committed to our customer’s success with Filestack. Please don't hesitate to reach out to Filestack Technical Support if we can help in any way.
We are aware of an issue with Filestack Webhooks. Our Development Team is making every effort to resolve the issue as quickly as possible. We apologize for the inconvenience and appreciate your patience.