# Coralogix in January 2023: incidents, uptime and changes

> Coralogix in January 2023: 3 incidents on its status page (1 major or critical), 99.81% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Coralogix’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/coralogix/2023/01
Last updated: 2023-02-01T00:00:00Z

- Incidents posted: 3 (major/critical: 1) · Maintenance: 1
- By vendor impact label: major 1, minor 1, none 1
- Uptime (vendor-reported): 99.81% free of major/critical incidents, 99.54% free of any incident; outage time 1 h 23 min, incident time 3 h 24 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2022](https://rewindex.com/company/coralogix/2022/12.md) · Next: [February 2023](https://rewindex.com/company/coralogix/2023/02.md) · [All months](https://rewindex.com/company/coralogix/reports.md) · [Coralogix](https://rewindex.com/company/coralogix.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Customers that are running on eu-west-1 (team.coralogix.com) might experience delays with triggering alerts and L2M creation](https://rewindex.com/company/coralogix/incidents/t16113jzxych.md) | major | 2023-01-16 10:30 UTC | 2023-01-16 11:53 UTC | 1.4 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Delays in data transfer - USA cluster customers](https://rewindex.com/company/coralogix/incidents/dxqhnfqsdjsg.md) | minor | 2023-01-15 07:38 UTC | 2023-01-15 09:39 UTC | 2.0 h | resolved |
| [Customers that are running on eu-west-1 (team.coralogix.com) might experience delays with triggering alerts and L2M creation](https://rewindex.com/company/coralogix/incidents/t16113jzxych.md) | major | 2023-01-16 10:30 UTC | 2023-01-16 11:53 UTC | 1.4 h | resolved |
| [Customers that are running on eu-west-1 (team.coralogix.com) might experience delays with triggering alerts and L2M creation](https://rewindex.com/company/coralogix/incidents/03b6hbc9tgng.md) | none | 2023-01-19 07:30 UTC | 2023-01-19 07:46 UTC | 16 min | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] The option of connecting NEW S3 buckets from other regions than the Coralogix account will be disabled starting January 15th, 2023](https://rewindex.com/company/coralogix/incidents/s7727y4d1cgq.md) | maintenance | 2023-01-15 07:00 UTC | 2023-01-15 07:05 UTC | 5 min | resolved |

## Cite this

Coralogix posted 3 status incidents in January 2023 (1 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/coralogix/2023/01
- Citation: Coralogix, “Coralogix in January 2023” (2023-01-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/coralogix/2023/01 (CC BY 4.0).
- Markdown link: `[Coralogix: Coralogix in January 2023 (2023-01-01)](https://rewindex.com/company/coralogix/2023/01)`


---
Canonical: https://rewindex.com/company/coralogix/2023/01 · Markdown: https://rewindex.com/company/coralogix/2023/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T13:55:54.485Z