Smartlook 장애 기록

1. 2026년 10월 26일 오전 5:57 UTCinvestigating

   Smartlook 로그인에 문제가 있습니다. 사용자는 계정에 액세스하려고 시도 할 때 504 Gateway Timeout 오류를 볼 수 있습니다. 우리의 개발 팀은 문제점의 aware이고 고침에 적극적으로 일하고 있습니다.

2. 2026년 10월 26일 오전 6:01 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 10월 26일 오전 9:26 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

4. 2026년 10월 26일 오전 9:27 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

5. 2026년 10월 26일 오후 2:37 UTCmonitoring

   우리는 현재 문제가 완전히 해결 된 최종 확인을 제공하기 전에 서비스를 모니터링하고 있습니다.

6. 2026년 10월 26일 오후 2:38 UTCmonitoring

   수정이 릴리스되었습니다. 이제 Smartlook에 다시 로그인 할 수 있습니다.

7. 2026년 10월 26일 오후 2:40 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

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

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

   Due to a global AWS outage between October 19 and 20, 2025, some Smartlook services experienced disruptions. The main application at app.smartlook.com remained fully operational. The issue has been resolved, and smartlook.com is now fully online again.

1. 2025년 1월 27일 오후 1:40 UTCidentified

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

2. 2025년 1월 27일 오후 1:40 UTCidentified

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

3. 2025년 1월 27일 오후 4:26 UTCidentified

   If you need access to Smartlook account before the final solution is provided, please contact our support team at [email protected].

4. 2025년 1월 28일 오후 5:07 UTCidentified

   The issue is still ongoing, as we are currently awaiting feedback from the provider regarding the publication of the new Okta certificates. We apologize for the complications and appreciate your patience. Rest assured, we will keep you updated on any developments. In the meantime, if you'd like, you can contact [email protected] for an interim login solution while we work to resolve the issue. Thank you for your understanding.

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

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

6. 2025년 2월 24일 오전 8:53 UTCresolved

   This incident has been resolved.

1. 2024년 11월 14일 오후 2:13 UTCinvestigating

   We are currently investigating the issue.

2. 2024년 11월 14일 오후 2:41 UTCresolved

   The incident has been now resolved. Sessions are playable without any troubles.

1. 2024년 8월 7일 오후 1:55 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 8월 7일 오후 3:49 UTCresolved

   A larger load of recordings caused a delay in their processing. As a result, active and recently completed recordings were not immediately accessible, but they became playable after some time. The issue is fixed now and all the sessions work as expected. There is a possibility of corrupted sessions.

1. 2024년 8월 7일 오전 6:14 UTCresolved

   A larger load of recordings caused a delay in their processing. As a result, active and recently completed recordings were not immediately accessible, but they became playable after some time. The issue is fixed now and all the sessions work as expected. There is a possibility of corrupted sessions.

1. 2024년 5월 7일 오전 7:41 UTCresolved

   Due to a disruption in our service, completed sessions were loading with a significant delay.

1. 2024년 4월 11일 오후 3:04 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 4월 11일 오후 3:27 UTCmonitoring

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

3. 2024년 4월 11일 오후 3:56 UTCresolved

   This incident has been resolved.

1. 2024년 3월 27일 오후 2:42 UTCinvestigating

   We are looking into an issue where for some users the sessions and session list is loading with a significant delay.

2. 2024년 3월 27일 오후 4:34 UTCidentified

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

3. 2024년 3월 27일 오후 5:32 UTCresolved

   This incident has been resolved.

1. 2024년 3월 21일 오후 6:34 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 3월 22일 오전 6:48 UTCmonitoring

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

3. 2024년 3월 22일 오전 8:50 UTCresolved

   This incident has been resolved. The issue lasted from 6.45 PM to 7.15 PM (CET), March 21, 2024, mainly session replay was affected. There might be a minor data loss (missing/corrupted sessions).

1. 2024년 3월 14일 오전 7:25 UTCinvestigating

   We are currently investigating an issue where recording playback returns "Missing or corrupted record." error.

2. 2024년 3월 14일 오전 7:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 3월 14일 오전 8:44 UTCidentified

   The issue has been located, and we are working on a fix.

4. 2024년 3월 14일 오전 11:09 UTCresolved

   The issue is now resolved. Some website project recordings recorded from 07:00 AM to 11:50 AM CET and mobile project recordings from 09:00 AM to 11:50 AM CET might be corrupted or missing. The issue affected recordings stored in EU datacenter. The root cause was AWS load balancer controller failure, which we have fixed in coordination with AWS support.

1. 2024년 3월 13일 오후 3:02 UTCinvestigating

   We are investigating a degraded performance with sessions loading.

2. 2024년 3월 13일 오후 6:21 UTCmonitoring

   Sessions are loading again, and we keep monitoring the situation.

3. 2024년 3월 13일 오후 8:34 UTCresolved

   This incident was resolved, and the performance is back to normal.

1. 2024년 3월 12일 오후 1:28 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 3월 12일 오후 7:06 UTCresolved

   Short-term decrease in UI performance between 5pm and 6pm (CET). Some recordings may not have been persisted. We are sorry for any inconvenience caused.

1. 2024년 3월 11일 오후 2:06 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 3월 11일 오후 2:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 3월 11일 오후 4:12 UTCmonitoring

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

4. 2024년 3월 11일 오후 5:24 UTCresolved

   This incident was resolved, and the performance is back to normal. There might be some data loss between 2:45 PM and 3:45 PM (CET). We apologize for the inconvenience, and thank you for your understanding.

1. 2024년 3월 5일 오후 7:03 UTCinvestigating

   We are investigating the degraded performance of the app.

2. 2024년 3월 6일 오전 5:55 UTCresolved

   This incident was resolved, and the performance is back to normal. No sessions should be impacted.

1. 2024년 3월 4일 오후 5:07 UTCinvestigating

   We are investigating a degraded performance of the app.

2. 2024년 3월 5일 오전 6:43 UTCmonitoring

   The services have returned to the normal level of performance, and we are monitoring them.

3. 2024년 3월 5일 오전 8:35 UTCresolved

   This incident was resolved, performance is back to normal, there should be no data loss.

1. 2024년 2월 29일 오후 8:27 UTCresolved

   UI performance issue that affected loading sessions. There might be some data loss (especially mobile projects) between 8.00 PM and 9.00 PM (CET). We are very sorry for any inconvenience.

1. 2024년 2월 14일 오후 5:03 UTCinvestigating

   We are currently investigating issues with sessions not loading.

2. 2024년 2월 14일 오후 5:55 UTCresolved

   The performance issue has been resolved, some recordings recorded between 5:30 PM CET and 6:30 PM CET might be corrupted.

1. 2024년 2월 12일 오후 6:34 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 2월 12일 오후 8:06 UTCmonitoring

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

3. 2024년 2월 12일 오후 8:30 UTCresolved

   The issue has been solved. As for sessions, from 7:00 PM CET to 9:00 PM CET, there might be some sessions missing or corrupted, especially mobile ones. Our apologies for any inconvenience caused by this issue.

1. 2024년 2월 5일 오전 8:12 UTCinvestigating

   We have observed prolonged loading times for some of the features and we are currently looking into the root cause.

2. 2024년 2월 5일 오전 8:20 UTCidentified

   We are currently experiencing performance issues with our database and are actively working on resolving it.

3. 2024년 2월 5일 오전 9:22 UTCresolved

   The database is stable now. The issue lasted from 8:45 AM CET to 9:45 AM CET, affecting both the reading and saving of recordings. Some recordings may be missing or corrupted.