Nylas is operating normally.

This message serves as notification that we are making changes to Nylas' Subprocessors page today

This message serves as notification that the following updates have been made to the Nylas Subprocessors page. The following subprocessor is being added: PostHog You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.

We are investigating elevated rates of HTTP 500 responses for the <tt>/messages</tt> 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 <tt>/messages</tt> 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 <tt>/messages</tt> 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 support@nylas.com.

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.

<b>Mitigated</b> - 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 experiencing elevated error rates for the <tt>/attachment</tt> 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.

<b>Mitigated</b> - We have implemented changes to address the elevated error rates affecting <tt>/attachment</tt> 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 <tt>/attachment</tt> 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 <tt>/attachment</tt> 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 <tt>/attachment</tt> 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 support@nylas.com.

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.

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

This message serves as notification that we are making changes to Nylas' Subprocessors page today

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This message serves as notification that updates have been made to the Nylas Subprocessors page today. You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.

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 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 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 <tt>query_imap=true</tt> 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 <tt>query_imap=true</tt> 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 <tt>message.created</tt> 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.

<b>Mitigated</b> - 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 <tt>message.created</tt> 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 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.

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

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.