Is Nylas v3 Down?

Microsoft API connectivity has returned to normal operating levels, and Nylas has confirmed that email and calendar synchronization and webhook processing have recovered across the US and EU regions. The significant processing backlog accumulated during Microsoft's service disruption has been addressed, and remaining synchronization delays have decreased to near-normal levels. We will continue monitoring Microsoft integrations for any residual issues. Microsoft Status Page: https://status.cloud.microsoft/ --- [2026-11-13T05:51:39.426-08:00] (monitoring) <b>Mitigated</b> - Microsoft API connectivity has continued to improve, and Nylas API error rates and request throughput have returned to near-normal levels across the US and EU regions. However, we are still processing a significant backlog of Microsoft email and calendar notifications accumulated during the disruption. Customers may continue to experience delays in email and calendar synchronization and associated webhook delivery while this backlog is cleared. Our team is actively monitoring recovery progress and will provide further updates as the situation evolves. Microsoft Status Page: https://status.cloud.microsoft/ --- [2026-11-13T04:24:25.613-08:00] (monitoring) We are seeing significant recovery in Microsoft's services, with Nylas API request success rates and throughput for Microsoft integrations returning to normal operating levels. While Microsoft has not yet officially resolved its incident, our monitoring indicates that the impact on Nylas services has substantially subsided. We are continuing to monitor email and calendar synchronization, webhook delivery, and any remaining processing backlogs across the US and EU regions before considering this incident fully resolved. Microsoft Status Page: https://status.cloud.microsoft/ --- [2026-11-12T10:59:40.713-08:00] (identified) Microsoft has acknowledged that they have an incident regarding their systems that Nylas uses to communicate for Microsoft grants. At this time, Webhooks and Nylas API calls regarding Microsoft grants may not succeed or have significant delays. All other providers, including on-premise Exchange, are not affected. Webhooks regarding Microsoft grants that are not triggering will fire correctly once communication to the Microsoft services has been restored. We are continuing to track this incident to ensure our services will resume normal operation as soon as Microsoft has resolved their issues. Microsoft status page: https://status.cloud.microsoft/ --- [2026-11-12T10:29:59.167-08:00] (investigating) We are investigating a widespread issue affecting Microsoft grants in the US and EU regions. This appears to be caused by an issue on Microsoft's side, as requests to Microsoft Graph are failing or responding slowly, and we are receiving significantly fewer change notifications from Microsoft than usual. Some customers may experience errors when sending messages, errors or slower responses on email, calendar, and contacts API requests, and webhook notifications for new or updated data arriving later than expected or not at all. Email, calendar, and contacts data may also take longer than usual to sync. Google, IMAP, and other providers are not affected. We are monitoring the situation closely and will provide additional information as it becomes available. More details here about the Microsoft outage: https://status.cloud.microsoft/

