COR Outage History

COR is up right now

COR had 2 outages in the last 2 years totaling 58m of downtime, averaging 0.1 incidents per month.

There were 2 COR outages since September 7, 2026 totaling 58m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.projectcor.com

Minor September 25, 2026

Status: Identified

Detected by Pingoru
Sep 25, 2026, 07:24 PM UTC
Resolved
Sep 25, 2026, 07:36 PM UTC
Duration
11m
Affected: Web (cor.works)MAIASearchAPI (api.projectcor.com)Notifications (Email)
Timeline · 4 updates
  1. identified Sep 25, 2026, 07:24 PM UTC

    ▎ Some users are experiencing intermittent errors when using COR and its integrations. We have identified the cause as an infrastructure configuration change and are applying a fix. We will provide an update as soon as service is fully restored.

  2. identified Sep 25, 2026, 07:34 PM UTC

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

  3. identified Sep 25, 2026, 07:36 PM UTC

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

  4. resolved Sep 25, 2026, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 7, 2026

Degraded performance on the COR web application

Detected by Pingoru
Sep 07, 2026, 12:51 PM UTC
Resolved
Sep 07, 2026, 01:38 PM UTC
Duration
47m
Affected: Web (cor.works)
Timeline · 1 update
  1. resolved Sep 07, 2026, 03:07 PM UTC

    Between 12:51 and 13:38 UTC on September 7, 2026, the COR web application experienced degraded performance for approximately 47 minutes. Most users would have noticed slower page loads, and during part of this window a portion of requests failed and had to be retried — including a brief period of a few minutes when most requests did not complete. The cause was a configuration issue introduced by a recent infrastructure update. It was not related to capacity or traffic levels. Once identified, we shifted traffic to a healthy server and service returned to normal at 13:38 UTC. We have found no indication of data loss, and no customer action is required. We have corrected the configuration and are adding automated checks so this class of issue is caught before it reaches production. We apologize for the disruption.

Read the full incident report →