Corvic - Notice history

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

We have identified that our identity provider is having issues.

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

We are still monitoring recovery in GCP us-central1.

The upstream cloud provider has applied a fix, and we are seeing services recover.

We've identified that a cloud provider has been having a major outage. We are monitoring the recovery of their systems.