Targetprocess Outage History

Targetprocess is up right now

Targetprocess had 48 outages in the last 2 years totaling 137h 59m of downtime — averaging 2 incidents per month.

There were 48 Targetprocess outages since October 24, 2024 totaling 137h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.targetprocess.com

Minor September 10, 2026

Search service issue in EU2 cluster

Detected by Pingoru
Sep 10, 2026, 09:40 AM UTC
Resolved
Sep 10, 2026, 02:12 PM UTC
Duration
4h 31m
Affected: EU2 cluster
Timeline · 3 updates
  1. investigating Sep 10, 2026, 09:40 AM UTC

    We are currently investigating this issue.

  2. identified Sep 10, 2026, 01:32 PM UTC

    We have identified the root cause of the search service disruption and applied a mitigation. The service is currently unavailable while it recovers. We are actively monitoring progress and will provide updates as the situation develops.

  3. resolved Sep 10, 2026, 02:12 PM UTC

    The search service has been fully restored. We apologize for any inconvenience caused.

Read the full incident report →

Major July 27, 2026

US Frontdoor authentication errors

Detected by Pingoru
Jul 27, 2026, 05:24 PM UTC
Resolved
Jul 27, 2026, 06:06 PM UTC
Duration
41m
Affected: US clusterUS2 cluster
Timeline · 4 updates
  1. investigating Jul 27, 2026, 05:24 PM UTC

    We are investigating an issue with the IBM Verify service which is resulting in failed authentication through Frontdoor.

  2. investigating Jul 27, 2026, 05:34 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 27, 2026, 05:34 PM UTC

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

  4. resolved Jul 27, 2026, 06:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 10, 2026

Intermittent login difficulty on IBM Support portal

Detected by Pingoru
Jul 10, 2026, 03:49 PM UTC
Resolved
Jul 10, 2026, 05:34 PM UTC
Duration
1h 44m
Timeline · 2 updates
  1. monitoring Jul 10, 2026, 03:49 PM UTC

    The IBMid authentication service was experiencing issues that may prevent some customers from logging in to the IBM Support Portal (support.ibm.com). Customers who are still unable to login and have a critical Severity 1 issue that cannot wait for portal access to be restored should contact IBM Support directly by phone.

  2. resolved Jul 10, 2026, 05:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Performance Degradation / General Slowness on EU2 cluster

Detected by Pingoru
Apr 27, 2026, 08:08 AM UTC
Resolved
Apr 27, 2026, 09:24 AM UTC
Duration
1h 16m
Affected: EU2 cluster
Timeline · 3 updates
  1. investigating Apr 27, 2026, 08:08 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 27, 2026, 08:46 AM UTC

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

  3. resolved Apr 27, 2026, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 22, 2026

Targetprocess unavailable - US cluster

Detected by Pingoru
Apr 22, 2026, 12:41 PM UTC
Resolved
Apr 22, 2026, 04:55 PM UTC
Duration
4h 13m
Affected: US cluster
Timeline · 5 updates
  1. investigating Apr 22, 2026, 12:41 PM UTC

    We are actively investigating the issue. Further updates will be posted shortly.

  2. investigating Apr 22, 2026, 01:44 PM UTC

    We are still investigating the issue and will provide further updates as more information becomes available.

  3. investigating Apr 22, 2026, 02:45 PM UTC

    We are continuing to investigate the issue and believe it may be related to a network problem. Further updates will be provided as we learn more.

  4. monitoring Apr 22, 2026, 03:24 PM UTC

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

  5. resolved Apr 22, 2026, 04:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 16, 2026

Targetprocess Service Interruption on US cluster

Detected by Pingoru
Apr 16, 2026, 07:32 AM UTC
Resolved
Apr 16, 2026, 11:41 AM UTC
Duration
4h 8m
Affected: US cluster
Timeline · 4 updates
  1. investigating Apr 16, 2026, 07:32 AM UTC

    We are currently investigating this issue.

  2. investigating Apr 16, 2026, 09:31 AM UTC

    We are continuing to investigate the issue.

  3. monitoring Apr 16, 2026, 09:39 AM UTC

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

  4. resolved Apr 16, 2026, 11:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

