Coralogix

Affected: UI - Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-18 09:51 UTC

   We are aware that customers on EU2 are currently unable to load custom dashboards and may see error messages. Our team is actively investigating this issue.

2. identified 2026-10-18 10:27 UTC

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

3. monitoring 2026-10-18 10:41 UTC

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

4. resolved 2026-10-18 10:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Fleet, Processing – Logs, Processing – Metrics, Processing – Event2Metric, Processing – Traces, Processing – RUM, Ingestion – Logs (Frequent Search), Ingestion – Logs (Archive), Ingestion – Metrics, Ingestion – Traces (Frequent Search), Ingestion – Traces (Archive), Alerts – Logs, Alerts – Metrics, Alerts – Traces, Alerts – Flow, Alerts - SLO, Alerts – Notifications, Notification Center, Cases/Incidents

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 10:27 UTC

   We are currently experiencing ingestion delays on our US3 cluster, affecting all pipelines, including Logs, Metrics, and Traces. As a result, related platform features may also be impacted. Our teams are actively investigating the issue and working to implement a resolution. We...

2. identified 2026-10-14 10:53 UTC

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

3. monitoring 2026-10-14 11:05 UTC

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

4. monitoring 2026-10-14 11:11 UTC

   Alerts related features are operational. We are still monitoring for any ingestion delays affecting the cluster.

5. resolved 2026-10-14 11:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 19:12 UTC

   We are seeing elevated lag related to metrics/logs in AP1 region, associated alerts are also affected. Our team is actively working on mitigation.

2. identified 2026-10-06 19:16 UTC

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

3. identified 2026-10-06 19:24 UTC

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

4. identified 2026-10-06 19:33 UTC

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

5. identified 2026-10-06 19:35 UTC

   We have mitigated most of the issues with some lingering lag relative to log alerts. We'll continue to update when possible.

6. monitoring 2026-10-06 19:40 UTC

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

7. resolved 2026-10-06 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 17:37 UTC

   We are observing increased latency and delayed ingestion of data usage metrics in EU2. Our team is aware and actively working on mitigating.

2. identified 2026-09-24 17:40 UTC

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

3. monitoring 2026-09-24 17:49 UTC

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

4. resolved 2026-09-24 18:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 20:03 UTC

   Our team is currently investigating an issue causing log alert delays in the AP2 region. Should you have any questions or require further assistance, please contact us via live chat or email at support@coralogix.com.

2. identified 2026-09-14 20:11 UTC

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

3. resolved 2026-09-14 20:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Processing - Metrics, Processing - Metrics, Processing - Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 18:14 UTC

   We have identified an issue our end that is related specifically to the calculation of the cx_data_usage metrics rather than an actual failure or loss of incoming data. Our engineering team is actively adjusting the service capacity and settings, and the metrics are expected to...

2. identified 2026-09-14 18:22 UTC

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

3. monitoring 2026-09-14 18:27 UTC

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

4. resolved 2026-09-14 18:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Archive)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 20:16 UTC

   We are currently experiencing approximately 1 hour lag for ingesting logs in EU2 env for Archive Tier logs only.

2. identified 2026-09-01 20:18 UTC

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

3. monitoring 2026-09-01 20:23 UTC

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

4. resolved 2026-09-01 20:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs, Alerts - Metrics, Alerts - Traces, Alerts - Flow

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-26 01:00 UTC

   The issue has been identified as related to internal resources, and we are actively working on a fix with an expected recovery time of 30mins.

2. resolved 2026-08-26 01:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Notifications, UI - Incident Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 20:13 UTC

   We are aware of an issue affecting certain features such as Alerts Management on the frontend UI. We are actively investigating and will update as soon as possible.

2. identified 2026-08-25 20:14 UTC

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

3. monitoring 2026-08-25 20:19 UTC

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

4. monitoring 2026-08-25 20:24 UTC

   We can now observe that systems look nominal at this time and are continuing to monitor the situation.

