- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Filestack. 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 3h 18m it lasted.
Anything that failed between 2018-02-07 15:33 UTC and 2018-02-07 18:52 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 3
- identified
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.
provider
- monitoring
All services are back to normal and we are monitoring them. Most probable cause we are confirming right now was DNS issue.
provider
- resolved
This incident has been resolved.
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-331a6dd253
Is Filestack still down?
No, this incident was resolved 2018-02-07 18:52 UTC. For Filestack's live state, see https://down.guide/providers/filestack.
How long did it last?
3h 18m, from 2018-02-07 15:33 UTC to 2018-02-07 18:52 UTC, by the times Filestack posted.
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.