Error Communicating with Custom Quick Filters & Solution Library

Detected by Pingoru
Apr 14, 2026, 06:24 PM UTC
Resolved
Apr 14, 2026, 07:48 PM UTC
Duration
1h 23m
Affected: APAC clusterEU clusterUS clusterEU2 clusterUS2 clusterPOVEU clusterUS3 cluster
Timeline · 3 updates
  1. investigating Apr 14, 2026, 06:24 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 14, 2026, 07:31 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 14, 2026, 07:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

Performance degradation on EU2 cluster

Detected by Pingoru
Mar 16, 2026, 08:09 AM UTC
Resolved
Mar 16, 2026, 12:53 PM UTC
Duration
4h 44m
Affected: EU2 cluster
Timeline · 3 updates
  1. investigating Mar 16, 2026, 08:09 AM UTC

    We're currently investigating performance degradation of some of the Targetprocess services.

  2. monitoring Mar 16, 2026, 10:21 AM UTC

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

  3. resolved Mar 16, 2026, 12:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Error Communicating with Custom Quick Filters

Detected by Pingoru
Feb 23, 2026, 08:31 PM UTC
Resolved
Feb 23, 2026, 09:54 PM UTC
Duration
1h 23m
Affected: APAC clusterEU clusterUS clusterEU2 clusterUS2 clusterPOVEU clusterUS3 cluster
Timeline · 3 updates
  1. investigating Feb 23, 2026, 08:31 PM UTC

    Custom quick filters are currently not loading. A ticket has been opened for further investigation and we will post updates as we have them.

  2. monitoring Feb 23, 2026, 09:17 PM UTC

    We believe the issue blocking communication with the Custom Quick Filters has been resolved. We will monitor to confirm there are no further reports of the issue.

  3. resolved Feb 23, 2026, 09:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 23, 2026

Intermittent Issues with Frontdoor SSO

Detected by Pingoru
Feb 23, 2026, 03:29 PM UTC
Resolved
Feb 24, 2026, 01:26 AM UTC
Duration
9h 56m
Affected: US clusterUS2 clusterUS3 cluster
Timeline · 8 updates
  1. investigating Feb 23, 2026, 03:29 PM UTC

    We are currently investigating an issue where SSO logins are intermittently failing. This is being actively tracked at https://statuspage.ibmcloudsecurity.com/. We will also post updates here as we have them.

  2. identified Feb 23, 2026, 03:43 PM UTC

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

  3. identified Feb 23, 2026, 03:44 PM UTC

    We are continuing to work on a fix for this issue.

  4. investigating Feb 23, 2026, 05:33 PM UTC

    We are continuing to monitor the progress at https://statuspage.ibmcloudsecurity.com/. At this time, only US region is still impacted.

  5. investigating Feb 23, 2026, 07:19 PM UTC

    We are continuing to monitor the progress at https://statuspage.ibmcloudsecurity.com/. At this time, only US region is still impacted.

  6. investigating Feb 23, 2026, 09:55 PM UTC

    Outage reportedly still affecting US clusters intermittently. Issue appears to be resolved for other clusters.

  7. monitoring Feb 24, 2026, 12:17 AM UTC

    A fix has been applied and has stabilised login performance. Please test using a Private or Incognito Window. We will continue to monitor the status.

  8. resolved Feb 24, 2026, 01:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 23, 2026

We are currently experiencing some performance issue in EU2 cluster. We are currently investigating the issue.

