- Detected by Pingoru
- Jun 16, 2026, 02:38 AM UTC
- Resolved
- Jun 16, 2026, 02:38 AM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 2 updates
-
investigating Jun 16, 2026, 02:20 AM UTC
Status: Investigating We are investigating elevated 503s on the API. We are actively investigating. Affected components Cortex Public API (Degraded performance)
-
resolved Jun 16, 2026, 02:38 AM UTC
Status: Resolved 503s are resolved. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 09:13 PM UTC
- Resolved
- May 29, 2026, 09:13 PM UTC
- Duration
- —
Affected: Cortex Web ApplicationCortex Public APICortex Ingestions
Timeline · 1 update
-
resolved May 29, 2026, 09:13 PM UTC
Status: Resolved While performing a database migration, we experience a brief loss of availability on the Cortex API for 8 minutes. All services are fully restored. Affected components Cortex Web Application (Operational) Cortex Ingestions (Operational) Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 02:11 PM UTC
- Resolved
- May 22, 2026, 02:11 PM UTC
- Duration
- —
Affected: Cortex Web ApplicationCortex Public APICortex Ingestions
Timeline · 1 update
-
resolved May 22, 2026, 02:11 PM UTC
Status: Resolved 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. Affected components Cortex Web Application (Operational) Cortex Ingestions (Operational) Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 03:21 PM UTC
- Resolved
- Apr 22, 2026, 03:21 PM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 2 updates
-
investigating Apr 22, 2026, 02:33 PM UTC
Status: Investigating We are investigating degraded performance for the API that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Public API (Degraded performance)
-
resolved Apr 22, 2026, 03:21 PM UTC
Status: Resolved The issue with the API has been resolved. Impacted services have returned to normal operation. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 12:45 AM UTC
- Resolved
- Apr 11, 2026, 12:45 AM UTC
- Duration
- —
Affected: Cortex Web Application
Timeline · 3 updates
-
investigating Apr 10, 2026, 08:12 PM UTC
Status: Investigating We are investigating a potential service interruption with workflows that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Web Application (Degraded performance)
-
identified Apr 10, 2026, 09:52 PM UTC
Status: Identified We have identified the issue with workflows and are working to resolve it. Affected components Cortex Web Application (Degraded performance)
-
resolved Apr 11, 2026, 12:45 AM UTC
Status: Resolved The issue with [business components] has been resolved. Impacted services have returned to normal operation. Affected components Cortex Web Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 02:35 PM UTC
- Resolved
- Apr 01, 2026, 02:35 PM UTC
- Duration
- —
Affected: Cortex Web Application
Timeline · 3 updates
-
investigating Apr 01, 2026, 01:47 PM UTC
Status: Investigating We are investigating a service interruption with workflows that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Web Application (Degraded performance)
-
monitoring Apr 01, 2026, 02:27 PM UTC
Status: Monitoring 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. Affected components Cortex Web Application (Degraded performance)
-
resolved Apr 01, 2026, 02:35 PM UTC
Status: Resolved The issue with workflows has been resolved. Impacted services have returned to normal operation. Affected components Cortex Web Application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 05:09 AM UTC
- Resolved
- Mar 25, 2026, 05:09 AM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 3 updates
-
investigating Mar 25, 2026, 03:42 AM UTC
Status: Investigating We are investigating a potential API interruption that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Public API (Degraded performance)
-
monitoring Mar 25, 2026, 03:58 AM UTC
Status: Monitoring API performance is getting back to normal, we are monitoring the situation and will keep this page updated until it's fully resolved. Affected components Cortex Public API (Degraded performance)
-
resolved Mar 25, 2026, 05:09 AM UTC
Status: Resolved The API degradation has been resolved. Impacted services have returned to normal operation. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 03:10 AM UTC
- Resolved
- Mar 24, 2026, 03:10 AM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 2 updates
-
monitoring Mar 24, 2026, 02:23 AM UTC
Status: Monitoring 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. Affected components Cortex Public API (Degraded performance)
-
resolved Mar 24, 2026, 03:10 AM UTC
Status: Resolved The temporary Cortex API degradation is now resoled. All services are operating normally. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 04:11 AM UTC
- Resolved
- Mar 12, 2026, 04:11 AM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 3 updates
-
investigating Mar 12, 2026, 02:10 AM UTC
Status: Investigating We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Public API (Partial outage)
-
monitoring Mar 12, 2026, 02:31 AM UTC
Status: Monitoring 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. Affected components Cortex Public API (Operational)
-
resolved Mar 12, 2026, 04:11 AM UTC
Status: Resolved The issue with Cortex Public API has been resolved. Impacted services have returned to normal operation. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 07:15 PM UTC
- Resolved
- Feb 24, 2026, 07:15 PM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 2 updates
-
investigating Feb 24, 2026, 05:31 PM UTC
Status: Investigating We are investigating a potential Cortex API service interruption that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Public API (Degraded performance)
-
resolved Feb 24, 2026, 07:15 PM UTC
Status: Resolved 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. Affected components Cortex Public API (Operational)
Read the full incident report →
Critical February 24, 2026 - Detected by Pingoru
- Feb 24, 2026, 05:24 PM UTC
- Resolved
- Feb 23, 2026, 10:06 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 01:18 AM UTC
- Resolved
- Feb 20, 2026, 01:18 AM UTC
- Duration
- —
Timeline · 2 updates
-
identified Feb 18, 2026, 09:34 PM UTC
Status: Identified Some customers are experiencing issues with search functionality. We have identified the issue and are working to resolve it.
-
resolved Feb 20, 2026, 01:18 AM UTC
Status: Resolved The issue with search functionality has been resolved, service has returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 01:19 AM UTC
- Resolved
- Feb 12, 2026, 01:19 AM UTC
- Duration
- —
Affected: Cortex Ingestions
Timeline · 2 updates
-
monitoring Feb 11, 2026, 08:42 PM UTC
Status: Monitoring 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. Affected components Cortex Ingestions (Degraded performance)
-
resolved Feb 12, 2026, 01:19 AM UTC
Status: Resolved The issue with increased processing times is now resolved. Impacted services have returned to normal operation. Affected components Cortex Ingestions (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 01:32 AM UTC
- Resolved
- Feb 10, 2026, 01:32 AM UTC
- Duration
- —
Affected: Cortex Web ApplicationCortex Public APICortex Ingestions
Timeline · 3 updates
-
investigating Feb 09, 2026, 09:18 PM UTC
Status: Investigating We are investigating a service disruption with increased latency that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Ingestions (Degraded performance) Cortex Public API (Degraded performance) Cortex Web Application (Degraded performance)
-
monitoring Feb 09, 2026, 09:34 PM UTC
Status: Monitoring The issue with increased latency has been identified and mitigated. We are monitoring the performance of impacted services. We will continue to update this page until it is resolved. Affected components Cortex Ingestions (Operational) Cortex Public API (Operational) Cortex Web Application (Operational)
-
resolved Feb 10, 2026, 01:32 AM UTC
Status: Resolved The issue with increased latency has been resolved. Impacted services have returned to normal operation. Affected components Cortex Public API (Operational) Cortex Web Application (Operational) Cortex Ingestions (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 05:55 AM UTC
- Resolved
- Jan 28, 2026, 05:55 AM UTC
- Duration
- —
Affected: Cortex Public APICortex Ingestions
Timeline · 4 updates
-
investigating Jan 28, 2026, 02:21 AM UTC
Status: Investigating We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Ingestions (Degraded performance) Cortex Public API (Degraded performance)
-
monitoring Jan 28, 2026, 03:28 AM UTC
Status: Monitoring The issue 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. Affected components Cortex Ingestions (Degraded performance) Cortex Public API (Degraded performance)
-
monitoring Jan 28, 2026, 04:31 AM UTC
Status: Monitoring The issue with has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services and will continue to update this page until it is fully resolved. Affected components Cortex Ingestions (Degraded performance) Cortex Public API (Degraded performance)
-
resolved Jan 28, 2026, 05:55 AM UTC
Status: Resolved The backlog has been cleared. Gitops event processing has fully recovered. Affected components Cortex Ingestions (Operational) Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 05:35 PM UTC
- Resolved
- Jan 27, 2026, 05:35 PM UTC
- Duration
- —
Affected: Cortex Public API
Timeline · 3 updates
-
investigating Jan 27, 2026, 03:53 PM UTC
Status: Investigating We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates. Affected components Cortex Public API (Partial outage)
-
monitoring Jan 27, 2026, 04:56 PM UTC
Status: Monitoring We identified the root cause of the List Entities API not returning ownership information and have resolved such. We are actively monitoring the situation to confirm a full resolution. Affected components Cortex Public API (Partial outage)
-
resolved Jan 27, 2026, 05:35 PM UTC
Status: Resolved The issue impacting the List Entities API has been resolved. Services have returned to normal operation. Affected components Cortex Public API (Operational)
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 10:52 PM UTC
- Resolved
- Dec 09, 2025, 11:03 PM UTC
- Duration
- 11m
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 09:42 PM UTC
- Resolved
- Dec 08, 2025, 10:07 PM UTC
- Duration
- 25m
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 02:56 AM UTC
- Resolved
- Dec 01, 2025, 03:04 AM UTC
- Duration
- 8m
Read the full incident report →
Critical December 1, 2025 - Detected by Pingoru
- Dec 01, 2025, 12:59 AM UTC
- Resolved
- Dec 01, 2025, 01:41 AM UTC
- Duration
- 42m
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 01:40 PM UTC
- Resolved
- Nov 19, 2025, 05:22 PM UTC
- Duration
- 3h 41m
Read the full incident report →
- Detected by Pingoru
- Oct 24, 2025, 05:09 AM UTC
- Resolved
- Oct 24, 2025, 05:27 AM UTC
- Duration
- 17m
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 05:11 PM UTC
- Resolved
- Oct 21, 2025, 12:27 PM UTC
- Duration
- 19h 16m
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 03:37 PM UTC
- Resolved
- Sep 25, 2025, 05:54 PM UTC
- Duration
- 2h 17m
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2025, 05:56 PM UTC
- Resolved
- Sep 18, 2025, 11:43 PM UTC
- Duration
- 5h 46m
Read the full incident report →