Controlant Outage History

Started Sep 16, 2026, 09:42 AM UTC· resolved Sep 16, 2026, 05:00 PM UTC

1. identified Sep 16, 2026, 09:42 AM UTC

   We are writing to let you know that our third-party system used for case handling (Salesforce) is experiencing intermittent availability issues. This may cause slower than usual responses to support cases and requests today. The MARS service has activated business continuity procedures, and our team continue to process requests through alternative channels. Any core functionalities of Controlant system, such as temperature monitoring, data logging, and alerting from the system are not affected, and your shipment data continues to be collected and stored as normal. The provider has acknowledged the issue on their public status page. Resolution is dependent on the third-party provider and no restoration time has been confirmed. We will issue the next update by 10:30 UTC+0.

2. identified Sep 16, 2026, 10:22 AM UTC

   The status is unchanged. The incident remains ongoing at our third-party provider (Salesforce), who is working to restore service. No resolution time has been confirmed. Our customer support, MARS and logistics teams have activated business continuity procedures and continue to provide services using alternative systems. Slight delays in responses may be experienced. No other disruptions to our services are expected. An update will be posted once the third-party provider has resolved the issue on their end, or sooner if there is any significant change in status. We would like to extend our appreciation for your patience and understanding during the incident. Our incident management team continues to monitor the situation closely.

3. resolved Sep 16, 2026, 05:00 PM UTC

   Incident Status: Resolved. Our third-party provider (Salesforce) deployed a fix on their end in the early afternoon. Our teams have since returned to normal systems, and we have monitored the situation for over four hours with no further issues. On that basis, the incident is now marked as resolved.

Read the full incident report →

Started Mar 14, 2026, 06:20 PM UTC· resolved Mar 16, 2026, 09:39 AM UTC

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.

Read the full incident report →

Started Oct 20, 2025, 10:04 AM UTC· resolved Oct 20, 2025, 04:20 PM UTC

1. monitoring Oct 20, 2025, 10:04 AM UTC

   AWS globally is experiencing issues. Controlant’s team is monitoring our services closely and no impact to our solutions has been identified. Controlant continues to monitor the status and will issue an update should any impact be confirmed.

2. resolved Oct 20, 2025, 04:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 31, 2025, 04:10 PM UTC· resolved Mar 31, 2025, 04:42 PM UTC

1. investigating Mar 31, 2025, 04:10 PM UTC

   We need to inform you about an incident that has recently occurred affecting SCM’s performance. Below is the status based on our initial analysis. Date and Time: Mon, March 31, 2025; 13:45 GMT SCM was reported to have intermittent performance issues for the majority of users from 13:45 GMT. We are investigating this and will provide updates as necessary. The next update will be provided at 17:00 GMT.

2. resolved Mar 31, 2025, 04:42 PM UTC

   SCM is fully operational from 16:13 GMT.

Read the full incident report →