Controlant incident

Intermittent service disruption

Notice Resolved View vendor source →

Controlant experienced a notice incident on March 14, 2026 affecting Device Programmer - AM and Centralized ID API and 1 more component, lasting 1d 15h. The incident has been resolved; the full update timeline is below.

Started
Mar 14, 2026, 06:20 PM UTC
Resolved
Mar 16, 2026, 09:39 AM UTC
Duration
1d 15h
Detected by Pingoru
Mar 14, 2026, 06:20 PM UTC

Affected components

Device Programmer - AMCentralized ID APISupply Chain MonitoringCalibration - AMDevice Programmer APIAPI v1 (Legacy Integrations API)Calibration APIIntegrations API (integrations.controlant.com)Scanning Service API

Update timeline

  1. monitoring Mar 14, 2026, 06:20 PM UTC

    We would like to inform you about the service disruption and was quickly investigated and solved. Date and Time: 14 March 2026, 12:07 GMT to 16:45 GMT Incident Title/ID: Intermittent service disruption Incident Severity: Major Incident Status: Underlying issue resolved, disruption being resolved in the coming hours Incident summary The controlant.com domain experienced an issue leading to temporary service disruption. Initial impact assessment SCM is temporarily unavailable to some users, with some disruptions to alerts from devices, and some APIs not accessible. While there are some delays, there is no risk of data loss. The underlying issue has been resolved. Service availability will normalize as the DNS updates propagate globally over the coming hours. We continue to monitor the situation.

  2. monitoring Mar 14, 2026, 08:32 PM UTC

    The situation remains unchanged since the previous update. SCM is still temporarily unavailable to some users, with some disruptions to alerts from devices, and some APIs not accessible. While there are some delays, there is no risk of data loss. The underlying issue was resolved. Service availability will normalize as the DNS updates propagate globally over the coming hours. We are actively monitoring the recovery and will provide further updates as needed. Next update will be issued at 09:00 GMT+0.

  3. monitoring Mar 14, 2026, 10:36 PM UTC

    We’re seeing clear signs of recovery. Device traffic has returned to normal levels, and DNS records are continuing to update correctly across the internet. We are actively monitoring the recovery and will provide next update at 09:00 GMT+0

  4. monitoring Mar 15, 2026, 08:42 AM UTC

    We continue to see clear signs of recovery. Device traffic has returned to normal levels, and DNS records are continuing to update correctly across the internet. Some users may still experience minor, intermittent disruptions when accessing our platform. These are expected while DNS updates continue to propagate globally. Full normalization is anticipated within the next hours. Our teams are continuing to monitor recovery closely.

  5. monitoring Mar 15, 2026, 01:01 PM UTC

    We continue to see clear signs of recovery. Device traffic has returned to normal levels, and DNS records are continuing to update correctly across the internet. Some users may still experience minor, intermittent disruptions when accessing our platform. These are expected while DNS updates continue to propagate globally. Full normalization is anticipated within the next hours. Our teams are continuing to monitor recovery closely.

  6. monitoring Mar 15, 2026, 05:16 PM UTC

    We continue to see clear signs of recovery. Device traffic has returned to normal levels, and DNS records are continuing to update correctly across the internet. Some users may still experience minor, intermittent disruptions when accessing our platform. These are expected while DNS updates continue to propagate globally. Full normalization is anticipated within the next hours. Our teams are continuing to monitor recovery closely will provide next update at 09:30 GMT+0 tomorrow.

  7. resolved Mar 16, 2026, 09:39 AM UTC

    Incident Status: Resolved. Note that some users may still experience some delays accessing the system as service availability continues to normalize, as the DNS updates propagate globally. For any additional information, or questions related to this incident, please contact [email protected] or your usual contact person at Controlant.