Authentication Issue - 500 Error and Email/Calendar Sync Failures

Incident Summary

Between July 2, 2026, and July 8, 2026, Some customers experienced intermittent failures affecting email and calendar services. The primary impacts included errors when sending or syncing emails and occasional "500 errors" during login. These issues were caused by a technical regression in the underlying runtime environment (Node.js) that handles outbound connections to third-party services.

For a subset of customers using specific email integration settings, the connection instability caused the system to incorrectly perceive a successful email send as a failure. This triggered an automated retry mechanism, which in some cases resulted in a "retry loop" where the same communication was re-sent to recipients at regular intervals until the connection was stabilized.

Detection

The issue was identified following reports of intermittent service disruptions. Our support and engineering teams conducted a thorough investigation into these reports, identifying a specific pattern of connection failures within our system logs. Further analysis confirmed that the impact began on approximately July 2, 2026, following a routine update to our service infrastructure.

Root Cause

The root cause was a defect in a specific version of Node.js (version 24.17.0), the software environment used to run our services. This version contained a flaw in how it managed "keep-alive" connections—reusable connections used to communicate with external services. Under certain conditions, the software would prematurely close these connections before a task was completed, resulting in failed email sends and data sync errors.

Resolution

To resolve the issue, our engineering team performed the following steps:

• Identification: Correlated the "Premature close" errors to a known regression in the Node.js runtime.
• Upgrade: Updated our base system images to Node.js version 24.18.0, which contains the official fix for this connection issue.
• Deployment: Rebuilt and redeployed critical services (including email and calendar components) on the corrected version.
• Verification: Confirmed that connection errors ceased and service stability returned to normal levels on July 8, 2026.

Preventative Measures

To prevent similar issues in the future, we are implementing the following improvements:

• Version Pinning: We have updated our build process to ensure we deploy only versions that have been fully verified.
• Enhanced Monitoring: We are adding specific alerts for outbound connection errors to detect and respond to similar communication failures more rapidly.
• Automated Testing: We are implementing new synthetic checks for email and calendar synchronization to proactively identify issues before they impact customers.
• Improved Visibility: We are updating our internal dashboards to provide better visibility into the exact software versions running in our production environment to speed up future diagnoses.