Coralogix · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Coralogix status

Coralogix · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

Scheduled Maintenance: RUM Artifacts Database

As part of our ongoing efforts to keep the Coralogix platform secure, stable and up to date, we will be performing scheduled maintenance on the database supporting our RUM artifacts pipeline. Regions: All regions Start Time: Tuesday, September 22, 2026, 08:00 UTC Scheduled Duration: Approximately 4 hours Potentially Affected Components: RUM artifacts ingestion and processing (source maps, React Native source maps, dSYM files, ProGuard files, Dart symbols) Expected Impact: During the maintenance window, newly uploaded RUM artifacts will be buffered, and their ingestion and processing will be delayed. RUM data collection, error monitoring, and querying of already-processed artifacts are not affected and continue to operate as normal. Recovery is automatic once the maintenance completes - buffered artifacts will be processed and catch up shortly after the window ends. No data loss is expected and no action is required on your part. Our engineering team will be closely monitoring the

Status scheduled Starts Ends Updated

Component health

Reported
262
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 262 reported components across 8 source groups · bounded/truncated source projection.
Collection - Logs Group: EU1 Operational
Collection - Logs Group: EU2 Operational
Collection - Logs Group: US1 Operational
Collection - Logs Group: US2 Operational
Collection - Logs Group: AP1 Operational
Collection - Logs Group: AP2 Operational
Collection - Logs Group: AP3 Operational
Collection – Logs Group: US3 Operational
Collection - Metrics Group: EU1 Operational
Collection - Metrics Group: EU2 Operational
Collection - Metrics Group: US1 Operational
Collection - Metrics Group: US2 Operational
Collection - Metrics Group: AP1 Operational
Collection - Metrics Group: AP2 Operational
Collection - Metrics Group: AP3 Operational
Collection – Metrics Group: US3 Operational
Collection - Traces Group: EU1 Operational
Collection - Traces Group: EU2 Operational
Collection - Traces Group: US1 Operational
Collection - Traces Group: US2 Operational
Showing 20 of 100 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 135.5 ms feed latency
Operational
HTTP 200 · 263.06 ms feed latency
Operational
HTTP 200 · 207.53 ms feed latency
Operational
HTTP 200 · 253.87 ms feed latency
Operational
HTTP 200 · 257.72 ms feed latency
Operational
HTTP 200 · 270.39 ms feed latency
Operational
HTTP 200 · 397.57 ms feed latency
Operational
HTTP 200 · 334.9 ms feed latency
Operational
HTTP 200 · 211.55 ms feed latency
Operational
HTTP 200 · 193.73 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
156.3 ms