The automated credential update has been successfully completed for affected Microsoft / Office 365 Sandbox applications in both the US and EU regions. Microsoft authentication using Nylas-provided shared credentials has been restored. <b>No manual credential updates are required.</b> <b>Important:</b> Any Microsoft grants that became invalid during the incident will still require reauthentication through your application's normal Hosted Authentication flow. You can identify these accounts in the Nylas Dashboard under <b>Grants</b> by filtering for Provider = Microsoft and Status = Invalid. Existing valid grants require no action. Production applications and applications using their own Microsoft Azure credentials were not affected. Thank you for your patience while we worked to resolve this issue. If you require additional assistance, please contact support@nylas.com. --- [2026-10-23T14:04:50.045-07:00] (identified) <b>Mitigated</b> - The fix for Microsoft / Office 365 authentication failures affecting Sandbox applications using Nylas-provided shared credentials remains available. Affected customers can restore authentication by following the instructions in our previous update. <b>Step 1 (Update your Sandbox credentials) should be completed regardless of the additional automated remediation described below.</b> Any Microsoft grants that became invalid will still require reauthentication. We have successfully completed testing of an additional automated credential update, which is planned for Monday, October 26, to further address affected existing Sandbox applications. If you are still experiencing authentication issues, please follow the instructions in our previous update or contact support@nylas.com for assistance. Production applications and applications using their own Microsoft Azure credentials remain unaffected. We will provide a final update once the remaining remediation work is complete. --- [2026-10-22T08:53:39.847-07:00] (identified) <b>Mitigated</b> - We have deployed a fix for Microsoft / Office 365 authentication failures affecting Sandbox applications using Nylas-provided shared credentials. Affected customers can now restore authentication using the following steps: <b>Step 1: Update your Sandbox credentials</b> 1. Sign in to the Nylas Dashboard at https://dashboard.nylas.com. 2. Open your affected Sandbox application. 3. On the <b>Overview</b> or <b>Connectors</b> page, locate the expired Microsoft credential warning and click <b>Update credential</b>. 4. Confirm that the green "Microsoft credential updated" message appears. If you do not see the warning banner, navigate to <b>Connectors</b>, select your <b>Microsoft</b> connector, and save it without making any changes. This will also apply the updated credentials. <b>Step 2: Reauthenticate affected Microsoft accounts (if needed)</b> 1. Click <b>View invalid Microsoft grants</b> in the confirmation banner, or navigate to <b>Grants</b> and filter by Provider = Microsoft and Status = Invalid. 2. Reauthenticate any invalid grants using your application's normal Hosted Authentication flow. Existing valid connections do not require reauthentication, and new Microsoft accounts can connect normally once the credentials are updated. <b>Additional remediation underway:</b> We are also testing an automated bulk update for existing Sandbox applications to reduce the need for manual credential updates. <b>Any grants that became invalid will still require reauthentication.</b> Production applications and applications using their own Microsoft Azure credentials remain unaffected. We will provide a final update once the remaining remediation work is complete. --- [2026-10-22T06:59:35.328-07:00] (identified) Deployment of the fix for existing affected Sandbox applications is progressing, and our Engineering team is now completing final testing and validation. Once testing is complete, we will provide additional instructions for affected customers, including any steps required to restore Microsoft authentication. Production applications and applications using their own Microsoft Azure credentials remain unaffected. --- [2026-10-22T04:58:11.347-07:00] (identified) We have identified an expired credential affecting Microsoft / Office 365 authentication for Sandbox applications using Nylas-provided shared credentials. Updated credentials have been deployed for newly created Sandbox applications, and we are now deploying a fix for existing affected Sandbox applications. Once available, affected users may need to refresh their credentials in the Nylas Dashboard and re-authenticate any impacted Microsoft accounts. This issue is limited to Sandbox applications using Nylas shared Microsoft credentials. Production applications and applications using their own Microsoft Azure credentials are not affected. We will provide another update as the fix is rolled out. --- [2026-10-22T05:04:32.750-07:00] (investigating) We have identified an expired credential affecting Microsoft / Office 365 authentication for Sandbox applications using Nylas-provided shared credentials. Replacement credentials have been deployed for newly created Sandbox applications. Our Engineering team is continuing work to restore authentication functionality for existing Sandbox applications that may still be affected. Production applications, applications using their own Microsoft Azure credentials, and existing active connections remain unaffected. We will provide additional updates as remediation progresses. --- [2026-10-22T05:03:56.158-07:00] (investigating) We are investigating Microsoft / Office 365 authentication failures affecting Sandbox applications in the US and EU regions that use Nylas-provided shared credentials. Affected users may encounter errors when connecting new Microsoft accounts or re-authenticating existing accounts. Production applications, Sandbox applications using their own Microsoft Azure credentials, and existing active connections are not affected. Our Engineering team is actively working to restore normal authentication functionality.

IMAP synchronization has returned to normal operating levels across the US and EU regions. Our monitoring confirms that affected grants have recovered and previously missed message activity and associated webhooks have been processed. Customers are no longer affected by this incident. Thank you for your patience while we worked to address this issue. --- [2026-09-17T07:23:19.329-07:00] (monitoring) <b>Mitigated</b> - The remediation has been fully deployed across the US and EU regions, and IMAP synchronization and error rates have returned close to normal operating levels. Some previously affected grants may still be catching up on messages missed during the incident. We are continuing to monitor recovery closely and validate that synchronization remains stable before resolving the incident. --- [2026-09-17T06:48:22.118-07:00] (monitoring) We identified an issue in IMAP message processing that could cause synchronization to stop when certain messages were encountered, resulting in 404 responses when those messages were retrieved by ID. A remediation has now been fully deployed across the US and EU regions. Message synchronization and success rates are recovering, and we are continuing to validate stability before resolving the incident. --- [2026-09-17T06:03:43.022-07:00] (identified) We have identified an issue in IMAP message processing that can cause synchronization to stop when certain messages are encountered, resulting in 404 responses when those messages are retrieved by ID. Our team is actively working on remediation and validating the appropriate recovery path. We will provide another update as this work progresses and we confirm recovery. --- [2026-09-17T05:43:53.408-07:00] (investigating) We are investigating elevated 404 errors when retrieving specific messages via the Messages API for IMAP grants in the US and EU regions. Some messages that exist in the provider mailbox may return a 404 response when retrieved by ID. Our team is actively investigating the issue and working to restore normal message retrieval. We will provide additional information as it becomes available.