CommandLink Outage History

CommandLink degraded View live status →

CommandLink had 7 outages in the last 2 years totaling 64h 33m of downtime — averaging 0.3 incidents per month.

There were 7 CommandLink outages since March 5, 2025 totaling 64h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.commandlink.com

Minor February 12, 2026

Slowness on some pages

Detected by Pingoru
Feb 12, 2026, 06:39 PM UTC
Resolved
Feb 12, 2026, 07:22 PM UTC
Duration
42m
Affected: ITSM Platform
Timeline · 3 updates
  1. investigating Feb 12, 2026, 06:39 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 12, 2026, 06:51 PM UTC

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

  3. resolved Feb 12, 2026, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 30, 2025

Degraded Performance

Detected by Pingoru
Oct 30, 2025, 04:23 PM UTC
Resolved
Nov 01, 2025, 06:03 PM UTC
Duration
2d 1h
Affected: ITSM Platform
Timeline · 4 updates
  1. investigating Oct 30, 2025, 04:23 PM UTC

    In response to underlying provider failures, we have activated our failover plans to mitigate. Services should be working at this time. We will continue to update.

  2. identified Oct 30, 2025, 06:55 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 31, 2025, 02:44 AM UTC

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

  4. resolved Nov 01, 2025, 06:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 29, 2025

Platform Outage

Detected by Pingoru
Oct 29, 2025, 10:30 PM UTC
Resolved
Oct 29, 2025, 08:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Oct 29, 2025, 10:30 PM UTC

    Outage of Backend Servers caused prolong HTTP timeouts on certain resources.

Read the full incident report →

Notice May 5, 2025

Partial Outage

Detected by Pingoru
May 05, 2025, 10:58 PM UTC
Resolved
May 05, 2025, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved May 05, 2025, 10:58 PM UTC

    Partial Outage of Backend Servers caused intermediate HTTP timeouts.

Read the full incident report →

Minor April 16, 2025

Page Failures

Detected by Pingoru
Apr 16, 2025, 05:24 PM UTC
Resolved
Apr 17, 2025, 04:49 AM UTC
Duration
11h 24m
Affected: ITSM Platform
Timeline · 4 updates
  1. investigating Apr 16, 2025, 05:24 PM UTC

    We are currently investigating this issue.

  2. identified Apr 16, 2025, 05:50 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 16, 2025, 06:24 PM UTC

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

  4. resolved Apr 17, 2025, 04:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 3, 2025

Platform Impact

Detected by Pingoru
Apr 03, 2025, 01:17 PM UTC
Resolved
Apr 03, 2025, 01:55 PM UTC
Duration
37m
Affected: ITSM Platform
Timeline · 2 updates
  1. investigating Apr 03, 2025, 01:17 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 03, 2025, 01:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025

Intermittent Access

Detected by Pingoru
Mar 05, 2025, 05:20 PM UTC
Resolved
Mar 05, 2025, 07:28 PM UTC
Duration
2h 7m
Affected: ITSM Platform
Timeline · 8 updates
  1. investigating Mar 05, 2025, 05:20 PM UTC

    We are currently investigating this issue.

  2. identified Mar 05, 2025, 05:26 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 05, 2025, 05:38 PM UTC

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

  4. identified Mar 05, 2025, 05:46 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Mar 05, 2025, 05:54 PM UTC

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

  6. identified Mar 05, 2025, 06:21 PM UTC

    The issue has been identified and a fix is being implemented.

  7. monitoring Mar 05, 2025, 06:36 PM UTC

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

  8. resolved Mar 05, 2025, 07:28 PM UTC

    This incident has been resolved.

Read the full incident report →