Outage affecting 'Log in with Email'

Incident Report for CVaaS

Postmortem

Incident Report: Login By Email Service Outage - January 30th, 2026

On January 30, 2026, CloudVision as-a-Service experienced a service outage affecting the "Login By Email" functionality lasting 2 hours and 36 minutes. During this window, customers attempting to access their accounts using Login By Email failed to receive the invitation emails. This incident was isolated strictly to the Login By Email service; SSO and SAML based login remained fully operational.

There was no data loss or compromise of customer information. This outage was not the result of a security breach, unauthorized intrusion, or any malicious activity.

Root Cause

Our investigation identified a gap in monitoring for a critical third-party integration. Because this specific telemetry was missing, early warning signals were missed, leading to the eventual service disruption. Additionally, we identified internal process failures that contributed to the duration of the outage.

Our Response

Internal escalation protocols successfully engaged subject matter experts within 30 minutes of the first reported case. Initial delays in resolution were primarily due to various process failures including delays in required coordination with third party vendor. We are implementing the missing monitoring triggers for third-party integrations to ensure early detection, as well as reviewing our processes as part of various fixes we are addressing.

We understand that any service disruption is impactful. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again.

Thank you for using CloudVision as-a-Service.

Posted Feb 05, 2026 - 22:03 UTC

Resolved

Login by email is functional again. We apologize for this disruption and will be following up with a postmortem.
Posted Jan 30, 2026 - 16:05 UTC

Investigating

We are aware of an issue with our email system, and the 'Log in with Email' is currently unavailabe.

We have identified the cause and are working on a mitigation.
Posted Jan 30, 2026 - 14:36 UTC
This incident affected: us-central1-a (Login), us-central1-c (Login), euwest-2 (Login), apnortheast-1 (Login), ausoutheast-1 (Login), na-northeast1-b (Login), uk-1 (Login), us-central1-b (Login), india-1 (Login), and us-4 (Login).