Nylas outage history

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.

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.

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.

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.

Mitigated - 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: Step 1: Update your Sandbox credentials 1. Sign in to the Nylas Dashboard at https://dashboard.nylas.com. 2. Open your affected Sandbox application. 3. On the Overview or Connectors page, locate the expired Microsoft credential warning and click Update credential . 4. Confirm that the green "Microsoft credential updated" message appears. If you do not see the warning banner, navigate to Connectors , select your Microsoft connector, and save it without making any changes. This will also apply the updated credentials. Step 2: Reauthenticate affected Microsoft accounts (if needed) 1. Click View invalid Microsoft grants in the confirmation banner, or navigate to Grants 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. Additional remediation underway: We are also testing an automated bulk update for existing Sandbox applications to reduce the need for manual credential updates. Any grants that became invalid will still require reauthentication. 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.

Mitigated - 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. Step 1 (Update your Sandbox credentials) should be completed regardless of the additional automated remediation described below. 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 [email protected] 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.

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.

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.

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.

Mitigated - 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.

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.

We are investigating degraded message retrieval and webhook delivery affecting IMAP grants in the EU region. Customers may see messages missing from standard Messages API responses and may not receive expected message webhooks. The underlying IMAP mailboxes and messages remain available. The US region is not affected. Our team is actively investigating the issue and working to restore normal service. We will provide additional information as it becomes available.

We are continuing to investigate this issue.

We have identified an issue affecting Nylas's cached message data for IMAP grants in the EU region. The underlying IMAP mailboxes and messages are unaffected, and the US region is not affected. As a temporary workaround, customers can pass query_imap=true on all Messages API requests for affected IMAP grants. This bypasses the Nylas message cache and retrieves messages directly from the underlying IMAP server. Our team is actively working to restore normal cached message synchronization and webhook delivery. We will provide additional updates as recovery progresses.

We have identified a compatibility issue in Nylas's IMAP synchronization affecting some connected IMAP accounts. Impact is concentrated in the EU region, with substantially more limited impact confirmed in the US region. Multiple IMAP hosting providers may be affected, and we are continuing to validate the full scope. Affected accounts may have missing messages in Nylas API responses and delayed or missing message webhooks. The underlying emails remain available at the email provider. As a temporary workaround, customers can pass query_imap=true on Messages API requests for affected IMAP grants. This bypasses the Nylas message cache and retrieves messages directly from the underlying IMAP server. A fix has been prepared and deployment is underway. As affected accounts resynchronize, customers may receive an increased volume of delayed message.created webhooks, including notifications for messages previously processed. These notifications do not represent duplicate emails. Customers should ensure their applications handle repeated notifications without creating duplicate records or repeating automated actions. We will provide further updates as deployment and recovery progress. Thank you for your patience.

Mitigated - The fix for this issue has been deployed, and affected IMAP accounts are now resynchronizing. We are seeing message synchronization recover and delayed webhooks begin processing as expected. As affected accounts resynchronize, customers may receive an increased volume of delayed message.created webhooks, including notifications for messages previously processed. These notifications do not represent duplicate emails. Customers should ensure their applications handle repeated notifications without creating duplicate records or repeating automated actions. Our current expectation is that missed webhooks will be backfilled automatically as synchronization completes. We are continuing to validate the completeness of that recovery, including messages from the affected period, before confirming full resolution. Impact remains concentrated in the EU region, with substantially more limited impact in the US region. We will continue monitoring recovery closely and provide another update once stability and backfill completion have been confirmed.

IMAP message synchronization and webhook processing have returned to normal operating levels following remediation. We are continuing to monitor service health closely and validate that delayed webhooks from the affected period were fully delivered across affected accounts.

IMAP message synchronization and webhook processing have returned to normal operating levels. We are continuing to monitor service health closely and validate the completeness of delayed webhook delivery across affected accounts before resolving the incident.

IMAP message synchronization and webhook processing have remained at normal operating levels. Our validation indicates that delayed webhooks from the affected period have been delivered and affected accounts have completed recovery. Thank you for your patience while we worked to address this issue.

We are investigating degraded Notetaker join rates affecting some Microsoft Teams meetings in the US region. The EU region and other supported meeting providers are not affected. Our team is actively investigating the issue and working to restore normal join performance. We will provide additional information as it becomes available.