5. resolved 2026-08-25 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs, Alerts - Metrics, Alerts - Notifications

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-25 14:29 UTC

   Between 13:35 and 13:57 UTC, alerts using the "less than" condition were disabled in our EU2 region(team-name.app.eu2.coralogix.com) Also, some customers in this region may have experienced delayed alert evaluations for the other alert conditions.

2. resolved 2026-08-25 14:33 UTC

   The issue has been resolved. If you have any questions, reach out via chat or email at support@coralogix.com.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Collection - Metrics, Processing - Metrics, Ingestion - Metrics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 16:40 UTC

   We are seeing elevated latency and error rates related to metrics ingestion.

2. identified 2026-08-21 16:41 UTC

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

3. monitoring 2026-08-21 16:46 UTC

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

4. identified 2026-08-21 16:56 UTC

   Unfortunately error rates remain elevated, we are continuing to investigate and will update soonest.

5. identified 2026-08-21 17:09 UTC

   Our engineering team have identified possible root causes and are working on mitigating the problem with specific remediation actions. We will continue to update as soon as new information is available.

6. monitoring 2026-08-21 17:37 UTC

   We have executed several remediation actions and should be seeing improvements now and are continuing to monitor the situation.

7. monitoring 2026-08-21 17:49 UTC

   We are observing infrastructure dashboards showing nominal outputs at this time but are continuing to monitor the results. Will update soon.

8. monitoring 2026-08-21 18:14 UTC

   Our team can confirm at this juncture that all signals are green and are continuing to monitor the situation for developments.

9. resolved 2026-08-21 18:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 04:52 UTC

   We are investigating reports of delays in webhook notification delivery on EU1. Our team is actively working to identify and resolve the issue. If you have any questions, reach out via chat or email at support@coralogix.com.

2. identified 2026-08-21 04:59 UTC

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

3. monitoring 2026-08-21 05:13 UTC

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

4. resolved 2026-08-21 05:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-20 17:57 UTC

   We are currently investigating a delay in log alerts within the US2 region. Our engineering team is actively working on resolving the issue as quickly as possible. If you need immediate assistance, please reach out via in-app chat or email us at support@coralogix.com.

2. identified 2026-08-20 18:41 UTC

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

3. monitoring 2026-08-20 18:41 UTC

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

4. resolved 2026-08-20 18:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-11 17:23 UTC

   An issue is currently affecting customers in our US3 region, where custom dashboard links are failing to load and preventing dashboards from displaying. Our R&D team is actively investigating the situation to implement a resolution. We will post regular updates on our status...

2. identified 2026-08-11 17:58 UTC

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

3. monitoring 2026-08-11 18:00 UTC

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

4. resolved 2026-08-11 18:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Collection - Logs, Processing - Logs, Ingestion - Logs (Archive)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-11 08:33 UTC

   Some customers in the US1 region (team-name.app.coralogix.us) may currently experience delays in logs ingestion. The issue has been identified and we are working for a fix. For further assistance or inquiries, please contact us via our in-app chat or email us at...

2. monitoring 2026-08-11 08:45 UTC

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

3. resolved 2026-08-11 09:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-09 15:03 UTC

   We are aware that some customers in the EU1 region may be unable to use the Olly AI observability agent and are receiving errors when attempting to interact with it. Features related to it such as the Query Assistant are also impacted. Our team is actively investigating the...

2. monitoring 2026-08-09 15:12 UTC

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

3. resolved 2026-08-09 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Collection - RUM, Collection - RUM, Collection - RUM, Collection - RUM, Collection - RUM, Collection - RUM, Processing - RUM, Processing - RUM, Processing - RUM, Processing - RUM, Processing - RUM, Processing - RUM, UI - RUM, UI - RUM, UI - RUM, UI - RUM, UI - RUM, UI - RUM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 09:37 UTC

   We are currently investigating an issue affecting Real User Monitoring (RUM). Some customers may be unable to view RUM data or access RUM-related features. Our team is actively working to restore full functionality. If you have any questions, reach out via chat or email at...

