Frontify 장애 기록

1. 2026년 7월 24일 오후 12:05 UTCinvestigating

   우리는 현재 일반 자산 업로드 또는 Library 페이지 로딩보다 느리게 발생할 수있는 성능 문제를 조사하고 있습니다. 우리의 팀은 가능한 빨리 정상적인 성과를 복원하기 위하여 일하고 있습니다.

2. 2026년 7월 24일 오후 12:33 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 24일 오후 2:04 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 3월 12일 오후 2:34 UTCidentified

   We are currently experiencing degraded performance on the Self-Service environment. Our team is actively investigating the root cause and working to restore stability as quickly as possible. At this stage, the impact is limited to the Self-Service environment; Enterprise customers remain operational.

2. 2026년 3월 12일 오후 3:04 UTCmonitoring

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

3. 2026년 3월 12일 오후 3:07 UTCresolved

   This incident has been resolved.

1. 2026년 1월 13일 오후 4:38 UTCinvestigating

   We are currently experiencing degraded performance across the application and are investigating the issue.

2. 2026년 1월 13일 오후 4:49 UTCmonitoring

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

3. 2026년 1월 13일 오후 4:52 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오후 3:37 UTCidentified

   Due to an Amazon Web Services outage, we are temporarily routing the delivery and processing of assets in the Americas via Europe. If you have any concerns, please contact [email protected]

2. 2025년 10월 21일 오전 8:13 UTCresolved

   After AWS reported that all issues had been resolved, we were able to migrate the delivery and processing of assets back to the US for US hosted customers this morning.

1. 2025년 10월 20일 오후 2:18 UTCmonitoring

   Our SelfService application is still affected by the ongoing AWS issue in the US region, preventing us from launching new servers. This may cause slower processing or temporary outages, mainly in image processing and search. Newly uploaded assets may not appear. AWS is working to resolve the issue.

2. 2025년 10월 20일 오후 6:08 UTCmonitoring

   The service is running and catching up with the queue. The search should start showing new content.

3. 2025년 10월 20일 오후 6:20 UTCmonitoring

   All uploaded assets are processed and should show and search results are up-to-date as well.

4. 2025년 10월 20일 오후 6:21 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 10월 20일 오후 6:22 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오전 11:56 UTCresolved

   We recently experienced a partial outage caused by a global Amazon Web Services (AWS) issue. This led to temporary disruption of file processing and degraded performance across some other functionalities. AWS has since mitigated the issue, and all Frontify services are now fully operational. If you continue to experience any issues, please contact our support team at [email protected].

1. 2024년 4월 17일 오후 12:44 UTCresolved

   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.

1. 2023년 10월 10일 오후 2:53 UTCresolved

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

1. 2022년 11월 16일 오후 5:07 UTCidentified

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

2. 2022년 11월 16일 오후 8:35 UTCidentified

   We are currently working on a fix.

3. 2022년 11월 16일 오후 10:00 UTCidentified

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

4. 2022년 11월 16일 오후 11:32 UTCidentified

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

5. 2022년 11월 17일 오전 2:05 UTCidentified

   We are working on the last big libraries

6. 2022년 11월 17일 오전 5:45 UTCidentified

   Still working on the last big libraries.

7. 2022년 11월 17일 오전 8:00 UTCmonitoring

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

8. 2022년 11월 17일 오후 4:32 UTCresolved

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

1. 2022년 11월 7일 오후 2:20 UTCmonitoring

   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

2. 2022년 11월 7일 오후 5:43 UTCresolved

   This incident has been resolved.

1. 2021년 12월 22일 오후 1:57 UTCidentified

   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.

2. 2021년 12월 22일 오후 3:01 UTCresolved

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

1. 2021년 12월 21일 오후 2:23 UTCresolved

   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.

1. 2021년 12월 7일 오후 5:49 UTCinvestigating

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

2. 2021년 12월 7일 오후 7:59 UTCmonitoring

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

3. 2021년 12월 7일 오후 9:49 UTCresolved

   Frontify page speed is back to normal.

1. 2021년 9월 29일 오후 3:45 UTCresolved

   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.

1. 2021년 5월 27일 오전 9:58 UTCresolved

   We are currently investigating a network issue within the data center

1. 2021년 1월 14일 오전 9:04 UTCresolved

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

1. 2020년 11월 21일 오후 9:51 UTCidentified

   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

2. 2020년 11월 21일 오후 10:16 UTCresolved

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

1. 2020년 9월 1일 오후 4:25 UTCresolved

   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

1. 2020년 8월 19일 오전 9:56 UTCinvestigating

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

2. 2020년 8월 19일 오전 10:03 UTCidentified

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

3. 2020년 8월 19일 오전 11:36 UTCmonitoring

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

4. 2020년 8월 19일 오후 2:22 UTCresolved

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

1. 2020년 6월 17일 오후 2:29 UTCidentified

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

2. 2020년 6월 17일 오후 2:30 UTCresolved

   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.

3. 2020년 6월 17일 오후 2:32 UTCpostmortem

   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.