Corvic Status - Incident history https://status.corvic.ai Corvic Mon, 20 Oct 2025 20:30:21 +0000 Errors logging into app Type: Incident Duration: 5 hours and 40 minutes Affected Components: App Oct 21, 02:10:02 GMT+0 - Resolved - This incident has been resolved. Oct 20, 20:30:21 GMT+0 - Identified - We have identified an issue with our identity provider which is preventing logins. They are currently investigating \[1\], and we are monitoring their status. \[1\] <https://status.workos.com/incidents/rdz189wnjhyn> Oct 21, 01:04:04 GMT+0 - Monitoring - Our identity provider has rolled out a fix and we are monitoring. Type: Incident

Duration: 5 hours and 40 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>02:10:02</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:30:21</var> GMT+0</small><br><strong>Identified</strong> - We have identified an issue with our identity provider which is preventing logins. They are currently investigating \[1\], and we are monitoring their status. \[1\] <https://status.workos.com/incidents/rdz189wnjhyn>.</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:04:04</var> GMT+0</small><br><strong>Monitoring</strong> - Our identity provider has rolled out a fix and we are monitoring..</p> ]]> Mon, 20 Oct 2025 20:30:21 +0000 https://status.corvic.ai/incident/cmgzlausu04el30uybv8gqo25 https://status.corvic.ai/incident/cmgzlausu04el30uybv8gqo25 Issues logging in Type: Incident Duration: 38 minutes Affected Components: App Oct 10, 16:29:23 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 10, 16:50:59 GMT+0 - Monitoring - A fix has been applied by our login provider. Oct 10, 17:07:32 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 38 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>16:29:23</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>16:50:59</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been applied by our login provider..</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>17:07:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 10 Oct 2025 16:29:23 +0000 https://status.corvic.ai/incident/cmgl2afo002wsvs2to8dr4bli https://status.corvic.ai/incident/cmgl2afo002wsvs2to8dr4bli Elevated timeouts with SSE deployed agents Type: Incident Duration: 9 hours and 17 minutes Affected Components: App Sep 10, 15:50:45 GMT+0 - Resolved - This incident has been resolved. Sep 10, 06:34:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 10, 15:24:00 GMT+0 - Monitoring - We have identified the cause and have applied a fix. We are currently monitoring the fix. Type: Incident

Duration: 9 hours and 17 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:50:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>06:34:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:24:00</var> GMT+0</small><br><strong>Monitoring</strong> - We have identified the cause and have applied a fix. We are currently monitoring the fix..</p> ]]> Wed, 10 Sep 2025 06:34:00 +0000 https://status.corvic.ai/incident/cmfe57uev000dfh91ojrmpekm https://status.corvic.ai/incident/cmfe57uev000dfh91ojrmpekm Errors logging into app Type: Incident Affected Components: App Jul 16, 21:13:00 GMT+0 - Monitoring - Our identity provider has identified the problem and is rolling out a fix. Jul 16, 21:15:00 GMT+0 - Resolved - This incident has been resolved. Jul 16, 20:40:00 GMT+0 - Investigating - We are currently investigating this incident. Jul 16, 20:54:00 GMT+0 - Identified - We have identified that our identity provider is having issues. Jul 16, 21:16:00 GMT+0 - Resolved - This incident has been resolved. Jul 16, 22:42:42 GMT+0 - Postmortem - Mini postmortem: Our identity provider, WorkOS, experienced an issue in its support for custom domains \[1\], which caused issues logging into Corvic. \[1\] <https://status.workos.com/incidents/nq59pqv5z2d2> Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>21:13:00</var> GMT+0</small><br><strong>Monitoring</strong> - Our identity provider has identified the problem and is rolling out a fix..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>21:15:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>20:40:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>20:54:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified that our identity provider is having issues..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>21:16:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>22:42:42</var> GMT+0</small><br><strong>Postmortem</strong> - Mini postmortem: Our identity provider, WorkOS, experienced an issue in its support for custom domains \[1\], which caused issues logging into Corvic. \[1\] <https://status.workos.com/incidents/nq59pqv5z2d2>.</p> ]]> Wed, 16 Jul 2025 20:40:00 +0000 https://status.corvic.ai/incident/cmd6iv1r9004d3njbekds3xah https://status.corvic.ai/incident/cmd6iv1r9004d3njbekds3xah Errors logging into app Type: Incident Duration: 3 hours and 31 minutes Affected Components: App Jun 12, 18:10:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 12, 18:00:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 12, 21:01:00 GMT+0 - Monitoring - GCP us-central1 recovery is ongoing and expected to complete in the hour. Jun 12, 20:05:32 GMT+0 - Monitoring - The upstream cloud provider has applied a fix, and we are seeing services recover. Jun 12, 19:16:19 GMT+0 - Monitoring - We've identified that a cloud provider has been having a major outage. We are monitoring the recovery of their systems. Jun 12, 20:31:27 GMT+0 - Monitoring - We are still monitoring recovery in GCP us-central1. Jun 12, 21:31:28 GMT+0 - Resolved - This incident has been resolved. Jun 13, 15:57:54 GMT+0 - Postmortem - Mini incident report: An incident in GCP \[1\] caused two issues. First, it affected CloudFlare \[2\] which affected Corvic's identity provider and prevented users from logging into Corvic site-wide. Second, Corvic deployments based in GCP were directly affected. The downtime for these deployments was particularly severe as the us-central1 region in GCP took the longest to recover. \[1\] <https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW> \[2\] <https://www.cloudflarestatus.com/incidents/25r9t0vz99rp> Type: Incident

Duration: 3 hours and 31 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:10:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. .</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>21:01:00</var> GMT+0</small><br><strong>Monitoring</strong> - GCP us-central1 recovery is ongoing and expected to complete in the hour..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:05:32</var> GMT+0</small><br><strong>Monitoring</strong> - The upstream cloud provider has applied a fix, and we are seeing services recover..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:16:19</var> GMT+0</small><br><strong>Monitoring</strong> - We've identified that a cloud provider has been having a major outage. We are monitoring the recovery of their systems..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:31:27</var> GMT+0</small><br><strong>Monitoring</strong> - We are still monitoring recovery in GCP us-central1..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>21:31:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>15:57:54</var> GMT+0</small><br><strong>Postmortem</strong> - Mini incident report: An incident in GCP \[1\] caused two issues. First, it affected CloudFlare \[2\] which affected Corvic's identity provider and prevented users from logging into Corvic site-wide. Second, Corvic deployments based in GCP were directly affected. The downtime for these deployments was particularly severe as the us-central1 region in GCP took the longest to recover. \[1\] <https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW> \[2\] <https://www.cloudflarestatus.com/incidents/25r9t0vz99rp>.</p> ]]> Thu, 12 Jun 2025 18:00:00 +0000 https://status.corvic.ai/incident/cmbtr2c3a005nxlonwjaruu5m https://status.corvic.ai/incident/cmbtr2c3a005nxlonwjaruu5m Test incident Type: Incident Affected Components: App Apr 3, 18:13:41 GMT+0 - Resolved - Incident resolved. A summary of the investigation will be posted in 7 days. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>18:13:41</var> GMT+0</small><br><strong>Resolved</strong> - Incident resolved. A summary of the investigation will be posted in 7 days..</p> ]]> Thu, 3 Apr 2025 18:13:41 +0000 https://status.corvic.ai/incident/cm91ocqnt0001ksm0aepozl7u https://status.corvic.ai/incident/cm91ocqnt0001ksm0aepozl7u