2. identified 2026-08-06 09:46 UTC

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

3. monitoring 2026-08-06 09:59 UTC

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

4. resolved 2026-08-06 10:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Processing - Logs, Processing - Logs, UI - Explore, UI - Explore

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-08-05 08:46 UTC

   We experienced a brief period of log query failures affecting Explore → Logs (both v2 and Legacy) in the EU1 and US1 regions. During this time, some customers may have encountered errors when running log queries or accessing archived log data. Our engineering team was actively...

2. monitoring 2026-08-05 08:51 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-08-05 09:01 UTC

   All services are currently up and running. We can confirm that the issue was affecting only EU1 region.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 14:31 UTC

   Our third-party chat application is currently experiencing issues. For status updates, please visit https://www.finstatus.com. We apologize for any inconvenience this may cause. If you need assistance, please send an email to support@coralogix.com.

2. resolved 2026-08-03 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Metrics, Alerts - Metrics, Alerts - Metrics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-03 11:55 UTC

   We have identified an ongoing issue with metric alerts that have the less-than condition in the EU1, EU2 and US1 region. As a result these alert types are not working as intended. Our team is actively working to resolve the issue as quickly as possible. We apologize for the...

2. monitoring 2026-08-03 11:58 UTC

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

3. resolved 2026-08-03 12:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Dashboards, UI - Dashboards, UI - Dashboards, UI - Dashboards

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 17:55 UTC

   Customers may experience widgets failing to load in custom dashboard widgets leveraging dataprime queries. Our team is currently investigating the issue with urgent priority and will update when possible.

2. investigating 2026-07-30 17:56 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-30 18:04 UTC

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

4. monitoring 2026-07-30 18:17 UTC

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

5. resolved 2026-07-30 18:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 16:15 UTC

   Customers in US2 / cx498 may experience degraded performance and intermittent issues with Metrics related dashboards and widgets, we are actively investigating the issue and will relay updates as soon as they become available.

2. identified 2026-07-30 16:32 UTC

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

3. monitoring 2026-07-30 16:39 UTC

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

4. resolved 2026-07-30 16:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Frequent Search)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 18:28 UTC

   Customers in AP1 region may observe a small delay relative to ingestion of Frequent Search (high) tier logs. We are actively working towards resolution. Updates will be relayed as soon as they become available.

2. identified 2026-07-14 18:29 UTC

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

3. monitoring 2026-07-14 18:34 UTC

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

4. resolved 2026-07-14 18:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Frequent Search), Ingestion - Logs (Archive), Alerts - Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 21:50 UTC

   We are currently experiencing an elevated delay in EU2 for logs, this is affecting ingestion and alerts. Issue is being actively worked on and we will provide updates as soon as they are available.

2. identified 2026-07-13 21:54 UTC

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

3. monitoring 2026-07-13 21:56 UTC

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

4. resolved 2026-07-13 22:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Collection - Logs, UI - Explore, UI - Dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-06 07:55 UTC

   Our team is currently working on fixing an issue causing slowness in querying archive data (logs) in the EU2 region. Access to archived data may experience delays, impacting queries and related services. We are working on a solution to restore full functionality as soon as...

2. monitoring 2026-07-06 08:30 UTC

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

3. resolved 2026-07-06 11:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs, Alerts - Metrics, Alerts - Traces, Alerts - Flow, Alerts - Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-29 14:00 UTC

   We are currently working on implementing a fix for an issue which causes delays for case related notifications in the EU1 region. The incidents related notifications are not affected. Our team is actively working to resolve this issue. If you have any questions, reach out via...

2. monitoring 2026-06-29 15:20 UTC

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

