mabl Outage History

mabl is up right now

mabl had 15 outages in the last 2 years totaling 404h 40m of downtime — averaging 0.6 incidents per month.

There were 15 mabl outages since August 4, 2025 totaling 404h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mabl.com

Major July 20, 2026

Error saving assertion steps in version 2.57.0 of the desktop app

Detected by Pingoru
Jul 20, 2026, 07:31 PM UTC
Resolved
Jul 21, 2026, 12:48 AM UTC
Duration
5h 16m
Timeline · 2 updates
  1. investigating Jul 20, 2026, 07:31 PM UTC

    We have identified an issue with saving assertion steps in version 2.57.0 of the desktop app. Please refrain from updating to this version. Engineers are actively working on a solution.

  2. resolved Jul 21, 2026, 12:48 AM UTC

    The core functionality is restored in Desktop App version 2.57.1. A display bug remains with the description of the selected element on the assertion form and will be resolved in the next release. This no longer impacts the ability to create, replay, and save custom find assertions in 2.57.1.

Read the full incident report →

Major July 13, 2026

mabl Desktop App failing to launch on some macOS devices after app update

Detected by Pingoru
Jul 13, 2026, 03:21 PM UTC
Resolved
Jul 14, 2026, 06:14 PM UTC
Duration
1d 2h
Timeline · 2 updates
  1. investigating Jul 13, 2026, 04:13 PM UTC

    We have identified the issue and it appears to only impact macOS machines running x64 architecture, macOS machines running on arm64 are not impacted. The team is working on a patch to the mabl Desktop app to resolve this issue for all affected users as soon as possible.

  2. resolved Jul 14, 2026, 06:14 PM UTC

    A patch has been applied with desktop app version 2.56.0 which should resolve the reported installation problems macOS systems running on x64 architecture. If you are still experiencing issues after updating to the latest version of the mabl app, please reach out to support for further assistance.

Read the full incident report →

Major June 24, 2026

Investigating - Test Scheduling and Execution Delays

Detected by Pingoru
Jun 24, 2026, 06:07 PM UTC
Resolved
Jun 24, 2026, 08:27 PM UTC
Duration
2h 20m
Timeline · 3 updates
  1. investigating Jun 24, 2026, 06:07 PM UTC

    We are currently investigating reports of delays affecting test scheduling and execution. Tests may take longer than expected to start or complete. Our team is actively investigating the root cause. We will provide updates as our investigation progresses.

  2. investigating Jun 24, 2026, 07:51 PM UTC

    We have resolved the underlying issue and are monitoring as the system recovers.

  3. resolved Jun 24, 2026, 08:27 PM UTC

    We will continue to monitor for any outliers.

Read the full incident report →

Major June 24, 2026

Degraded mabl Link connectivity — agents may fail to connect

Detected by Pingoru
Jun 24, 2026, 05:03 AM UTC
Resolved
Jun 24, 2026, 09:48 AM UTC
Duration
4h 45m
Timeline · 3 updates
  1. investigating Jun 24, 2026, 05:03 AM UTC

    We've identified an issue affecting mabl Link. Link agents may be unable to establish a connection and can remain in an "Initializing tunnel" state. As a result, test runs that use Link to reach private, internal, or firewalled applications may fail. Tests that do not use Link are unaffected. We've identified the underlying cause and are actively working on remediation.

  2. investigating Jun 24, 2026, 05:33 AM UTC

    We've applied a fix and Link agents are reconnecting. We're monitoring the recovery and confirming that Link-dependent test runs are succeeding again.

  3. resolved Jun 24, 2026, 09:48 AM UTC

    New Link tunnels are being created successfully, and we are not seeing any further signs of connectivity problems at this time.

Read the full incident report →

Major May 7, 2026

Login broken in desktop app version 2.50.0

Detected by Pingoru
May 07, 2026, 01:00 PM UTC
Resolved
May 07, 2026, 06:03 PM UTC
Duration
5h 3m
Timeline · 2 updates
  1. investigating May 07, 2026, 03:13 PM UTC

    When clicking the login button in version 2.50.0 of the desktop app, it currently opens an incorrect URL to continue the login process in the browser. We have identified the cause of the issue, and a fix will be available shortly. In the meantime, please avoid updating the desktop app.

  2. resolved May 07, 2026, 06:03 PM UTC

    Version 2.50.1 of the desktop app has been published which fixes the login problem. It is now safe to resume installing mabl app updates.

Read the full incident report →

Major November 2, 2025

Temporary Trainer "start task" step saving issue

Detected by Pingoru
Nov 02, 2025, 07:20 AM UTC
Resolved
Nov 02, 2025, 10:34 AM UTC
Duration
3h 14m
Timeline · 1 update
  1. resolved Nov 03, 2025, 03:39 AM UTC

    We identified an issue where tests with "start task" steps were unable to be saved. Upgrade to version 2.36.10 to resolve the issue. Thank you for your patience.

Read the full incident report →

Major October 20, 2025

Degradation of mabl mailbox

Detected by Pingoru
Oct 20, 2025, 04:33 PM UTC
Resolved
Oct 20, 2025, 09:11 PM UTC
Duration
4h 38m
Timeline · 1 update
  1. resolved Oct 20, 2025, 09:11 PM UTC

    The incident has been resolved and mabl Mailbox service has been restored. We apologize for the disruption.

Read the full incident report →

Major October 6, 2025

Login issues

Detected by Pingoru
Oct 06, 2025, 08:24 PM UTC
Resolved
Oct 20, 2025, 09:36 AM UTC
Duration
13d 13h
Timeline · 1 update
  1. resolved Oct 20, 2025, 09:36 AM UTC

    This incident has was resolved 20:40 UTC - 6 October 2025

Read the full incident report →

Major August 4, 2025

Mobile training down

Detected by Pingoru
Aug 04, 2025, 12:24 PM UTC
Resolved
Aug 04, 2025, 01:20 PM UTC
Duration
56m
Timeline · 1 update
  1. resolved Aug 04, 2025, 01:20 PM UTC

    We’ve completed monitoring the issue affecting the Mobile Training platform and confirmed that it was intermittent and did not impact all users. The service is now stable and fully operational. Thank you for your patience while we investigated. If you continue to experience any issues, please contact our support team.

Read the full incident report →