Is Framer Down Right Now? Check if there is a current outage ongoing.

We are experiencing higher-than-normal traffic levels caused by a DDoS attack, and are responding to it.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're seeing higher-than-usual amounts of traffic on the editor.

This incident has been resolved.

The editor is now fully operational again, but we’ll continue to monitor.

The editor is available, but performance can be degraded. We’ll continue working on a full fix.

The issue has been identified and a fix is being implemented.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We’ve identified the issue and service is restored to full availability. Apologies for the inconvenience!

We are continuing to investigate this issue.

We are seeing degraded performance of the Framer editor (hosted websites remain unaffected).

This incident has been resolved.

We’ve observed slower response times between 22:02 UTC and 22:10 UTC due to an attack in the US region. We’ve mitigated the attack and are monitoring.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The Marketplace on www.framer.com is temporarily unavailable due to issues at a 3rd party. We’re assured they’re working on it. Note: hosted sites and the Framer editor are not affected.

The block has seemingly been lifted. We're still investigating further here, and will keep the community post updated when we learn more.

We are aware that framer.website and any subdomain of it are currently inaccessible in Türkiye due to government block. > framer.website has been blocked by the decision dated 01/08/2024 and numbered 490.05.01.2024.-608178 of the Information and Communication Technologies Authority. We are looking into our options, for updates please see the community announcement: https://www.framer.community/c/announcements/framer-website-domain-blocked-in-turkey

This incident has been resolved.

We are currently experiencing periods of higher than normal load on our editor, which leads to degraded performance and occasional errors when opening projects.

This incident has been resolved.

We have implemented a fix for the issue, and newly published sites will again optimize correctly. If you saw errors during the incident that optimization failed please retry publication to trigger a new optimization attempt.

We have identified a problem in our site optimization pipeline, and are working on a fix. Existing published sites continue to work, but newly published sites will fail optimization and only be available in their un-optimized variant. We will update this incident when the issue is resolved.

This incident has been resolved.

We're still not happy with the performance of the analytics backend, and are scaling it out once more today. We expect minimal short interruptions during that time when accessing the analytics in the editor.

The scaled out cluster is working normally. We're still monitoring it for performance issues, and might further scale it in the next few days.

We're scaling our analytics backend in the coming hours. During that time access to analytics functions in the editor might be slow or could be completely unavailable. We'll post an update here when the scaling operation has been completed.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

You might experience loading issues in the Framer editor and on the dashboard. Published sites are *not* affected. We are aware of the issue and expecting to have it resolved within about 15m.

This incident has been resolved.

We are continuing to monitor for any further issues.

We have re-enabled all edge locations, and performance of the editor should be back to normal. We are continuing to monitor the system.

We’ve mitigated the issue by temporarily switching off edge locations for the editor in Asia. (Websites are not affected.) This change will increase connection times from the app to our backend, and therefore will slightly impact the loading performance of the editor in that region. We are waiting for more information from AWS on this issue and are hoping to remove the mitigation as soon as possible.

We are observing that all requests that are coming via the Hyderaba, India edge location are missing valid authorization headers, making the requests fail. This is causing loading issues in the editor. Projects will only load partially and the preview and publishing will not work. This is a connection issue and no data has been lost. The workaround is to use a VPN to connect to Framer. We currently believe this issue is out of our control, but are working with AWS to make sure this is the case and are looking into possible mitigations. Hosted websites are not affected.

This incident has been resolved.

The attack seems to be subsiding and we're continuing to monitor for any further activity.

We are experiencing higher-than-normal traffic levels possibly caused by an attack, and are responding to it.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Due to an ongoing HTTP flood we are seeing degraded performance of the Framer editor (hosted websites remain unaffected). We’re working on mitigating the issue.

On February 27th 2024, a small subset of Framer sites experienced a partial service degradation. The affected sites were served with incomplete HTML content under certain conditions. The root cause was a code change that we deployed February 26th 2024 at 15:39 UTC. The change caused our servers to incorrectly truncate `gzip` compressed sites. The corrupted content was also stored into our caches. This resulted in sites being served with incomplete content when clients requested a `gzip` compressed site. Modern browsers \(about 97% of site visitors\) use `brotli` compression, so were not affected. However, sites using a reverse proxy that request `gzip` content were affected, and possibly passed on broken content. On February 27th 2024 around 09:05 UTC, multiple Framer employees started noticing some sites to be broken \(as well as some Framer community posts reporting similar issues\). We immediately started investigating and fixed the issue by: * Rolling back the problematic code change. * Purging all cached content from our hosting systems. This process was completed by 11:30 UTC on February 27th 2024. We are committed to a high quality standard, and we take this incident extremely seriously. This is what we’re doing to prevent this from happening again: * We are reviewing our testing and vetting procedures for future code changes and deployments carefully. We’re adding additional regression testing for more common and not-so-common scenarios before a code change can be released to the production systems. * We are looking into improving our reaction time to such incidents, giving customers better means to alert us and improving the processes for rolling back code changes. We apologize to all our customers and Framer site visitors for the inconvenience and disruptions caused by this incident.

