Unleash Outage History

Unleash is up right now

Pingoru has recorded 48 incidents for Unleash: 2 in the last 12 months and 0 in the last 90 days.

Source: unleash.instatus.com

48incidents recorded
2last 12 months
0last 90 days
15 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Unleash 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 511 (0%)

Incidents, newest first

Minor February 3, 2026 Some customers on self-served have issues signing in. 29m

Started Feb 03, 2026, 09:45 AM UTC· resolved Feb 03, 2026, 10:14 AM UTC

  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 38m

Started Jan 30, 2025, 09:17 PM UTC· resolved Jan 30, 2025, 09:55 PM UTC

  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. 1h 10m

Started Nov 29, 2024, 10:15 AM UTC· resolved Nov 29, 2024, 11:25 AM UTC

  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 →