- Level
- confirmed
- Worst impact
- Operational
- Components
- Uploads
What to do
Check whether you use Filestack Uploads. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 15h 27m it lasted.
Anything that failed between 2024-04-03 21:26 UTC and 2024-04-04 12:53 UTC may need a replay.Subscribe to Filestack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=filestack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Filestack 2
- investigating
Investigation: The Filestack team is investigating a 500 internal server error pertaining to file uploads with Filestack workflows.
provider
- resolved
The issue has been resolved. Thank you for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-22a37ff516
Is Filestack still down?
No, this incident was resolved 2024-04-04 12:53 UTC. For Filestack's live state, see https://down.guide/providers/filestack.
How long did it last?
15h 27m, from 2024-04-03 21:26 UTC to 2024-04-04 12:53 UTC, by the times Filestack posted.
What was affected?
Filestack named Uploads.
What caused it?
Filestack hasn't published a root cause. If it does, it shows here.
Where does this come from?
Filestack's official status page, https://status.filestack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.