We have identified the issue affecting Notetaker join rates for a limited subset of Microsoft Teams meetings in the US region. The EU region and other supported meeting providers are not affected. Our team is deploying a fix and initial validation indicates it is working as intended. We are continuing deployment and testing while closely monitoring join performance.

We identified a change in Microsoft Teams display-name validation behavior that began affecting a very limited subset of Notetaker joins in the US region today. We have deployed and validated a fix that normalizes affected Notetaker display names before joining Microsoft Teams meetings. Our testing and monitoring confirm that affected Notetakers are now joining successfully and that customer impact has been resolved. The EU region and other supported meeting providers were not affected. Thank you for your patience while we worked to address this issue.

We are seeing elevated error rates affecting message sending, drafts, and message and folder retrieval for a subset of Microsoft-connected accounts in the US and EU regions. Some requests may fail or require retrying. Microsoft is also reporting a service degradation that appears consistent with the behavior we are observing: https://status.cloud.microsoft/ Initial evidence indicates that this issue is related to the ongoing Microsoft service degradation. We are continuing to assess the impact to Nylas customers and will provide additional updates as more information becomes available.

We have confirmed that the elevated error rates are related to an ongoing Microsoft Exchange Online service degradation affecting Microsoft-connected accounts. Microsoft is tracking the incident as EX1464935. Customers with Microsoft-connected accounts may experience failures when sending messages, creating or accessing drafts, or retrieving message and mailbox data in the US and EU regions. Some requests may require retrying. This issue is limited to Microsoft-connected accounts and does not affect other providers. We are continuing to monitor Microsoft's service degradation and its impact to Nylas customers. Microsoft's public service update: https://x.com/MSFT365Status/status/2094455556454920701

According to Microsoft's service health updates, Microsoft has begun deploying broader mitigation for the ongoing Exchange Online service degradation and is reporting gradual recovery across affected services. Microsoft has indicated that mail flow is expected to be among the first areas to recover. We are continuing to monitor the impact to Microsoft-connected Nylas accounts and will provide another update as recovery progresses. This issue remains limited to Microsoft-connected accounts and does not affect other providers.

According to Microsoft's service health updates, mitigation has been deployed for the ongoing Exchange Online service degradation and Microsoft continues to report recovery across affected services. Nylas monitoring confirms that Microsoft-connected message send, draft, and read operations have substantially recovered across both the US and EU regions. The provider-related errors observed during the incident have declined to near-normal levels, and request performance continues to stabilize. We will continue to closely monitor performance and confirm that recovery remains sustained before considering this incident resolved.

According to Microsoft's service health updates, recovery continues across the remaining infrastructure affected by the Exchange Online service degradation, with availability returning across previously impacted scenarios. Nylas monitoring confirms that message send, draft, and read operations for Microsoft-connected accounts are currently operating at normal levels across both the US and EU regions. The Microsoft-related errors observed during the incident have remained near normal levels in the US and continue to decline in the EU. Some residual retry and throttling activity also remains as traffic recovers from the earlier degradation, but it continues to decrease and is not currently causing broader customer-facing impact. We will continue to monitor Microsoft's recovery and Nylas service performance before considering this incident resolved.

Microsoft-connected message send, draft, and read operations have returned to normal operating levels across both the US and EU regions. Nylas monitoring, as well as Microsoft’s service health updates, confirm sustained recovery from the earlier Exchange Online degradation. The Microsoft-related errors observed by Nylas have returned to near-normal levels, customer-facing request success rates remain healthy, and no additional provider-related degradation has emerged. We will continue to monitor Microsoft-connected account performance as part of our normal operations. Thank you for your patience while Microsoft worked to address this issue.

We are investigating an issue with missing or delayed webhooks for Microsoft and Google grants in the US region. EU region and all IMAP and EWS grants for both regions are working correctly.

We are continuing to investigate delayed webhooks. Based on our investigation, we have expanded the scope of the issue to include all providers in both the US and EU regions. We will provide another update as our investigation progresses.

We are working to deploy a fix for the issue causing delayed webhooks across providers in the US and EU regions. We will provide another update as this work progresses.

We are continuing to work on restoring webhook delivery for affected grants. We will provide another update as recovery progresses.

Mitigated - We have recovered the sync state for all affected grants, and webhook delivery has returned to normal levels. Some previously delayed messages are still being processed, and we are closely monitoring the remaining backlog to ensure delivery completes successfully.