Detected by Pingoru
Feb 23, 2026, 08:52 AM UTC
Resolved
Feb 23, 2026, 04:41 PM UTC
Duration
7h 49m
Affected: EU2 cluster
Timeline · 7 updates
  1. investigating Feb 23, 2026, 08:52 AM UTC

    We are currently investigating this issue.

  2. investigating Feb 23, 2026, 09:56 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 23, 2026, 10:53 AM UTC

    We applied database configuration optimizations on the cluster. Performance has improved, but some elevated wait times are still observed. Investigation and monitoring are ongoing.

  4. identified Feb 23, 2026, 12:33 PM UTC

    We have identified the cause as increased database query compilation time. Our engineering team is actively working on a fix and closely monitoring the EU2 cluster.

  5. identified Feb 23, 2026, 02:06 PM UTC

    The issue has been partially mitigated. Performance has improved, but some elevated wait times may still occur. Our team continues to investigate and closely monitor the situation.

  6. monitoring Feb 23, 2026, 03:19 PM UTC

    The issue has now been fully mitigated after the required measures were applied. We will continue to closely monitor system performance.

  7. resolved Feb 23, 2026, 04:41 PM UTC

    Performance has been stable for the past two hours, and the incident is now considered resolved.

Read the full incident report →

Critical February 10, 2026

Targetprocess unavailable

Detected by Pingoru
Feb 10, 2026, 02:08 PM UTC
Resolved
Feb 10, 2026, 02:28 PM UTC
Duration
19m
Affected: APAC clusterEU clusterUS clusterEU2 clusterUS2 clusterPOVEU clusterUS3 cluster
Timeline · 2 updates
  1. investigating Feb 10, 2026, 02:08 PM UTC

    We are investigating the issue.

  2. resolved Feb 10, 2026, 02:28 PM UTC

    The incident has been resolved - Targetprocess Functioning as Expected

Read the full incident report →

Minor January 26, 2026

Performance degradation on US cluster

Detected by Pingoru
Jan 26, 2026, 03:45 PM UTC
Resolved
Jan 27, 2026, 09:47 PM UTC
Duration
1d 6h
Affected: US cluster
Timeline · 4 updates
  1. investigating Jan 27, 2026, 10:51 AM UTC

    We are investigating a performance issue due to high system load, which is causing delays in some system components.

  2. monitoring Jan 27, 2026, 02:10 PM UTC

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

  3. monitoring Jan 27, 2026, 07:15 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 27, 2026, 09:47 PM UTC

    No performance issues observed today - the incident is resolved.

Read the full incident report →

Critical January 9, 2026

Targetprocess Service Interruption-We are currently experiencing a 500 error for accounts hosted on the Dublin (EU2) cluster.

Detected by Pingoru
Jan 09, 2026, 08:10 AM UTC
Resolved
Jan 09, 2026, 09:07 AM UTC
Duration
57m
Affected: EU2 cluster
Timeline · 3 updates
  1. investigating Jan 09, 2026, 08:10 AM UTC

    We are currently investigating this issue.

  2. monitoring Jan 09, 2026, 08:39 AM UTC

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

  3. resolved Jan 09, 2026, 09:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 1, 2025

Slowness and delays in receiving live updates

Detected by Pingoru
Dec 01, 2025, 04:38 PM UTC
Resolved
Dec 01, 2025, 09:50 PM UTC
Duration
5h 11m
Affected: US cluster
Timeline · 3 updates
  1. investigating Dec 01, 2025, 04:38 PM UTC

    We are currently investigating the issue

  2. monitoring Dec 01, 2025, 08:51 PM UTC

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

  3. resolved Dec 01, 2025, 09:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 30, 2025

Report service is unavailable on US and US2 clusters

Detected by Pingoru
Oct 30, 2025, 01:57 PM UTC
Resolved
Oct 30, 2025, 05:33 PM UTC
Duration
3h 35m
Affected: US clusterUS2 cluster
Timeline · 4 updates
  1. investigating Oct 30, 2025, 01:57 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 30, 2025, 02:57 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 30, 2025, 03:56 PM UTC

    We are continuing to investigate this issue.

  4. resolved Oct 30, 2025, 05:33 PM UTC

    The fix has been applied and the issue is now resolved.

