Is Filestack Down Right Now? Check if there is a current outage ongoing.

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

Filestack experienced a partial degradation with the conversion service for less than 2 hours. The issue has been resolved. 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.

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 continuing to work on a resolution for this issue. We apologize for the inconvenience.

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 investigate this issue.

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 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.

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

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

This incident has been resolved.

A fix has been implemented and we are monitoring results.

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

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

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 issue has been resolved.

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

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

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

This incident has been resolved.

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

We are continuing to work on a fix for 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 investigate this issue.

We are currently investigating this issue.

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

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

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.

The workflow 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.

This incident has been resolved.

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!

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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.

This incident has been resolved.

Latency times are improving and error rate is going down. We will continue monitoring this incident.

We are again experiencing increased error rates and increased latency on file delivery and transformations related to our infrastructure provider issues in one of their datacenters.

This incident has been resolved.

We are continuing to investigate this issue.

We are experiencing increased error rates on file delivery and transformations related to our infrastructure provider issues in one of their datacenters.

This incident has been resolved.

Our services are operational now and we continue to monitor them.

We are continuing to monitor for any further issues.

Our team is monitoring a fix for API performance as this issue is ongoing.

We are continuing to investigate this issue.

Engineers are investigating degraded performance of our API related to infrastructure provider issues.

The issue has been identified and after monitoring the performance it has been resolved.

We are currently investigating this issue.

This incident has been resolved.

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

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

We are currently investigating this issue.

Our team has found the root cause related to the Filestack Picker GUI- our engineers have deployed a fix which has resolved the issue.

We are continuing to investigate this issue.

Our team is investigating issues with assets rendering/loading within the Filepicker UI. We will update you as soon as we know more.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented. Only FII users should experience the issue.

This incident has been resolved.

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

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating the issue with our CDN services

After monitoring the fix put in place, our team can confirm that all video conversions have returned to normal operating capacity.

Our team is monitoring a fix put in place to help deal with the issue being seen with active video conversions. Once we have further information we will update this page.

We are experiencing an increased error rate from video transformations. Our engineers are investigating.

AWS engineers confirmed that their fix was fully rolled out in all affected availability zones. We have been closely monitoring our services for last couple hours and can confirm everything is back to normal. We have rerouted traffic back to our regular load balancers at AWS and will monitor them further.

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

Uploads traffic in US-EAST-1 is back to normal. AWS is rolling out their fix to load balancers in affected zones. We continue serving traffic through our backup load balancers until we confirm that the fix is in place.

US-EAST-1 uploads traffic was rerouted through our API servers in other regions. AWS confirmed that they have implemented fix and are deploying it to affected load balancers.