All services have returned to normal operations, and webhook latency and delivery volume have returned to expected levels. All affected webhooks were successfully recovered and delivered. Thank you for your patience while we worked to address this issue.

We are experiencing elevated error rates for the /attachment API endpoint affecting EWS grants for on-premises and hosted Microsoft Exchange providers in both the US and EU regions. Other grant types, including Microsoft Graph, Google, and IMAP, are not affected.

Mitigated - We have implemented changes to address the elevated error rates affecting /attachment API requests for Microsoft Exchange (EWS) grants and are seeing recovery. We are continuing to monitor performance to confirm full recovery across both the US and EU regions.

Error rates have returned to normal levels for /attachment API requests affecting Microsoft Exchange (EWS) grants in both the US and EU regions. We are continuing to monitor performance to confirm the issue remains fully resolved.

Error rates for /attachment API requests affecting Microsoft Exchange (EWS) grants remain at normal levels across both the US and EU regions. We are continuing to monitor closely to confirm the issue remains fully resolved.

Error rates for /attachment API requests affecting Microsoft Exchange (EWS) grants have remained at normal levels across both the US and EU regions, and our monitoring confirms that the issue is no longer affecting customers. Thank you for your patience while we worked to address this issue. If you require additional assistance, please contact [email protected].

We have observed a large increase in notification traffic from Microsoft Graph today, which resulted in higher latencies for new and updated messages across providers in the US region. We have made changes to our infrastructure to better handle the increased traffic, and latencies have reduced. We are continuing to monitor performance and investigate the source of the unusually high notification traffic. The EU region is not affected.

Mitigated - Sync latencies for new and updated messages in the US region have returned to normal operating levels following the infrastructure changes implemented earlier. We have mitigated the customer impact and are continuing to monitor performance while we investigate the unusually high notification traffic that contributed to the incident. The EU region remains unaffected.

Sync latencies for new and updated messages in the US region have remained at normal operating levels, and our systems are stable. The changes implemented during the incident have mitigated the impact of the unusually high notification traffic. We will continue to monitor and address that traffic as part of our normal operations, but it is no longer affecting broader message synchronization performance. The EU region was not affected. This incident is now resolved. Thank you for your patience while we worked to address this issue.

We are investigating elevated rates of HTTP 500 responses for the /messages API endpoint affecting IMAP grants in the US region. Some requests may fail as a result. The issue is not affecting grants for other providers, other API endpoints, or the EU region. The overall error rate remains low. We will provide another update as our investigation progresses.

Error rates and request latency for the /messages API endpoint have returned to normal operating levels. We will continue to monitor performance to confirm the mitigation remains effective.

Error rates and request latency for the /messages API endpoint have remained at normal operating levels, and our monitoring confirms that the issue is no longer affecting customers. This incident is now resolved. Thank you for your patience while we worked to address it. If you require additional assistance, please contact [email protected].

Webhook traffic has returned to normal and all systems are operating correctly. Due the time span elapsed since the issue, we are no longer able to accept any additional requests to replay the webhooks. Please reach out to Nylas Support for assistance retrieving items that may still be missing from this time.

We identified an issue that affected the delivery of a small percentage of message webhooks for some Nylas applications in the EU region. The issue primarily occurred between 06:00 and 11:00 UTC on July 24, 2026. Webhook delivery has recovered, and new webhooks are being sent successfully. Nylas applications in the US region were not affected. Customers who would like us to replay message webhooks should contact [email protected] as soon as possible and include their Nylas application IDs, when available. Please note that we cannot replay only the webhooks that were not successfully delivered. A replay will resend all message webhooks from the start of the incident through the time the replay is performed and will generate duplicates. Before requesting a replay, customers should ensure that their systems can safely identify and handle duplicate webhook events. We are continuing to investigate the underlying cause and closely monitor webhook delivery.

Webhook traffic has continued to function normally and all systems are operating correctly. Due to the time elapsed since the issue, we are no longer able to accept additional requests to replay the webhooks. Please reach out to Nylas Support for assistance retrieving items that may still be missing from this period.

We are currently investigating degraded join rates for Notetaker on Zoom meetings (other meeting providers are not affected). We will share updates as we have more information.

We continue to work with our service providers and internal engineering teams to investigate the issue and evaluate potential mitigations. We will provide additional updates as our investigation progresses.