The fix has fully rolled out, and we've confirmed it solves the rendering issue for the subset of affected sites.

We're rolling out a fix to mitigate the issue.

We have found the root cause which was related to our gzip compression, which only affected a small subset of sites because most browsers use brotli compression. Proxied sites (especially CloudFlare) were also mostly affected because they default to gzip.

We are continuing to investigate this issue.

We're seeing that some sites are not rendering correctly. We're currently investigating the issue.

We have been experiencing elevated error rates from our email provider, and some emails could not be send or will be delivered with a delay.

This incident has been resolved.

All sites are fully back up, but we continue to monitor the situation.

We’re under a heavy HTTP flood attack and some sites might be slow or experience downtime. We’re working to get it under control.

This Fontshare fonts are working again. If you don’t see the fonts yet, your browser might have cached an outdated API response, this will resolve itself in less than an hour. (Or you can manually clear the cache.)

All Fontshare fonts are currently unavailable in the editor because the downstream Fontshare API is sending an incorrect response. We’ve reached out to Fontshare to fix the issue and are awaiting an ETA. (NOTE: Fontshare fonts on published websites continue to work.)

This issue has been resolved. We’ve seen 30 minutes of successful response to our OpenAI requests and OpenAI’s status page also indicates it’s resolved https://status.openai.com/incidents/00fpy0yxrx1q

AI powered features such as generating pages and translations do currently not work, as they are powered by OpenAI, which is having a major outage. For more details and updates see OpenAI’s status page: https://status.openai.com/incidents/00fpy0yxrx1q

Sites using custom domains should redirect any requests using unencrypted HTTP to use encrypted HTTPS when they first get accessed by a browser. Unfortunately this was unavailable between about ~12:15 CEST and ~21:15 CEST. Note that the sites were available using HTTPS, and if a user had ever opened the site before they would also be redirected by their browser immediately as Framer configures all sites to use "strict transport security". Many browsers also use a "HTTPS by default" policy and would similarly not have been exposed to this problem.

This incident has been resolved.

The Framer app is currently experiencing occasional downtime due to an attack. Hosted sites are not affected.

This incident has been resolved.

We fought off the attack but are monitoring. The editor is operational again.

We are investigating an attack that is causing intermittent downtime of our editor. Hosted sites are not affected.

This incident has been resolved.

A fix has been implemented and we’re monitoring the results.

We are currently investigating intermittent site optimization errors when publishing. The log will contain messages about “Failed to write to output file”. The workaround is to retry publishing. Apologies for the inconvenience.

This incident has been resolved.

We've deployed additional rules to block the malicious traffic, and are continuing to monitor the effectiveness of these rules.

Due to an ongoing attack we are seeing degraded performance of the Framer editor (hosted websites remain unaffected).

This incident has been resolved.

Services should be back to normal. We are monitoring the situation.

We are seeing more attacks but are scaling up to handle the traffic. In the meantime you may see intermittent unavailability.

Services are back to normal and we are monitoring the situation and updating configurations.

Due to an ongoing attack we are seeing degraded performance of the Framer editor (hosted websites remain unaffected).

This incident has been resolved.

We've been observing intermittent attacks on our infrastructure, which create short moments of slower responses while we're reacting to these attacks through automated and manual processes.

We've further optimized the performance of our hosting environment, and have not observed problems since then.

We've been observing intermittent attacks on our infrastructure, which create short moments of slower responses while we're reacting to these attacks through automated and manual processes.

We have not seen any further issues during monitoring.

We are continuing to monitor for any further issues.

We have increased capacity and improved how we handle large bursts of traffic, and are seeing much better performance. We will continue to monitor the situation.

We're observing intermittent attacks on our infrastructure, which create short moments of slower responses while we're reacting to these attacks through automated and manual processes.

This incident has been resolved.

We are currently monitoring for more attacks but performance should be back to normal.

Due to an ongoing DDoS attack, sites have degraded. We're mitigating the issue now.

The incident has been resolved. All services perform again as expected.

AWS is reporting that all their services are recovering. We’re still seeing issues with site and image optimization, so we’re continuing to monitor.

We're experiencing issues due to outages in the AWS us-east-1 region. From what we can see hosted sites are not affected.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

Framer is now operating normally again.

We have identified an issue in our backend related to signups and are working to release a mitigation.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

The Framer editor is back up.

The Framer editor is currently unavailable. We're working on resolving the issue.

