Smartlook Outage History

Smartlook is up right now

Pingoru has recorded 50 incidents for Smartlook: 0 in the last 12 months and 0 in the last 90 days.

Source: smartlook.statuspage.io

50incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Smartlook in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 527 (0%)

Incidents, newest first

Notice October 20, 2025 AWS Outage Impacting Smartlook Services –

Started Oct 20, 2025, 11:45 AM UTC· resolved Oct 20, 2025, 11:45 AM UTC

  1. resolved Oct 20, 2025, 11:49 AM UTC

    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.

Read the full incident report →

Minor January 27, 2025 SSO login is currently unavailable for some users 27d 19h Web Application

Started Jan 27, 2025, 01:40 PM UTC· resolved Feb 24, 2025, 08:53 AM UTC

  1. identified Jan 27, 2025, 01:40 PM UTC

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

  2. identified Jan 27, 2025, 01:40 PM UTC

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

  3. identified Jan 27, 2025, 04:26 PM UTC

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

  4. identified Jan 28, 2025, 05:07 PM UTC

    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. monitoring Feb 20, 2025, 01:10 PM UTC

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

  6. resolved Feb 24, 2025, 08:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 14, 2024 Sessions not playable due to the We're sorry, but something went wrong error. 28m Session Recording

Started Nov 14, 2024, 02:13 PM UTC· resolved Nov 14, 2024, 02:41 PM UTC

  1. investigating Nov 14, 2024, 02:13 PM UTC

    We are currently investigating the issue.

  2. resolved Nov 14, 2024, 02:41 PM UTC

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

Read the full incident report →