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

We are continuously working on enhancing our platform. Those ongoing improvements are implemented in small, iterative steps, and rigorously tested. During a database migration, a deadlock situation occurred for yet unknown reasons. This affected all our EU customers and caused a downtime of approximately 10 minutes. At no time did this compromise the security of our platform. Upon detecting the issue, we immediately took corrective actions and fixed the issue promptly. Once the immediate cause was identified and the deadlock resolved, all services were operational again. We are currently conducting a root cause analysis to prevent future occurrences and to extract valuable insights about what happened. Thank you for your understanding as we continue to refine our processes and enhance the reliability of our product.

We encountered higher load on our database cluster leading to slower response times.

All remaining index jobs finished successfully. If you still experience issues with asset display, please contact Frontify support.

The issue has been addressed. We are monitoring the additional reindexing today to ensure no additional issues come up.

Still working on the last big libraries.

We are working on the last big libraries

We are still recreating the index while more and more libraries should be up to date.

We are recreating the index for the overview of assets within the libraries. First customers should start to see assets they uploaded today.

We are currently working on a fix.

Currently freshly uploaded assets aren't visible within the libraries.

This incident has been resolved.

On Monday, on 12:40pm UTC a partial service outage occurred on all application clusters. Service restoration started at 13:05pm UTC with most of the accounts up and running in the following minutes. The service is fully restored. The issue was caused by database maintenance where legacy elements were renamed. We apologise for any inconvenience caused by this outage

The affected service has been restarted and all systems are back to normal.

A short 24-minute outage for non-Enterprise users occurred today around 13:21 pm UTC resulting in a 504 timeout error page. This was caused by the failure of one of the servers due to power issues at our hosting provider AWS. The application is running again, but there might be several residual issues that affect some functionalities. We are monitoring them as we expect an update on the issue from AWS. A further statement will provide more details once the hosting provider issue is completely addressed on their end.

On Monday morning, between 5:19 and 5:27 am UTC, one of our application clusters had a service interruption causing a short downtime. The following coincidence caused this: At midnight AWS took one of our application servers offline to mitigate a hypervisor issue. Shortly after, at 5:19 am UTC, our scheduled security update took the second application server out of service, causing the short outage. At 5:27 am UTC, the security updates finished successfully, and the server was retaken into service, ending the downtime. After investigating the issue, we put the first application server into service, so we are fully redundant again. To avoid this in the future, we enhanced monitoring and created automatic alerts notifying when there is only one application server in service. Additionally, any future scheduled security updates will first check for enough healthy resources before starting. We apologize for any inconvenience caused by this outage.

Frontify page speed is back to normal.

As AWS services are starting to resume the Frontify performance is increasing.

We can see slower response times for specific requests. These issues are related to the issues our infrastructure and services provider AWS is facing.

On September 29th a bug was reported that umlauts are not considered in group mapping, during the SSO login process. One of our developers fixed this bug, and, in order to verify the fix, he used some dummy credentials from his favourite show, SpongeBob. Unfortunately, the dummy credentials were shipped to production and affected the SSO login process. As a result, the wrong profile information was shown to already-registered users and the access to certain guidelines or projects was declined. Most importantly, no security breach happened and no external users had access to your account or your data. We rolled back the code and provided a fix shortly after that. We apologize for the circumstances. We learned our lesson from this and will analyze our deployment and peer programming process to avoid such mistakes in the future.

We are currently investigating a network issue within the data center

Our monitoring falsely reported an outage while there was none. We are sorry for the inconvenience this might have caused to you.

The incident has been resolved. All systems are back online.

Our Provider Metanet has identified a network problem on their server clusters. They are working on a solution to fix the issue. Affected Datacenter: CH

Partial Failure for some of our customers located in the EU Datacenter (Frankfurt) - we are investigating what happend and collecting all information. All customers are back online. Downtime was < 15min

All affected preview images on all edge locations of our CDN (cache) have been invalidated.

Most preview images should look good, again while we are still invalidating some cache content.

We found some broken preview images in our CDN (cache) and are about to invalidate them.

We are investigating some issues with images not properly shown in preview.

Due to a partition size change a server mount failed. For this reason, the application became unavailable in our Frankfurt Datacenter. Some servers needed a restart to fix the issue. The Infrastructure team is now analyzing why the fallback was not working properly.

The affected service has been restarted and all systems are back to normal. We'll be investigating why a single failure has led to this outage and take actions accordingly.

Due to the failure of one server users may have seen very long response times or even a 504 timeout error page.

All systems are back to normal

The issue was caused by a database server failover.

We are currently investigating this issue.

Adobe released a fixed version.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

Status: Known Issue The Frontify plugin and the latest version of Adobe XD, XD 23, are not compatible. The issue will be resolved with XD 24 when it is released. We suggest avoiding updating to XD 23 and to continue using XD 22. There are no known compatibility issues with version 22 of Adobe XD.

The Frontify Self Service Application was overloaded due to an internal process which hammered an expensive internal API on the Frontify Self Service Application. I turns out that it called this API due to a misconfiguration. We fixed the configuration and additionally adjusted the process to avoid things like this in the future.

The response time of the application was very slow. Many calls lead to timeouts or corresponding error pages.

Due to an overloaded system, we had an outtake of our public cloud system. All systems are fully available again. Duration of the failure: 5 minutes

Due to an automated system update, we had an overloaded server system. We are currently in the investigation of why the automated failover did not work. Between 07:00 am and 07:30 am, all systems have been successfully rebooted.

Due to an automated system update, we had an overloaded server system. We are currently in the investigation of why the automated failover did not work. Between 07:00am and 07:30am, all systems have been successfully rebooted.

Identified the cause for this alert. While the application was running as expected this alert was triggered due to changes in the site layout. Solution: Adjusted test to the new layout.

This incident has been resolved.

We are currently investigating this issue.

A fix was released. All systems are performing normally.

We've solved the issue for now and are working on a fix to avoid future issues.

We are seeing increased answer times that may even hit the request timeout. The issue has been identified and is about to being solved.

This incident has been resolved.

We are continuing to monitor for any further issues.

Due to an AWS outtage we encounter degrated performance on the Frontify Application and Website