See [https://www.framerstatus.com/incidents/8x6ws496lpv2](https://www.framerstatus.com/incidents/8x6ws496lpv2)

We mitigated the attack and all sites respond normally.

We’re experiencing a DoS (Denial of Service) attack causing sites to respond more slowly or with an error.

We experienced a very large DoS \(Denial of Service\) attack. The attack targeted a single site, but unfortunately all sites were affected, resulting in about 10 minutes of outage in two incidents. Our target is to have your site always be available, so we’re very sorry this happened. ‌ The reason all sites were affected is that our servers hit internal rate-limiting on the shared DynamoDB database storing site information. We have fixed this by increasing the limits. ‌ The reason the outage took around 5 minutes each was to that our infrastructure took some time to pick up the block. We have fixed this by improving how blocking works. The decision to block is made by a human, but deploying the block will now take seconds instead of possibly minutes. ‌ The reason a second outage happened was that the traffic from the DoS had not fully subsided and the attackers used the returned availability of the site as a signal to ramp up the DoS again. We have changed our unblocking policy to take this into account in the future.

The block has been restored and all sites are served as normal again.

We removed a block for the previous DoS (Denial of Service) attack after traffic went back to normal, but the attack has returned.

We experienced a short period where some requests were slow and we could not serve all requests. During a HTTP flood attack an underlying component of our infrastructure got overloaded despite most parts scaling up. We mitigated the attack and have started work to ensure stable performance in the future.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

The problems were likely caused by problems on JSPM.io, see https://status.jspm.io/.

We are continuing to investigate this issue.

We're seeing newly published sites failing to optimize and not loading properly, and are investigating. For sites that have been published successfully before a temporary workaround is to revert to an earlier version for the time being.

This incident has been resolved.

We’re investigating API errors that cause some users not being able to log-in and sites not to optimize.

This incident has been resolved.

Some functionality in the Framer application might be slower than usual

This incident has been resolved.

Error rates are down but still elevated, so we continue to monitor. Error rates are elevated only in the Amsterdam region and seem to indicated a problem with our third-party service provider (AWS).

We are seeing elevated error rates in our monitoring when accessing Framer, and are investigating.

We can confirm that Framer is not affected by the two high-severity OpenSSL security vulnerabilities disclosed today. The vulnerabilities are being tracked as <a href="https://www.openssl.org/news/vulnerabilities.html#CVE-2022-3786">CVE-2022-3786</a> and <a href="https://www.openssl.org/news/vulnerabilities.html#CVE-2022-3602">CVE-2022-3602</a>.

Framer is aware of a critical-severity security vulnerability in OpenSSL that is expected to be disclosed later today. Based on the limited information available at this time, we do not believe Framer is affected. Framer will continue to monitor the situation closely. In the meantime, if you have any questions, please reach out to your account manager or Framer Support (<a href="mailto:support@framer.com">support@framer.com</a>).

This incident has been resolved.

The root cause for the degradation has been mitigated and service is restored. We will keep monitoring the service.

We are currently investigating this issue.

This incident has been resolved.

Framer sites in the APAC region are currently seeing slower response times. We are monitoring this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We’re investigating degraded performance affecting hosted sites.

Services are back to operating normally.

Services have recovered. We will keep monitoring the issue.

Some users are experiencing network errors when trying to edit Framer projects. We are currently investigating this issue.

We’ve resolved the issue.

We’re investigating an issue with assets (images, fonts, etc) that don’t load and can’t be uploaded.

This incident has been resolved.

Framer is aware of a high-severity security vulnerability in the Apache Log4j logging library. This vulnerability was disclosed on Friday by the Apache Log4j project and is being tracked as CVE-2021-4428 (and dubbed "Log4Shell"). If exploited, this vulnerability could potentially allow a remote attacker to execute arbitrary code on the server. As soon as the vulnerability was made public on Friday (December 10, 2021), Framer's security team began a thorough audit of their products and cloud infrastructure. It was found that Framer products are not directly impacted, as they don't use Java in their stack. Framer does depend on several AWS services that use Apache Log4j, these have all since been patched. Framer will continue to monitor the situation closely. If you have any questions or concerns, please reach out to your account manager or Framer Support (<a href="mailto:support@framer.com">support@framer.com</a>)

With AWS fully recovering most if not all services, error rates have returned to normal for more than an hour.

Our error rates are back to normal, but we will continue monitoring the situation as AWS is not yet fully recovered.

Our error rates are still elevated, but we’re hearing most of the issues causing the outage have been identified by AWS and, like them, we’re seeing signs of recovery.

We’re affected by an outage of our cloud provider (AWS) and seeing several issues when using Framer.

We’ve successfully deployed the fix for smart components that stopped loading.

Some smart components and code components are not loading due to a bug in a recent update. We’re working to roll back the update, but are hindered by the ongoing partial outage of our cloud provider (AWS).

Our service provider has marked the incident as resolved.

API responses are back to normal. We'll continue to closely monitor performance until our service provider has marked the incident as resolved.

Our APIs are experiencing degraded performance due to increased error rates at one of our service providers. The issue has been identified, and we are awaiting a fix to be implemented.