Helix Control-M Outage History

Helix Control-M had 3 outages in the last 2 years totaling 24m of downtime — averaging 0.1 incidents per month.

There were 3 Helix Control-M outages since May 10, 2026 totaling 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.controlm.com

Notice June 17, 2026

Attention: The Alerts listener has not been receiving Alerts for over an hour

Detected by Pingoru: Jun 17, 2026, 01:39 PM UTC
Resolved: Jun 17, 2026, 01:39 PM UTC
Duration: —

Affected: EU19894

Timeline · 1 update

resolved Jun 17, 2026, 01:39 PM UTC

We noticed that the Alerts listener in your environment has not been receiving Alerts for over an hour, which means that your tenant cannot currently send it Alerts. You might be missing critical Alerts about your environment.Check that the Alerts listener in your environment is up and running and can connect to the internet. For more information, see https://documents.bmc.com/supportu/controlm-saas/en-US/Documentation/Alerts.htm#SettingUpExternalAlerts

Read the full incident report →

Notice June 14, 2026

Control-M/Server PACTV.9.0.27.083

Detected by Pingoru: Jun 14, 2026, 12:59 PM UTC
Resolved: Jun 14, 2026, 12:59 PM UTC
Duration: —

Affected: EU32071

Timeline · 1 update

investigating Jun 14, 2026, 12:59 PM UTC

An important update is scheduled for your tenant EU32071. Maintenance will take place during your tenant's maintenance window on June 28th between 8:00 – 8:30 UTC. The update process may take up to 10 minutes to complete. During this period, scheduling services may be temporarily unavailable for up to 10 minutes. To prepare for the update and understand the impact please read What happens to scheduled jobs when the Control-M SaaS tenant is down for maintenance? For details on what this update includes, please refer to the Technical Bulletin.

Read the full incident report →

Major May 31, 2026

Availability - Impacted services

Detected by Pingoru: May 31, 2026, 11:09 AM UTC
Resolved: May 31, 2026, 11:33 AM UTC
Duration: 24m

Affected: US02297

Timeline · 2 updates

identified May 31, 2026, 11:09 AM UTC

Our technical team identified a disruption with these service WEB connectivity
resolved May 31, 2026, 11:33 AM UTC

Issue resolved

Read the full incident report →