Störungsverlauf von Smartlook

1. 26. Oktober 2026 um 05:57 UTCinvestigating

   Wir haben derzeit ein Problem mit Smartlook Login. Benutzer sehen möglicherweise einen 504-Gateway-Timeout-Fehler, wenn sie versuchen, auf ihre Konten zuzugreifen. Unser Entwicklungsteam ist sich des Problems bewusst und arbeitet aktiv an einem Fix.

2. 26. Oktober 2026 um 06:01 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 26. Oktober 2026 um 09:26 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 26. Oktober 2026 um 09:27 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

5. 26. Oktober 2026 um 14:37 UTCmonitoring

   Wir überwachen derzeit den Service, bevor wir endgültig bestätigen, dass das Problem vollständig gelöst wurde.

6. 26. Oktober 2026 um 14:38 UTCmonitoring

   Der Fix wurde freigegeben und Benutzer können sich nun wieder bei Smartlook anmelden.

7. 26. Oktober 2026 um 14:40 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

8. 28. Oktober 2026 um 09:09 UTCresolved

   Wir entschuldigen uns für das Problem. Es wurde am 26. Oktober 2026 vollständig gelöst. Aufgrund dieses Problems wurden zwischen dem 23. Oktober 2026 um 21:30 UTC und dem 26. Oktober 2026 um 12:40 UTC keine Daten erhoben. Wir entschuldigen uns für die Unannehmlichkeiten und danken Ihnen für Ihr Verständnis.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Oktober 2025 um 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. 27. Januar 2025 um 13:40 UTCidentified

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

2. 27. Januar 2025 um 13:40 UTCidentified

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

3. 27. Januar 2025 um 16:26 UTCidentified

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

4. 28. Januar 2025 um 17: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. 20. Februar 2025 um 13:10 UTCmonitoring

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

6. 24. Februar 2025 um 08:53 UTCresolved

   This incident has been resolved.

1. 14. November 2024 um 14:13 UTCinvestigating

   We are currently investigating the issue.

2. 14. November 2024 um 14:41 UTCresolved

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

1. 7. August 2024 um 13:55 UTCinvestigating

   We are currently investigating this issue.

2. 7. August 2024 um 15: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. 7. August 2024 um 06: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. 7. Mai 2024 um 07:41 UTCresolved

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

1. 11. April 2024 um 15:04 UTCinvestigating

   We are currently investigating this issue.

2. 11. April 2024 um 15:27 UTCmonitoring

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

3. 11. April 2024 um 15:56 UTCresolved

   This incident has been resolved.

1. 27. März 2024 um 14:42 UTCinvestigating

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

2. 27. März 2024 um 16:34 UTCidentified

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

3. 27. März 2024 um 17:32 UTCresolved

   This incident has been resolved.

1. 21. März 2024 um 18:34 UTCinvestigating

   We are currently investigating this issue.

2. 22. März 2024 um 06:48 UTCmonitoring

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

3. 22. März 2024 um 08: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. 14. März 2024 um 07:25 UTCinvestigating

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

2. 14. März 2024 um 07:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 14. März 2024 um 08:44 UTCidentified

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

4. 14. März 2024 um 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. 13. März 2024 um 15:02 UTCinvestigating

   We are investigating a degraded performance with sessions loading.

2. 13. März 2024 um 18:21 UTCmonitoring

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

3. 13. März 2024 um 20:34 UTCresolved

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

1. 12. März 2024 um 13:28 UTCinvestigating

   We are currently investigating this issue.

2. 12. März 2024 um 19: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. 11. März 2024 um 14:06 UTCinvestigating

   We are currently investigating this issue.

2. 11. März 2024 um 14:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 11. März 2024 um 16:12 UTCmonitoring

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

4. 11. März 2024 um 17: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. 5. März 2024 um 19:03 UTCinvestigating

   We are investigating the degraded performance of the app.

2. 6. März 2024 um 05:55 UTCresolved

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

1. 4. März 2024 um 17:07 UTCinvestigating

   We are investigating a degraded performance of the app.

2. 5. März 2024 um 06:43 UTCmonitoring

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

3. 5. März 2024 um 08:35 UTCresolved

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

1. 29. Februar 2024 um 20: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. 14. Februar 2024 um 17:03 UTCinvestigating

   We are currently investigating issues with sessions not loading.

2. 14. Februar 2024 um 17: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. 12. Februar 2024 um 18:34 UTCinvestigating

   We are currently investigating this issue.

2. 12. Februar 2024 um 20:06 UTCmonitoring

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

3. 12. Februar 2024 um 20: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. 5. Februar 2024 um 08:12 UTCinvestigating

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

2. 5. Februar 2024 um 08:20 UTCidentified

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

3. 5. Februar 2024 um 09: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.