- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Filestack. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h it lasted.
Anything that failed between 2018-02-08 10:57 UTC and 2018-02-08 11:57 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
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
- resolved
All services are back to normal and we are monitoring them. We are confirming right now the DNS issue, similar to last one.
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-90bf400d60
Is Filestack still down?
No, this incident was resolved 2018-02-08 11:57 UTC. For Filestack's live state, see https://down.guide/filestack.
How long did it last?
1h, from 2018-02-08 10:57 UTC to 2018-02-08 11:57 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.