Zenoti incident

MIDE01 APIs, ZMA and CMA Application Connectivity Issues

Notice Resolved View vendor source →

Zenoti experienced a notice incident on June 8, 2026 affecting Zenoti-MIDE01, lasting 6h 20m. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2026, 10:05 AM UTC
Resolved
Jun 08, 2026, 04:26 PM UTC
Duration
6h 20m
Detected by Pingoru
Jun 08, 2026, 10:05 AM UTC

Affected components

Zenoti-MIDE01

Update timeline

  1. investigating Jun 08, 2026, 10:05 AM UTC

    We are currently observing intermittent failures impacting ZMA and CMA applications for customers hosted on MIDE01. Our engineering team is actively investigating the issue and working to identify the root cause. We will provide further updates as soon as more information becomes available. We apologize for any inconvenience and appreciate your patience.

  2. investigating Jun 08, 2026, 11:47 AM UTC

    We are continuing to investigate the issue. We will provide further updates as soon as more information becomes available.

  3. investigating Jun 08, 2026, 12:35 PM UTC

    We are continuing to investigate the issue. We will provide further updates as soon as more information becomes available.

  4. investigating Jun 08, 2026, 01:29 PM UTC

    We are continuing to investigate the issue. We will provide further updates as soon as more information becomes available.

  5. investigating Jun 08, 2026, 02:44 PM UTC

    We are continuing to investigate the issue. We will provide further updates as soon as more information becomes available.

  6. identified Jun 08, 2026, 03:50 PM UTC

    We have identified the cause of the intermittent failures affecting ZMA and CMA applications for customers hosted on MIDE01. Our engineering team is actively working to implement a fix and is closely monitoring the environment. We will provide additional updates as progress is made toward full resolution. Thank you for your patience and understanding.

  7. monitoring Jun 08, 2026, 04:08 PM UTC

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

  8. monitoring Jun 08, 2026, 04:09 PM UTC

    A fix has been implemented. We are currently monitoring the environment to ensure service stability and confirm that the issue has been fully resolved. We will continue to provide updates as necessary.

  9. resolved Jun 08, 2026, 04:26 PM UTC

    This incident has been resolved.