Read the full incident report →

Minor October 20, 2025

Global Application Access Disruption

Detected by Pingoru
Oct 20, 2025, 10:27 AM UTC
Resolved
Oct 21, 2025, 05:06 AM UTC
Duration
18h 39m
Timeline · 4 updates
  1. investigating Oct 20, 2025, 10:27 AM UTC

    We are currently monitoring a widespread technical issue that is impacting access to several major applications globally. As a result, you may experience difficulty creating support cases through the IBM Support portal. If you are unable to create a case, please contact us via the Apptio Support hotline: https://www.ibm.com/support/pages/node/7174438

  2. monitoring Oct 20, 2025, 10:50 AM UTC

    The issue has been acknowledged by AWS, and they have been working to resolve: https://health.aws.amazon.com/health/status Latest is that the issue has been fully mitigated, though they continue to work towards a full resolution.

  3. monitoring Oct 20, 2025, 12:52 PM UTC

    We are continuing to monitor for any further issues. AWS continue to work towards a full resolution, and we appear to be experiencing no impact.

  4. resolved Oct 21, 2025, 05:06 AM UTC

    This incident has been resolved

Read the full incident report →

Major September 18, 2025

Report service is unavailable on APAC cluster

Detected by Pingoru
Sep 18, 2025, 02:02 PM UTC
Resolved
Sep 18, 2025, 02:07 PM UTC
Duration
5m
Affected: APAC cluster
Timeline · 2 updates
  1. investigating Sep 18, 2025, 02:02 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 18, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 19, 2025

We are facing performance issues with some of the accounts hosted on EU2(Dublin Datacentre). Our team is actively working on resolving this

Detected by Pingoru
Aug 19, 2025, 11:30 AM UTC
Resolved
Aug 20, 2025, 03:32 AM UTC
Duration
16h 1m
Affected: EU2 cluster
Timeline · 7 updates
  1. investigating Aug 19, 2025, 11:30 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 19, 2025, 12:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 19, 2025, 01:37 PM UTC

    We are continuing to investigate this issue.

  4. investigating Aug 19, 2025, 02:44 PM UTC

    We are continuing to investigate this issue.

  5. investigating Aug 19, 2025, 02:45 PM UTC

    We are continuing to investigate this issue.

  6. monitoring Aug 19, 2025, 03:07 PM UTC

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

  7. resolved Aug 20, 2025, 03:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2025

Global performance issues

Detected by Pingoru
Aug 05, 2025, 12:12 PM UTC
Resolved
Aug 05, 2025, 01:30 PM UTC
Duration
1h 17m
Affected: APAC clusterEU clusterUS clusterEU2 clusterUS2 clusterPOVEU cluster
Timeline · 3 updates
  1. investigating Aug 05, 2025, 12:12 PM UTC

    We are currently working on the issue.

  2. monitoring Aug 05, 2025, 12:36 PM UTC

    This issue has been mitigated, and we are currently monitoring.

  3. resolved Aug 05, 2025, 01:30 PM UTC

    This incident has been resolved, all systems should now be operational.

Read the full incident report →

Minor August 1, 2025

Jira and AzDO integration services - Performance Degradation on US2 cluster

Detected by Pingoru
Aug 01, 2025, 05:39 PM UTC
Resolved
Aug 01, 2025, 08:25 PM UTC
Duration
2h 45m
Affected: US2 cluster
Timeline · 4 updates
  1. investigating Aug 01, 2025, 05:39 PM UTC

    Currently, you may experience a delay in Integrations processing. We apologize for any inconvenience this interruption may have caused you. We are currently investigating this issue.

  2. investigating Aug 01, 2025, 06:39 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 01, 2025, 07:39 PM UTC

    We are continuing to investigate this issue further.

  4. resolved Aug 01, 2025, 08:25 PM UTC

    This incident has been resolved.

Read the full incident report →