- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Framer. 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 22m it lasted.
Anything that failed between 2026-02-10 20:50 UTC and 2026-02-10 22:12 UTC may need a replay.Subscribe to Framer's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=framer works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Framer 4
- update
We’re investigating issues with the framerusercontent.com DNS records not resolving as expected.
provider
- update
framerusercontent.com is experiencing DNS issues due to an underlying issue at AWS. The issue is under active investigation.
provider
- update
While AWS is working on the issue (see https://status.aws.amazon.com/), we have mitigated most of the issue to moving to static DNS records. We’re still seeing some DNS “flapping”, but for most people sites and the app should work as before.
provider
- resolved
We’re seeing full recovery and removed our mitigation. We’re monitoring the AWS reports until they also report a full recovery.
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-274066bd43
Is Framer still down?
No, this incident was resolved 2026-02-10 22:12 UTC. For Framer's live state, see https://down.guide/framer.
How long did it last?
1h 22m, from 2026-02-10 20:50 UTC to 2026-02-10 22:12 UTC, by the times Framer posted.
What caused it?
Framer hasn't published a root cause. If it does, it shows here.
Where does this come from?
Framer's official status page, https://www.framerstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.