Cronologia delle interruzioni di Filepicker

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.

Investigation: The Filestack team is investigating a 500 internal server error pertaining to file uploads with Filestack workflows.

The issue has been resolved. Thank you for your patience.

Filestack is aware that customers may find that Storage is blank when reviewing the Dev Portal Dashboard. This is in error, all assets are in storage and no action is required. The Filestack team is actively investigating the cause and will implement a fix as soon as possible. We will post an update as soon as possible.

A fix has been implemented and we are monitoring results.

This incident has been resolved.

We are aware of issues impacting customers with 500 errors and general Filestack access and are actively working on a solution.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

This issue has been identified and a fix is in process. We will update with an ETA as soon as possible. We apologize for the inconvenience.

This incident has been resolved.

We have identified the issue and anticipate resolution in less than 24 hours.

We continue with efforts to implement the solution. We apologize for the inconvenience.

Uploads from Facebook have been restored. We continue to implement the solution to restore Instagram uploads.

This issue has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified. Please note that this issue only affects attempts to upload from a Facebook source.

We are continuing to work on a fix for this issue.

This incident has been resolved.

We’re experiencing an intermittent service outage with Filestack. Our team is currently working to resolve the issue. We apologize for any inconvenience. Next update in 1 hour.

A fix has been implemented. We expect to return to normal performance within the next 30 minutes.

The service outage has been resolved. Thank you for your patience.

We're experiencing a service outage with the workflows feature. Our team is currently working to resolve the issue. We apologize for any inconvenience.

The workflow service outage has been resolved. Thank you for your patience.

We’re experiencing an intermittent service outage with Filestack. Our team is currently working to resolve the issue. We apologize for any inconvenience. Next update in 1 hour.

We are continuing to investigate this issue.

The root cause of the issue has been identified. We are now testing solutions.

We've resolved the issue, and all impacted customers should now be able to use Filestack. Thanks for bearing with us and we apologize for the disruption to your work day!

This incident has been resolved.