15 recorded Framer incidents since September 2025, with official updates, affected components, duration and resolution information.
Editor is currently unavailable. We're investigating the issue and working on the fix.
The incident is resolved and editor is available again. We're monitoring and further investigating
We’re investigating an issue causing some AI requests to fail or take longer than usual. Agent chats may show errors or respond more slowly.
AI requests are responding normally again. We’re continuing to monitor the service and investigate the cause.
Due to an outage in our third party service provider for data collection, Analytics will not work as expected for Framer Sites. We are investigating if anything can be done.
The cause of the issue was identified and the usage of Analytics is restored
We're experiencing an issue collecting usage data, so AI limits may be applied inconsistently, and your usage graph may not reflect current activity. Some analytics data starting at 18h30 CEST may also be temporarily unavailable. We're working on a fix and will keep this page updated.
Data collection is back to normal. Some usage and analytics data from 18h30–21h30 CEST is still missing and your usage graph may show a gap for that period. We're working on recovering it and will update here once it's done.
The usage and analytics data that was missing from 18h30–21h30 CEST on June 22 has now been fully recovered, so your usage graph should no longer show a gap for that period. Everything is back to normal, and this incident is resolved. Thanks for your patience.
API went down
API recovered
Some AI features are degraded due to issues with a downstream provider. Agent chats might respond a bit slower and translations are currently unavailable. We’re working on a mitigation.
The issue has been fixed at our downstream provider and all AI features are fully working again.
Usage of the Framer app will be interrupted for 5-10 minutes as we perform upgrades to our databases.
One of our font providers, fontshare.com, is experiencing an outage. Some fonts might be temporarily unavailable.
Fontshare fonts have resolved the issue
We’ve disabled forms on free projects while we investigate the current incident. On free projects the existing forms can’t be updated, new forms can’t be added and submissions to existing forms will fail silently, meaning the submissions will be lost. We apologize for the inconvenience.
We have resolved the incident and made forms available on free project plans again. Forms on free plans are currently restricted to one recipient for email destinations.
We’re investigating issues with the framerusercontent.com DNS records not resolving as expected.
framerusercontent.com is experiencing DNS issues due to an underlying issue at AWS. The issue is under active investigation.
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.
We’re seeing full recovery and removed our mitigation. We’re monitoring the AWS reports until they also report a full recovery.
We're going to be restarting some backend services a couple of times. During this time the editor may become unavailable. Hosted sites are not affected.
The database upgrade completed successfully.
We're experiencing higher latencies and response times in the editor.
We’re experiencing elevated errors due to [incident at AWS](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A). Currently, publishing a site might not work. We’ll monitor the situation and will provide updates if it changes.
Some hosted websites are currently returning 500 errors. This is related to a confirmed AWS outage impacting essential services used by Framer sites. We’re closely tracking their progress and will share updates as we learn more. Thank you for your patience.
**Good news**: we’ve redirected traffic to Framer sites away from the affected region which means that all websites are served correctly again. **Bad news**: the editor is currently fully unavailable. We’re continuing to monitor and are awaiting [updates from AWS](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A).
AWS reports that recovery has begun and we see the editor is working again. We will continue to monitor.
The editor is fully available again, the incident is now resolved.
We will be upgrading our database cluster configuration. During this time the Framer editor will be unavailable. Hosted websites are not affected by the upgrade.
Maintenance completed
