Cronologia delle interruzioni di Framer

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.

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.

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.

API went down

The issue has been fixed at our downstream provider and all AI features are fully working again.

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.

Usage of the Framer app will be interrupted for 5-10 minutes as we perform upgrades to our databases.

Fontshare fonts have resolved the issue

One of our font providers, fontshare.com, is experiencing an outage. Some fonts might be temporarily unavailable.

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’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’re seeing full recovery and removed our mitigation. We’re monitoring the AWS reports until they also report a full recovery.

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.

framerusercontent.com is experiencing DNS issues due to an underlying issue at AWS. The issue is under active investigation.

We’re investigating issues with the framerusercontent.com DNS records not resolving as expected.

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.

The editor is fully available again, the incident is now resolved.

AWS reports that recovery has begun and we see the editor is working again. We will continue to monitor.