3. resolved 2026-06-29 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-26 14:36 UTC

   We are currently experiencing increased processing delays affecting log-based alerts in the AP1 region. As a result, some log-based alerts may be delayed by a short period of time(minutes), particularly those configured with shorter evaluation intervals. Our team is actively...

2. identified 2026-06-26 14:40 UTC

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

3. monitoring 2026-06-26 15:32 UTC

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

4. resolved 2026-06-26 15:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Archive)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-24 18:13 UTC

   We are currently investigating this issue.

2. investigating 2026-06-24 18:17 UTC

   We are currently investigating an issue affecting archive queries in the AP1 region. Users may experience failures when loading dashboards, the Explore screen, or RUM screens. Our team is actively working to resolve this issue. If you have any questions, reach out via chat or...

3. identified 2026-06-24 18:27 UTC

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

4. monitoring 2026-06-24 18:27 UTC

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

5. resolved 2026-06-24 18:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Processing - Metrics, Alerts - Metrics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-23 15:22 UTC

   We are currently experiencing an issue affecting the Service Level Objectives (SLOs) and Recording Rules features in the EU2 region. At this time, metrics generated by recording rules are not being populated with data and the SLO functionality is degraded. As a result, SLO...

2. identified 2026-06-23 15:44 UTC

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

3. monitoring 2026-06-23 16:56 UTC

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

4. resolved 2026-06-23 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Archive)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-22 17:26 UTC

   Our team is currently investigating an issue with logs ingestion in the EU2 region. We are working actively to resolve this matter. Should you require further assistance or have any questions, please reach out via chat or email us at support@coralogix.com.

2. monitoring 2026-06-22 17:35 UTC

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

3. resolved 2026-06-22 17:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - APM

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-22 17:15 UTC

   Our team is currently investigating an issue with APM query in the EU2 region. We are working actively to resolve this matter. Should you require further assistance or have any questions, please reach out via chat or email us at support@coralogix.com.

2. monitoring 2026-06-22 17:20 UTC

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

3. resolved 2026-06-22 17:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Archive)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-09 15:47 UTC

   We are currently investigating an issue affecting archive queries in the EU2 region Users may experience failures when loading dashboards, the Explore screen, or RUM screens. Our team is actively working to resolve this issue. If you have any questions, reach out via chat or...

2. monitoring 2026-06-09 16:05 UTC

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

3. resolved 2026-06-09 16:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs, UI - Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 20:12 UTC

   For customers in EU1 region, we have observed that some custom dashboard widgets are having extended loading times. A subset of alerts may also be affected. Our team is aware and actively looking into it. For additional assistance, please open a support chat or send us an email...

2. identified 2026-06-08 20:13 UTC

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

3. identified 2026-06-08 20:25 UTC

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

4. identified 2026-06-08 20:41 UTC

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

5. monitoring 2026-06-08 20:46 UTC

   A fix has been implemented and we are seeing improvements now, continuing to monitor and actively assess the situation.

6. resolved 2026-06-08 21:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-02 17:34 UTC

   We have identified an issue with our US2 region where dataprime queries generate an error. Our Team is actively working on a fix. If you need assistance or have a question, please send us an email to support@coralogix.com or chat with our support Team.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Collection - RUM, Processing - RUM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 10:14 UTC

   We are currently experiencing an issue affecting the ingestion of RUM data in our EU2 environment. Our engineering teams are actively investigating and working to resolve the issue with the highest priority. We apologize for the inconvenience and will provide further updates as...

2. identified 2026-05-29 10:40 UTC

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

3. monitoring 2026-05-29 10:52 UTC

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

4. resolved 2026-05-29 11:02 UTC

   The incident has been fully resolved, and all previously affected RUM data is now available within the system.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 12:37 UTC

   We are currently experiencing an issue affecting the olly.new web application domain, which is currently inaccessible. Our R&D teams are actively investigating the root cause and working to restore service as quickly as possible. Please note that Olly integrations within...

