Cortex Outage History

Cortex is up right now

Pingoru has recorded 39 incidents for Cortex: 37 in the last 12 months and 3 in the last 90 days.

Source: status.cortex.io

39incidents recorded
37last 12 months
3last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Cortex 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 202636 of 720 (1%)
May 202620 of 744 (0%)
June 202626 of 720 (1%)
July 202635 of 744 (1%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 202620 of 744 (0%)
November 202600 of 21 (0%)

Incidents, newest first

Minor October 14, 2026 Temporary Cortex outage –

Started Oct 14, 2026, 04:57 PM UTC· resolved Oct 14, 2026, 04:57 PM UTC

  1. resolved Oct 14, 2026, 04:57 PM UTC

    The Cortex application and API experienced a brief outage for 3 minutes. All services are back to normal.

  2. resolved Oct 14, 2026, 04:57 PM UTC

    The Cortex application and API experienced a brief outage for 3 minutes. All services are back to normal.

Read the full incident report →

Minor October 6, 2026 OpEx Review Inaccessible 1m Cortex Web Application

Started Oct 06, 2026, 04:28 PM UTC· resolved Oct 06, 2026, 04:29 PM UTC

  1. identified Oct 06, 2026, 04:28 PM UTC

    All customers are currently unable to access OpEx Review. We have identified the issue and are working to resolve it.

  2. resolved Oct 06, 2026, 04:29 PM UTC

    The issue with OpEx Review has been resolved.

  3. resolved Oct 06, 2026, 04:29 PM UTC

    The issue with OpEx Review has been resolved.

Read the full incident report →

Minor August 6, 2026 Elevated error rate on Cortex API 56m Cortex Public API

Started Aug 06, 2026, 06:23 PM UTC· resolved Aug 06, 2026, 07:19 PM UTC

  1. investigating Aug 06, 2026, 06:23 PM UTC

    We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

  2. monitoring Aug 06, 2026, 07:04 PM UTC

    Mitigation was deployed to restore the Cortex API to a healthy state. We are still investigating the root cause of this degradation and will continue to post further updates here.

  3. resolved Aug 06, 2026, 07:19 PM UTC

    The degradation of Cortex API is now resolved.

  4. resolved Aug 06, 2026, 07:19 PM UTC

    The degradation of Cortex API is now resolved.

Read the full incident report →

Minor July 27, 2026 Elevated 503s 8m Cortex Public API

Started Jul 27, 2026, 04:02 AM UTC· resolved Jul 27, 2026, 04:11 AM UTC

  1. investigating Jul 27, 2026, 04:02 AM UTC

    We are investigating elevated, intermittent 503s in requests to our public API.

  2. monitoring Jul 27, 2026, 04:07 AM UTC

    No longer seeing 503s. Monitoring.

  3. resolved Jul 27, 2026, 04:11 AM UTC

    No longer seeing 503s.

Read the full incident report →

Minor July 14, 2026 Elevated 502s 2h 33m Cortex Web Application, Cortex Public API, Cortex Ingestions

Started Jul 14, 2026, 08:44 PM UTC· resolved Jul 14, 2026, 11:17 PM UTC

  1. monitoring Jul 14, 2026, 10:08 PM UTC

    For a brief period from 1:44pm to 1:45pm pacific time, we saw elevated 502s across our system. This has since resolved and we are monitoring the performance of impacted services. We will continue to update this page until it is resolved.

  2. resolved Jul 14, 2026, 11:17 PM UTC

    The issue with elevated 502s has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor July 1, 2026 Intermittent degradation on Cortex API 1h 50m Cortex Web Application, Cortex Public API, Cortex Ingestions

Started Jul 01, 2026, 05:30 PM UTC· resolved Jul 01, 2026, 07:20 PM UTC

  1. investigating Jul 01, 2026, 05:30 PM UTC

    We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

  2. resolved Jul 01, 2026, 07:20 PM UTC

    The intermittent elevated latency and errors on Cortex API have been fully resolved.

Read the full incident report →

Minor June 26, 2026 Ownership calculations degraded for some customers 5h 13m Cortex Web Application, Cortex Public API

Started Jun 26, 2026, 02:43 PM UTC· resolved Jun 26, 2026, 07:57 PM UTC

  1. investigating Jun 26, 2026, 02:43 PM UTC

    We are investigating a potential service interruption impacting ownership/member calculations that may impact some customers. Please continue to monitor this page for updates.

  2. identified Jun 26, 2026, 03:08 PM UTC

    Some customers are experiencing issues with ownership calculations. We have identified the issue and are working to refresh ownership across affected customers.

  3. monitoring Jun 26, 2026, 04:57 PM UTC

    The issue with ownership calculations has been resolved and a fix has been implemented. We are monitoring the impacted services and will continue to update this page until we're confident that this is completely resolved.

  4. resolved Jun 26, 2026, 07:57 PM UTC

    The issue impacting ownership calculations has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor June 16, 2026 Elevated 503s on API 18m Cortex Public API

Started Jun 16, 2026, 02:20 AM UTC· resolved Jun 16, 2026, 02:38 AM UTC

  1. investigating Jun 16, 2026, 02:20 AM UTC

    We are investigating elevated 503s on the API. We are actively investigating.

  2. resolved Jun 16, 2026, 02:38 AM UTC

    503s are resolved.

Read the full incident report →

Minor May 29, 2026 Brief API availability degradation – Cortex Web Application, Cortex Public API, Cortex Ingestions

Started May 29, 2026, 09:13 PM UTC· resolved May 29, 2026, 09:13 PM UTC

  1. resolved May 29, 2026, 09:13 PM UTC

    While performing a database migration, we experience a brief loss of availability on the Cortex API for 8 minutes. All services are fully restored.

Read the full incident report →

Minor May 22, 2026 No Scorecard data for all EU/dedicated tenants – Cortex Web Application, Cortex Public API, Cortex Ingestions

Started May 22, 2026, 02:11 PM UTC· resolved May 22, 2026, 02:11 PM UTC

  1. resolved May 22, 2026, 02:11 PM UTC

    Scorecard data stopped updating for all EU and dedicated tenants. No entities appeared on scorecards and rules were not evaluated. The issue has been resolved and impacted services have returned to normal operation.

Read the full incident report →

Minor April 22, 2026 Increased Latency 48m Cortex Public API

Started Apr 22, 2026, 02:33 PM UTC· resolved Apr 22, 2026, 03:21 PM UTC

  1. investigating Apr 22, 2026, 02:33 PM UTC

    We are investigating degraded performance for the API that may impact some customers. Please continue to monitor this page for updates.

  2. resolved Apr 22, 2026, 03:21 PM UTC

    The issue with the API has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor April 10, 2026 Workflows Service Interruption 4h 32m Cortex Web Application

Started Apr 10, 2026, 08:12 PM UTC· resolved Apr 11, 2026, 12:45 AM UTC

  1. investigating Apr 10, 2026, 08:12 PM UTC

    We are investigating a potential service interruption with workflows that may impact some customers. Please continue to monitor this page for updates.

  2. identified Apr 10, 2026, 09:52 PM UTC

    We have identified the issue with workflows and are working to resolve it.

  3. resolved Apr 11, 2026, 12:45 AM UTC

    The issue with [business components] has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor April 1, 2026 Workflow Performance Degradation 47m Cortex Web Application

Started Apr 01, 2026, 01:47 PM UTC· resolved Apr 01, 2026, 02:35 PM UTC

  1. investigating Apr 01, 2026, 01:47 PM UTC

    We are investigating a service interruption with workflows that may impact some customers. Please continue to monitor this page for updates.

  2. monitoring Apr 01, 2026, 02:27 PM UTC

    The issue with workflows has been identified and a fix has been implemented. We are monitoring the performance of impacted services. We will continue to update this page until it is resolved.

  3. resolved Apr 01, 2026, 02:35 PM UTC

    The issue with workflows has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor March 25, 2026 API Degradation 1h 26m Cortex Public API

Started Mar 25, 2026, 03:42 AM UTC· resolved Mar 25, 2026, 05:09 AM UTC

  1. investigating Mar 25, 2026, 03:42 AM UTC

    We are investigating a potential API interruption that may impact some customers. Please continue to monitor this page for updates.

  2. monitoring Mar 25, 2026, 03:58 AM UTC

    API performance is getting back to normal, we are monitoring the situation and will keep this page updated until it's fully resolved.

  3. resolved Mar 25, 2026, 05:09 AM UTC

    The API degradation has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor March 24, 2026 Temporary API Degradation 46m Cortex Public API

Started Mar 24, 2026, 02:23 AM UTC· resolved Mar 24, 2026, 03:10 AM UTC

  1. monitoring Mar 24, 2026, 02:23 AM UTC

    We identified a temporary degradation of the Cortex API service and are actively monitoring the situation to ensure it doesn’t reproduce. We will keep updating this status page until it is fully resolved.

  2. resolved Mar 24, 2026, 03:10 AM UTC

    The temporary Cortex API degradation is now resoled. All services are operating normally.

Read the full incident report →

Minor March 12, 2026 Partial Outage for Cortex Public API 2h Cortex Public API

Started Mar 12, 2026, 02:10 AM UTC· resolved Mar 12, 2026, 04:11 AM UTC

  1. investigating Mar 12, 2026, 02:10 AM UTC

    We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

  2. monitoring Mar 12, 2026, 02:31 AM UTC

    The issue with Cortex Public API has been mitigated. We are monitoring the performance of impacted services. We will continue to update this page until it is resolved.

  3. resolved Mar 12, 2026, 04:11 AM UTC

    The issue with Cortex Public API has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Major March 12, 2026 Partial Outage for Cortex Public API 2h

Started Mar 12, 2026, 02:10 AM UTC· resolved Mar 12, 2026, 04:11 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 24, 2026 Cortex API Performance Degraded 1h 43m Cortex Public API

Started Feb 24, 2026, 05:31 PM UTC· resolved Feb 24, 2026, 07:15 PM UTC

  1. investigating Feb 24, 2026, 05:31 PM UTC

    We are investigating a potential Cortex API service interruption that may impact some customers. Please continue to monitor this page for updates.

  2. resolved Feb 24, 2026, 07:15 PM UTC

    The issue impacting the Cortex API has been mitigated. We'll continue to monitor the performance of the Cortex API and are actively working on adding extra resilience.

Read the full incident report →

Critical February 23, 2026 Cortex API Outage –

Started Feb 23, 2026, 10:06 PM UTC· resolved Feb 23, 2026, 10:06 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 23, 2026 Cortex API Outage 6m Cortex Web Application, Cortex Public API, Cortex Ingestions

Started Feb 23, 2026, 10:00 PM UTC· resolved Feb 23, 2026, 10:06 PM UTC

  1. investigating Feb 23, 2026, 10:00 PM UTC

    We are investigating the issue impacting the Cortex API. We will continue to update this page until it is resolved.

  2. resolved Feb 23, 2026, 10:06 PM UTC

    The issue impacting the Cortex API has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Minor February 18, 2026 Search Functionality Degraded 1d 3h

Started Feb 18, 2026, 09:34 PM UTC· resolved Feb 20, 2026, 01:18 AM UTC

  1. identified Feb 18, 2026, 09:34 PM UTC

    Some customers are experiencing issues with search functionality. We have identified the issue and are working to resolve it.

  2. resolved Feb 20, 2026, 01:18 AM UTC

    The issue with search functionality has been resolved, service has returned to normal operation.

Read the full incident report →

Notice February 18, 2026 Search Functionality Degraded 1d 3h

Started Feb 18, 2026, 09:34 PM UTC· resolved Feb 20, 2026, 01:18 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 18, 2026 Cortex API Performance Degraded 1h 2m Cortex Public API

Started Feb 18, 2026, 06:34 PM UTC· resolved Feb 18, 2026, 07:36 PM UTC

  1. investigating Feb 18, 2026, 06:34 PM UTC

    We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

  2. monitoring Feb 18, 2026, 07:20 PM UTC

    The issue with the Cortex API has been identified and a fix has been implemented. We are monitoring the performance of impacted services. We will continue to update this page until it is resolved.

  3. resolved Feb 18, 2026, 07:36 PM UTC

    The issue with the Cortex API has been resolved. Impacted services have returned to normal operation.

Read the full incident report →

Critical February 18, 2026 Cortex API Performance Degraded 1h 2m

Started Feb 18, 2026, 06:34 PM UTC· resolved Feb 18, 2026, 07:36 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 11, 2026 Data processing backed up across multiple areas 4h 36m Cortex Ingestions

Started Feb 11, 2026, 08:42 PM UTC· resolved Feb 12, 2026, 01:19 AM UTC

  1. monitoring Feb 11, 2026, 08:42 PM UTC

    A service degradation earlier today has caused some processing delays across Scorecards, CQL Reports and Catalog Discovery. The issue has been mitigated and processing is now catching up. We will continue to update this page until it is fully resolved.

  2. resolved Feb 12, 2026, 01:19 AM UTC

    The issue with increased processing times is now resolved. Impacted services have returned to normal operation.

Read the full incident report →