Smartlook Outage History

Smartlook is up right now

Smartlook had 3 outages in the last 2 years totaling 667h 40m of downtime, averaging 0.1 incidents per month.

There were 3 Smartlook outages since November 14, 2024 totaling 667h 40m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: smartlook.statuspage.io

Notice October 20, 2025

AWS Outage Impacting Smartlook Services

Detected by Pingoru
Oct 20, 2025, 11:45 AM UTC
Resolved
Oct 20, 2025, 11:45 AM UTC
Duration
–
Timeline · 1 update
  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

Detected by Pingoru
Jan 27, 2025, 01:40 PM UTC
Resolved
Feb 24, 2025, 08:53 AM UTC
Duration
27d 19h
Affected: Web Application
Timeline · 6 updates
  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 →