- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, Conversions
- Down Index
- 26of 100
What to do
Check whether you use Filestack API, Conversions. 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 2h 32m it lasted.
Anything that failed between 2019-07-23 17:57 UTC and 2019-07-23 20:29 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
- investigating
We are investigating increased number of errors on our CDN and Transformation engine.
provider
- monitoring
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.
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-1a0040b070
Is Filestack still down?
No, this incident was resolved 2019-07-23 20:29 UTC. For Filestack's live state, see https://down.guide/filestack.
How long did it last?
2h 32m, from 2019-07-23 17:57 UTC to 2019-07-23 20:29 UTC, by the times Filestack posted.
What was affected?
Filestack named API, Conversions.
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.