AWS confirmed issue with their load balancers (https://status.aws.amazon.com/) that we are monitoring closely. In the meantime we have provisioned emergency load balancers cluster and directed CDN traffic through it. Delivery and transformations should be back to normal, however uploads are still affected.

We are continuing to investigate network issues. We will be updating this page with more details as we have them.

Our team is investigating an issue regarding abnormal traffic to the CDN. Once we have further information we will be updating the status of this incident.

This incident has been resolved.

Infrastructure scaled out automatically for sudden increase in traffic coming in and performance is back to normal. Engineers are monitoring closely.

We are continuing to investigate this issue.

Filestack engineers detected performance issues in our delivery and file conversion systems.

Filestack Engineers detected performance issue with one of the REST API clusters affecting 10% incoming traffic from approximately 2021-01-22 14:00 UTC to 2021-01-23 20:00 UTC. CDN delivery, transformation and V3 uploads were not affected. The issue has been resolved and we are monitoring performance closely.

This incident has been resolved.

Our team has implemented a temporary solution for the routing in regards to the systems impacted by the larger outage shown here: https://status.aws.amazon.com/ We will continue to monitor as the situation develops and update this page as soon as the issue is resolved.

Our team is investigating reports of issues with the PDF preview page endpoint. This appears to be related to the outage within Amazon's infrastructure, found here: https://status.aws.amazon.com/ Once we have more information on the issue our team will update this status.

We are seeing decreased error rates, as well as the network traffic stablizing from the Amazon resolution, here: https://status.aws.amazon.com/

Our team has made adjustments to our infrastructure and are continuing to monitor the situation as it evolves. We will provide another update as soon as we are able to resolve the traffic issue seen.

We have identified the issue reported as being connected to a larger Amazon outage impacting our infrastructure, detailed here: https://status.aws.amazon.com/ Our team is working to find ways to alleviate the issue being seen. We will update this incident report as soon as we have more details.

We are experiencing network issues that are affecting our API. Engineers are investigating. We will update this incident as soon as we have more details.

This incident has been resolved.

A fix has been implemented by Engineers and they are monitoring the service.

Engineers are investigating increased number of errors and latency in our v2 uploads and metadata API.

This incident has been resolved. Infrastructure scaled out to handle increased load. We are monitoring.

We are currently experiencing increased latency and error rates from Transformations and Delivery API. Engineering team is investigating.

This incident is resolved and performance is back to normal. Engineers are monitoring.

We are experiencing increased error rates on our CDN. Engineers are investigating.

Latency is back to normal. Engineers are monitoring closely.

We are currently experiencing increased latency and error rates on CDN delivery and transformations. We are investigating and infrastructure is scaling out to handle increased traffic.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating connectivity issues to our Video Processing API.

This incident has been resolved.

CDN connectivity is back to normal and we are monitoring it closely.

We are experiencing increased error rate from CDN. Our engineers are investigating.

This incident has been resolved.

We have identified the root cause of the issues and put solution in place. Engineers are currently monitoring this system closely.

We are experiencing issues with document conversion engine. Engineers are investigating.

This incident has been resolved.

We are experiencing increased video conversion error rate. We are working with our vendor to resolve.

This incident has been resolved.

Our transformation cluster experienced much higher load than usual and needed some time to scale up to desired capacity. During that time some customers could have experience increased number of errors from our CDN. Cluster is back to normal and engineers are monitoring.

We are investigating increased number of errors on our CDN and Transformation engine.

All services are back to normal and we are monitoring them. We are confirming right now the DNS issue, similar to last one.

We are experiencing network issues that are affecting our API. Engineers are investigating. We will update this incident as soon as we have more details.

This incident has been resolved.

All services are back to normal and we are monitoring them. Most probable cause we are confirming right now was DNS issue.

We are experiencing network issues that are affecting our API. Engineers are investigating. We will update this incident as soon as we have more details.

Support issues with Zendesk resolved.

Our support system utilizes Zendesk which is experiencing an outage. For urgent issues please use our chat features. For all others, we will monitor emails to support@filestack.com and answer as quickly as possible.

We have identified and resolved the issue with the Instagram API.

We're currently investigating issues with the Instagram integration that affect customers with videos on their accounts.

All systems are operational.

We are currently experiencing issues due to an outage with Amazon. Cached files will not be impacted.

Our Engineers are investigating an API issue. More details as soon as possible.

One of our partners experienced issues with database cluster, which caused problems with video conversions. Their engineering team identified the problem and fix was applied. All services are fully operational.

A server outage impacted connections to cloud sources for approximately 10 minutes starting at 9:10 CST. The issue has been resolved and all systems are operational

The issue between Filestack IOS SDK and Dropbox has been resolved. Please update to CocoaPod FSPicker (1.1.4) to resolve this within your application. Contact support@filestack.com if you have any questions.

We have identified an issue with the Filestack IOS SDK communicating with Dropbox. We are working to resolve the issue

Engineers solved issue with CDN access to some files hosted in Dropbox, Rackspace and files that were linked from Picker sources. This issue was caused by version mismatch of the VCL configuration between number of our CDN services that led to invalid domain resolution on origin servers. Many thanks for your patience during this incident.

The issue is solved, proper headers are send.

We experienced an issue related to CORS headers. Some requests didn't return proper header list.

We have rolled back changes that were implemented to route some Filepicker traffic through our Filestack infrastructure. The issue stemmed from instances where the dialog was being rendered by new Filestack servers, but the upload requests were going to old Filepicker API servers. With these changes rolled back, implementations that were effected should be working normally once more.

We are currently receiving increased reports of upload errors. We are investigating and will update the status as we know more.

Both old TLS versions (v1 and v1.1) are supported again.

We are working with our CDN partner Fastly to resolve issues related to TLSv1 and TLSv1.1

The issue affecting AWS US-EAST-1 appears to have been resolved and Filestack services have returned to normal.

We've identified the issue as high error rates with S3 in US-EAST-1, which is also impacting applications and services dependent on S3. We are actively working on remediating the issue.

Engineers have detected an issue with AWS services and are investigating.

One of our load balancers unexpectedly failed in the AWS North Virginia region and we have replaced it. While it was down, and while being replaced, some requests were failing because they were still being directed to the failed load balancer. We are adding additional back up load balancers and API servers to better manage future traffic.

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

We are currently experiencing an increased number of errors with our API. We are investigating and will update this status as we work through the issue.