CommandLink Outage History

CommandLink is up right now

Pingoru has recorded 12 incidents for CommandLink: 1 in the last 12 months and 0 in the last 90 days.

Source: status.commandlink.com

12incidents recorded
1last 12 months
0last 90 days
43 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking CommandLink in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 9 (0%)

Incidents, newest first

Minor February 12, 2026 Slowness on some pages 42m ITSM Platform

Started Feb 12, 2026, 06:39 PM UTC· resolved Feb 12, 2026, 07:22 PM UTC

  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 2d 1h ITSM Platform

Started Oct 30, 2025, 04:23 PM UTC· resolved Nov 01, 2025, 06:03 PM UTC

  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 –

Started Oct 29, 2025, 08:00 AM UTC· resolved Oct 29, 2025, 08:00 AM UTC

  1. resolved Oct 29, 2025, 08:00 AM UTC

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

Read the full incident report →

Notice May 5, 2025 Partial Outage –

Started May 05, 2025, 07:00 PM UTC· resolved May 05, 2025, 07:00 PM UTC

  1. resolved May 05, 2025, 07:00 PM UTC

    Partial Outage of Backend Servers caused intermediate HTTP timeouts.

Read the full incident report →

Minor April 16, 2025 Page Failures 11h 24m ITSM Platform

Started Apr 16, 2025, 05:24 PM UTC· resolved Apr 17, 2025, 04:49 AM UTC

  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 37m ITSM Platform

Started Apr 03, 2025, 01:17 PM UTC· resolved Apr 03, 2025, 01:55 PM UTC

  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 2h 7m ITSM Platform

Started Mar 05, 2025, 05:20 PM UTC· resolved Mar 05, 2025, 07:28 PM UTC

  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 →