2. resolved 2026-05-22 13:11 UTC

   Olly.new domain is currently under maintenance. Our service can be further accessed at https://ollyhq.com or through web application integration inside Coralogix Teams. This incident is resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-07 21:47 UTC

   Our team is investigating a delay in case creation in the us1 region (team.coralogix.us). For assistance or more questions, please contact us via chat or email support@coralogix.com.

2. identified 2026-05-07 22:04 UTC

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

3. monitoring 2026-05-07 22:45 UTC

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

4. resolved 2026-05-07 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Logs (Frequent Search)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 18:06 UTC

   Some customers in the US2 region (team-name.app.cx498.coralogix.com) may currently experience delays in data ingestion. Our engineering team is investigating the matter and working toward a resolution. For further assistance or inquiries, please contact us via our in-app chat or...

2. identified 2026-05-05 18:06 UTC

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

3. monitoring 2026-05-05 18:14 UTC

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

4. resolved 2026-05-05 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-04 12:17 UTC

   Some of our customers across various regions may currently be experiencing difficulties logging into their accounts. Our team is fully committed to resolving this matter promptly and expects a solution shortly. For any questions or further assistance, please contact us via email...

Excerpts are shortened. Read the full incident on Coralogix's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 20:00 UTC

   We have identified an issue causing the Coralogix Support Chat application to not load as expected. We are actively monitoring the situation and will restore chat functionality as soon as the issue is resolved. If you require any assistance in the meantime, please contact our...

2. resolved 2026-04-28 21:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Notifications, Alerts - Notifications, Alerts - Notifications, Alerts - Notifications, UI - Authentication / Login, UI - Authentication / Login, UI - Authentication / Login, UI - Authentication / Login

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-27 16:28 UTC

   We are currently investigating an issue causing errors when using the Email Group Webhook for alert notifications in EU1, EU2, US2 and AP1 regions. Our engineering teams are actively investigating this issue with the highest priority. We will provide further updates as soon as...

2. identified 2026-04-27 16:37 UTC

   This issue has been identified to affect email sends from Coralogix, which may affect emailed reports, password reset and invitation emails. Our engineering teams are continuing to investigate this issue. We will provide further updates as soon as more information becomes...

3. monitoring 2026-04-27 16:54 UTC

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

4. resolved 2026-04-27 16:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Live Tail

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 15:09 UTC

   We are currently experiencing lag in LiveTail. Our engineering team is actively investigating and working to resolve the processing backlog. If you have any questions, reach out via chat or email at support@coralogix.com.

2. resolved 2026-04-22 15:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - RUM, UI - RUM, UI - RUM, UI - RUM, UI - RUM, UI - RUM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 14:47 UTC

   We are currently investigating an issue affecting the Real User Monitoring (RUM) feature across the EU1, EU2, US1, US2, AP1 and AP3 regions. At this time, the issue appears to be UI-related, with users encountering a blank page when accessing the RUM section. Our team is...

2. identified 2026-04-20 14:49 UTC

   Our engineering team has identified the issue and is currently implementing a fix.

3. identified 2026-04-20 15:01 UTC

   The Real User Monitoring (RUM) UI functionality has been restored and is now fully operational in the EU1, EU2, AP1, and AP3 regions. Our teams are currently investigating the remaining affected regions, US1 and US2. Further updates will be provided as soon as they become...

4. monitoring 2026-04-20 15:17 UTC

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

5. resolved 2026-04-20 15:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Authentication / Login, UI - Authentication / Login, UI - Authentication / Login

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 15:56 UTC

   We are currently investigating an issue affecting a subset of customers in the EU1 ( .coralogix.com), EU2 ( app.eu2.coralogix.com) and US1 ( .app.coralogix.us) regions. Impacted users are logged in, but seeing the login page when they refresh. Our team is actively working to...

2. monitoring 2026-04-15 16:05 UTC

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

