Controlant logo

Is Controlant Down?

SaaSLive status, outages, and incident history

No. Controlant is up right now.

Every monitored Controlant system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 8m agoLive · every 60s

Know the moment Controlant breaks

Controlant is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Controlant status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Controlant Status Summary

As of 16:57 UTC on 14 November 2026, Controlant is operational. PulsAPI checked Controlant's official status page and found 9 of 9 components operational, with no active incidents. The latest incident, "Impact of Microsoft service outage", was on Nov 13, 2026 and lasted 6h 7m.

Cite as: PulsAPI, “Controlant status”, checked 14 November 2026, 16:57 UTC. https://www.pulsapi.com/services/controlant

Controlant Component Status

The main Controlant systems on this page. All 9 are operational right now.

9operational
API v1
Operational
Asset Management Services » Calibration - AM
Operational
Asset Management Services » Calibration API
Operational

6 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Asset Management Services » Centralized ID API, Asset Management Services » Device Programmer - AM, Asset Management Services » Device Programmer API, Asset Management Services » Scanning Service API, Integrations API, Supply Chain Monitoring.

See all of them free

Component statuses may change independently during partial outages.

Recent Controlant Outages & Incidents

Incident history from the official Controlant status page, including resolution updates.

Impact of Microsoft service outageResolved Nov 13, 2026 · 6h 7mResolved

Microsoft has not yet fully resolved its issue, but it no longer affects Controlant services. Email to and from Controlant is working as intended. If you have any further problems, please contact Controlant Support at support@controlant.com or +354 517 0630/ +1 (855) 44-CONTR. --- [2026-11-13T12:03:13.438Z] (monitoring) There has been no change since our last update. Restoring service depends on Microsoft. Core functions of the Controlant system are not affected. This includes temperature monitoring, data logging and system alerting. Shipment data continues to be collected and stored as usual, and shipment quality information is available in the Controlant SCM platform. 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. --- [2026-11-13T12:05:02.877Z] (monitoring) We’d like to let you know that Microsoft, the third-party provider of our email accounts, is having availability issues. Because of this, emails sent to our support team during this time may not have been received. For urgent requests, please call Controlant Support at +354 517 0630 or +1 (855) 44-CONTR (+1 855 442 6687). For non-urgent requests that have been sent by e-mail, Support will respond once Microsoft has restored normal functionality. MARS service continues to handle requests through phone and email to notify stakeholders of alerts. Core functions of the Controlant system are not affected. This includes temperature monitoring, data logging and system alerting. Shipment data continues to be collected and stored as usual, and shipment quality information is available in the Controlant SCM platform. The shipment quality reports are generated automatically to subscribed users, but depending on the service utilized by end users, their delivery may be affected. Users are encouraged to use Controlant's SharePortal to access the reports or to log in directly to SCM platform to assess the shipment quality. Microsoft has acknowledged the issue on its public status page. Restoring service depends on Microsoft, and it has not yet confirmed when that will happen. Our next update will be published by 12 UTC.

Salesforce intermittent availability issuesResolved Sep 16, 2026 · 7h 18mResolved

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. --- [2026-09-16T10:28:56.416Z] (identified) 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. --- [2026-09-16T10:28:34.422Z] (identified) 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.

Controlant Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Controlant incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Controlant Outage Reports

Problems reported by engineers using Controlant. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Controlant problems reported yet.

Something wrong with Controlant on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Controlant

Controlant's status page at status.controlant.com lists 9 components, such as API v1 (Legacy Integrations API), Calibration - AM and Calibration API. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Controlant's side or yours.

Controlant Status FAQ

Is Controlant down right now?

The verdict at the top of this page comes from the latest poll of the official Controlant status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Controlant is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Controlant recovers.

How do I check Controlant uptime history?

PulsAPI tracks Controlant uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Controlant changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Controlant outages?

PulsAPI reads the official Controlant status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Controlant components?

Yes. PulsAPI monitors 9 individual Controlant components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Controlant goes down?

Yes. Create a free account and subscribe to Controlant: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Controlant to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Controlant problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Controlant?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Controlant plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Controlant with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services