Our engineering teams continue to actively investigate the issue and are pursuing multiple remediation paths in parallel. The measures implemented so far have not resulted in a sustained improvement, and we remain focused on identifying an effective mitigation. We will provide another update as soon as we have meaningful progress to share.

Mitigated - We have deployed changes that have materially improved meeting join success rates. We are continuing to monitor performance closely and are progressively expanding the mitigation while evaluating additional improvements. We will provide another update as this work progresses.

The changes deployed have restored Notetaker meeting join performance for Zoom to normal operating levels, and our monitoring confirms that the issue is no longer affecting customers. We will continue to monitor performance and pursue further improvements as part of our normal operations. This incident is now resolved. Thank you for your patience while we worked to address this issue.

We are investigating reports of some event API calls failing for Google grants. The error messages report issues with the Nylas migration API endpoints. These errors are incorrect and our migration system was shut down long ago. We are investigating why it is triggering. The errors appear limited to Google grants that were migrated from v2 accounts. Deleting and recreating the grant has been identified as a work around to prevent further errors.

We have deployed a fix and the errors are no longer occurring. We are monitoring our API traffic to ensure the errors do not appear.

There have been no further reports of this error and we are closing this incident. Please reach out to support if you have questions or issues.

We are investigating errors affecting retrieval of previously scheduled messages via our API in the US region. Creating and sending scheduled messages is not affected. We will provide updates as we have more information.

We are continuing to investigate this issue.

This incident has been resolved. Retrieval of previously scheduled messages via our API in the US region is now working normally. We apologize for any disruption this may have caused. Please reach out to our support team if you continue to experience any issues.

We are currently experiencing elevated error rates affecting our v3 API and authentication endpoints across the US and EU regions. Some requests may be failing with 500 errors. We have identified the root cause and our engineering team is actively working on a fix. We will provide updates as we make progress.

A fix has been deployed and error rates are returning to normal. We are monitoring the situation closely and will provide a final update once we have confirmed full recovery.

We are continuing to monitor for any further issues.

This incident has been resolved. Error rates have returned to normal across all v3 API and authentication endpoints in the US and EU regions. We apologize for any disruption caused. Please reach out to our support team if you continue to experience any issues.

We are currently investigating reports that the Nylas dashboard is not displaying any logs. We have confirmed that our system is recording the logs. They are just not shown on the Nylas dashboard.

We identified the cause of the issue affecting log visibility in the Nylas Dashboard and have deployed a mitigation. Dashboard logs are now loading normally for customers. We will continue to monitor the service closely while we work with a third-party provider to fully resolve the underlying issue.

We have identified an issue affecting grant creation and authorization requests in our v3 environments (US and EU). Some customers may experience errors when attempting to create or authorize grants. Our Engineering team has identified the likely cause and is currently deploying a hotfix. We will continue monitoring the deployment and will provide the next update within 30 minutes, or sooner if we have meaningful progress to share.

The issue has been resolved, and grant creation and authorization requests are operating normally. Our engineering team identified and corrected an issue introduced by a recent billing system deployment. We have validated recovery and will continue monitoring to ensure ongoing stability. Thank you for your patience during this incident. If you have any questions or concerns, please contact [email protected].

Starting at approximately 8:59 AM PT, our 3rd party provider Oxylabs experienced an outage that is preventing Nylas Notetakers from joining some Zoom and Google Meet meetings. We are working with the provider and deploying internal mitigation steps now

We have deployed mitigation steps while we wait on Oxylabs, and join rates are improving once again. We will continue to monitor and post updates as available.

Oxylabs has fully restored their services, and we are seeing join rates returning to normal levels. We will continue to monitor closely, and working with Oxylabs to ensure this does not happen in the future. Thank you for your patience during this incident. If you have any further questions or concerns, please contact [email protected].

We are investigating sending failures with our Transactional Send (Beta) and Agent Account (Beta) features. The Nylas API is not affected and is still running correctly. This issue is strictly limited to those two beta features.

The incident has been resolved by our third party subprocessor. We will continue to monitor closely.

We are currently investigating elevated latency affecting Gmail realtime (Pub/Sub) event delivery in the US region. Customers may experience delayed webhooks notifications. The issue was initially caused by an expired SSL certificate, which has since been addressed. However, the system has not fully recovered and latency remains elevated. We will provide an update soon.

We have updated our systems and webhooks have returned to normal