3. resolved 2026-04-15 16:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Alerts - Logs, Alerts - Metrics, Alerts - Traces, Alerts - Flow, Alerts - Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-14 06:21 UTC

   We are currently investigating an issue affecting the alerting pipeline in the EU2 environment. Customers may experience missing or delayed alerts. Our engineering team is actively working to identify the root cause and restore normal alert delivery. We will share updates as...

2. identified 2026-04-14 06:53 UTC

   Our engineering team has identified the issue and is currently implementing a fix

3. monitoring 2026-04-14 06:56 UTC

   A fix has been implemented and we are monitoring the results

4. resolved 2026-04-14 06:58 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Explore

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-13 04:17 UTC

   We are currently experiencing an issue with querying All Logs in AP2. Our team is investigating this as a priority. Searches in Frequent Search are working as expected.

2. identified 2026-04-13 04:30 UTC

   Our engineering team has identified the issue and is currently implementing a fix.

3. resolved 2026-04-13 04:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: Ingestion - Metrics, Ingestion - Metrics, Ingestion - Metrics, Ingestion - Metrics, Ingestion - Metrics, Ingestion - Metrics, Ingestion - Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-04-09 12:48 UTC

   We are currently investigating an issue affecting the metrics ingestion into Coralogix from Azure integrations. This issue may reflect on some customers from all environments. We apologize for the inconvenience and will provide updates as soon as more information becomes...

2. identified 2026-04-09 12:51 UTC

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

3. monitoring 2026-04-09 12:56 UTC

   A fix has been implemented, and we are actively monitoring the results. Metrics ingestion is recovering, and any data impacted during the incident is expected to be backfilled shortly.

4. resolved 2026-04-09 13:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Incident Management, UI - Incident Management, UI - Incident Management, UI - Incident Management, UI - Incident Management, UI - Incident Management, UI - Incident Management

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 07:11 UTC

   We are currently investigating an issue affecting the Cases page. When opening an event (case), some users may encounter a blank page due to a frontend error impacting all Coralogix regions. Please note that this issue is limited to the user interface and does not affect...

2. identified 2026-04-07 07:13 UTC

   Our engineering team has identified the issue and is currently implementing a fix. We will provide further updates on the status as they become available.

3. monitoring 2026-04-07 07:57 UTC

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

4. resolved 2026-04-07 08:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - Explore, UI - Explore, UI - Explore, UI - Explore, UI - Explore, UI - Explore, UI - Explore, UI - Dashboards, UI - Dashboards, UI - Dashboards, UI - Dashboards, UI - Dashboards, UI - Dashboards, UI - Dashboards

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-26 14:05 UTC

   We are currently investigating elevated error rates in our DataPrime query engine across all regions. This may result in intermittent behavior of slower query performance or query failures when viewing dashboards and exploring data. We are sorry for this inconvenience and...

2. identified 2026-03-26 14:16 UTC

   Our engineering team has identified the issue and is currently implementing a fix. We will provide further updates on the status as they become available.

3. identified 2026-03-26 14:32 UTC

   Following further investigation, we have identified that users may experience errors only for some DataPrime queries that include the time period between 13:05 and 14:00 UTC. For all other time ranges, DataPrime queries should operate normally. Our R&D teams are actively working...

4. monitoring 2026-03-26 15:29 UTC

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

5. resolved 2026-03-26 15:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.

Affected: UI - APM, UI - APM, UI - APM, UI - APM, UI - APM, UI - APM, UI - APM

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-19 16:33 UTC

   We are investigating an issue with our APM service catalogue tab in all regions. Our engineering team is actively investigating and working to resolve. If you need assistance or have a question please contact us through chat or send us an email to support@coralogix.com.

2. monitoring 2026-03-19 17:10 UTC

   A fix has been implemented and we are monitoring the results. Teams that saw missing service in the Service Catalog should see relief now.

3. resolved 2026-03-19 17:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Coralogix's status page.