Unleash Outage History

Unleash is up right now

Unleash had 3 outages in the last 2 years totaling 2h 17m of downtime — averaging 0.1 incidents per month.

There were 3 Unleash outages since November 29, 2024 totaling 2h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://unleash.instatus.com

Minor February 3, 2026

Some customers on self-served have issues signing in.

Detected by Pingoru
Feb 03, 2026, 09:45 AM UTC
Resolved
Feb 03, 2026, 10:14 AM UTC
Duration
29m
Timeline · 3 updates
  1. investigating Feb 03, 2026, 09:45 AM UTC

    We are currently investigating this incident..

  2. monitoring Feb 03, 2026, 09:46 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Feb 03, 2026, 10:14 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor January 30, 2025

Sign-in page unreachable

Detected by Pingoru
Jan 30, 2025, 09:17 PM UTC
Resolved
Jan 30, 2025, 09:55 PM UTC
Duration
38m
Timeline · 4 updates
  1. investigating Jan 30, 2025, 09:17 PM UTC

    We are currently investigating this incident..

  2. identified Jan 30, 2025, 09:28 PM UTC

    we have identified the issue and working on an solution..

  3. monitoring Jan 30, 2025, 09:45 PM UTC

    We are seeing improvements on the sign-in at it looks healthy again. .

  4. resolved Jan 30, 2025, 09:55 PM UTC

    All systems are fully operational again. It only impacted the sign-in of new users. No customer applications impacted. .

Read the full incident report →

Minor November 29, 2024

Features endpoint returning empty features for PRO customers.

Detected by Pingoru
Nov 29, 2024, 10:15 AM UTC
Resolved
Nov 29, 2024, 11:25 AM UTC
Duration
1h 10m
Timeline · 2 updates
  1. investigating Nov 29, 2024, 10:15 AM UTC

    We are currently investigating this incident..

  2. resolved Nov 29, 2024, 11:25 AM UTC

    This incident has been resolved. It was due to an faulty change, only impacting some of our pro-customers. We will do a post-mortem to understand why this happens, how we can prevent it in the future and other improvements we should implement based on this incident. .

Read the full incident report →