Nylas Outage History

Started Oct 22, 2026, 10:08 AM UTC· resolved Oct 26, 2026, 05:31 PM UTC

1. investigating Oct 22, 2026, 10:08 AM UTC

   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.

2. investigating Oct 22, 2026, 11:07 AM UTC

   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.

3. identified Oct 22, 2026, 11:58 AM UTC

   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.

4. identified Oct 22, 2026, 01:59 PM UTC

   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.

5. identified Oct 22, 2026, 03:53 PM UTC

   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.

6. identified Oct 23, 2026, 09:04 PM UTC

   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.

7. resolved Oct 26, 2026, 05:31 PM UTC

   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. No manual credential updates are required. Important: 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 Grants 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 [email protected].

Read the full incident report →

Started Sep 17, 2026, 12:31 PM UTC· resolved Sep 17, 2026, 02:59 PM UTC

1. investigating Sep 17, 2026, 12:31 PM UTC

   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.

2. identified Sep 17, 2026, 01:03 PM UTC

   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.

3. monitoring Sep 17, 2026, 01:48 PM UTC

   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.

4. monitoring Sep 17, 2026, 02:23 PM UTC

   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.

5. resolved Sep 17, 2026, 02:59 PM UTC

   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.

Read the full incident report →

Started Sep 10, 2026, 12:28 PM UTC· resolved Sep 10, 2026, 06:37 PM UTC

1. investigating Sep 10, 2026, 12:28 PM UTC

   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.

2. investigating Sep 10, 2026, 12:35 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 10, 2026, 01:08 PM UTC

   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.

4. identified Sep 10, 2026, 02:33 PM UTC

   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.

5. identified Sep 10, 2026, 02:57 PM UTC

   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.

6. identified Sep 10, 2026, 04:28 PM UTC

   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.

7. monitoring Sep 10, 2026, 05:10 PM UTC

   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.

8. resolved Sep 10, 2026, 06:37 PM UTC

   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.

Read the full incident report →

Started Sep 04, 2026, 06:34 PM UTC· resolved Sep 04, 2026, 09:47 PM UTC

1. investigating Sep 04, 2026, 06:34 PM UTC

   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.

2. identified Sep 04, 2026, 08:15 PM UTC

   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.

3. resolved Sep 04, 2026, 09:47 PM UTC

   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.

Read the full incident report →

Started Aug 31, 2026, 09:39 PM UTC· resolved Sep 01, 2026, 01:30 PM UTC

1. investigating Aug 31, 2026, 09:39 PM UTC

   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.

2. identified Aug 31, 2026, 10:25 PM UTC

   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

3. identified Sep 01, 2026, 12:51 AM UTC

   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.

4. monitoring Sep 01, 2026, 02:32 AM UTC

   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.

5. monitoring Sep 01, 2026, 11:13 AM UTC

   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.

6. resolved Sep 01, 2026, 01:30 PM UTC

   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.

Read the full incident report →

Started Aug 19, 2026, 04:11 PM UTC· resolved Aug 19, 2026, 09:34 PM UTC

1. investigating Aug 19, 2026, 04:11 PM UTC

   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.

2. investigating Aug 19, 2026, 04:53 PM UTC

   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.

3. identified Aug 19, 2026, 05:26 PM UTC

   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.

4. identified Aug 19, 2026, 06:01 PM UTC

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

5. monitoring Aug 19, 2026, 08:20 PM UTC

   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.

6. resolved Aug 19, 2026, 09:34 PM UTC

   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.

Read the full incident report →

Started Aug 14, 2026, 02:15 PM UTC· resolved Aug 14, 2026, 05:21 PM UTC

1. investigating Aug 14, 2026, 02:15 PM UTC

   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.

2. monitoring Aug 14, 2026, 02:39 PM UTC

   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.

3. monitoring Aug 14, 2026, 03:02 PM UTC

   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.

4. monitoring Aug 14, 2026, 05:13 PM UTC

   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.

5. resolved Aug 14, 2026, 05:21 PM UTC

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

Read the full incident report →

Started Aug 11, 2026, 07:53 PM UTC· resolved Aug 11, 2026, 10:16 PM UTC

1. monitoring Aug 11, 2026, 07:53 PM UTC

   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.

2. monitoring Aug 11, 2026, 08:12 PM UTC

   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.

3. resolved Aug 11, 2026, 10:16 PM UTC

   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.

Read the full incident report →

Started Aug 06, 2026, 02:37 PM UTC· resolved Aug 06, 2026, 06:30 PM UTC

1. investigating Aug 06, 2026, 02:37 PM UTC

   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.

2. monitoring Aug 06, 2026, 04:36 PM UTC

   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.

3. resolved Aug 06, 2026, 06:30 PM UTC

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

Read the full incident report →

Started Jul 24, 2026, 09:30 PM UTC· resolved Jul 24, 2026, 09:30 PM UTC

1. monitoring Jul 24, 2026, 04:59 PM UTC

   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.

2. resolved Jul 24, 2026, 09:30 PM UTC

   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.

Read the full incident report →

Started Jul 24, 2026, 09:25 PM UTC· resolved Jul 24, 2026, 09:25 PM UTC

1. resolved Jul 24, 2026, 09:25 PM UTC

   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.

Read the full incident report →

Started Jul 17, 2026, 02:32 PM UTC· resolved Jul 23, 2026, 08:54 PM UTC

1. investigating Jul 17, 2026, 02:32 PM UTC

   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.

2. investigating Jul 17, 2026, 05:21 PM UTC

   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.

3. investigating Jul 17, 2026, 08:32 PM UTC

   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.

4. monitoring Jul 23, 2026, 04:09 PM UTC

   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.

5. resolved Jul 23, 2026, 08:54 PM UTC

   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.

Read the full incident report →

Started Jul 07, 2026, 03:03 PM UTC· resolved Jul 07, 2026, 05:17 PM UTC

1. investigating Jul 07, 2026, 03:03 PM UTC

   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.

2. monitoring Jul 07, 2026, 04:58 PM UTC

   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.

3. resolved Jul 07, 2026, 05:17 PM UTC

   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.

Read the full incident report →

Started Jul 03, 2026, 01:29 PM UTC· resolved Jul 03, 2026, 02:17 PM UTC

1. investigating Jul 03, 2026, 01:29 PM UTC

   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.

2. investigating Jul 03, 2026, 01:32 PM UTC

   We are continuing to investigate this issue.

3. resolved Jul 03, 2026, 02:17 PM UTC

   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.

Read the full incident report →

Started Jun 25, 2026, 05:34 PM UTC· resolved Jun 25, 2026, 05:45 PM UTC

1. identified Jun 25, 2026, 05:34 PM UTC

   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.

2. monitoring Jun 25, 2026, 05:36 PM UTC

   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.

3. monitoring Jun 25, 2026, 05:36 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 25, 2026, 05:45 PM UTC

   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.

Read the full incident report →

Started Jun 24, 2026, 09:21 PM UTC· resolved Jun 24, 2026, 09:50 PM UTC

1. investigating Jun 24, 2026, 09:21 PM UTC

   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.

2. resolved Jun 24, 2026, 09:50 PM UTC

   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.

Read the full incident report →

Started Jun 04, 2026, 11:27 PM UTC· resolved Jun 04, 2026, 11:52 PM UTC

1. identified Jun 04, 2026, 11:27 PM UTC

   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.

2. resolved Jun 04, 2026, 11:52 PM UTC

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

Read the full incident report →

Started May 20, 2026, 04:00 PM UTC· resolved May 20, 2026, 04:49 PM UTC

1. identified May 20, 2026, 06:50 PM UTC

   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

2. monitoring May 20, 2026, 06:52 PM UTC

   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.

3. resolved May 20, 2026, 06:56 PM UTC

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

Read the full incident report →

Started May 14, 2026, 06:12 PM UTC· resolved May 15, 2026, 04:05 AM UTC

1. investigating May 14, 2026, 06:09 PM UTC

   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.

2. resolved May 15, 2026, 12:57 PM UTC

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

Read the full incident report →

Started May 06, 2026, 03:28 PM UTC· resolved May 06, 2026, 04:39 PM UTC

1. monitoring May 06, 2026, 03:28 PM UTC

   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.

2. resolved May 06, 2026, 04:39 PM UTC

   We have updated our systems and webhooks have returned to normal

Read the full incident report →

Started May 04, 2026, 02:03 PM UTC· resolved May 04, 2026, 03:25 PM UTC

1. investigating May 04, 2026, 02:03 PM UTC

   We are currently investigating an increase in 504 API errors for EWS (Exchange on-premise) grants. Grants connected to other providers are not affected.

2. resolved May 04, 2026, 03:25 PM UTC

   We have deployed fixes to reduce the excessive 504 errors. They have returned to normal errors.

Read the full incident report →

Started Apr 30, 2026, 12:30 PM UTC· resolved Apr 30, 2026, 01:30 PM UTC

1. investigating Apr 30, 2026, 12:30 PM UTC

   We are currently investigating an issue in our US environment affecting Notetaker services. Some Notetaker instances are experiencing delays in joining meetings, which may result in extended join latency or a failure to connect. Our engineering team is currently investigating the issue and working toward a resolution. We will provide more information as it becomes available.

2. monitoring Apr 30, 2026, 12:39 PM UTC

   We have mitigated an issue in our US environment that briefly affected Notetaker services. Some instances experienced delays when joining meetings, but performance has now returned to normal. We are continuing to monitor the environment closely to ensure ongoing stability.

3. resolved Apr 30, 2026, 03:45 PM UTC

   Notetaker performance in the US & EU regions has fully returned to normal levels. The issue was caused by a temporary disruption with a Nylas subprocessor that impacted autoscaling behavior, leading to delays in some Notetaker instances joining meetings. The subprocessor has implemented a fix and confirmed stability, and we have validated sustained recovery across our environment. We will continue to monitor closely and are working with the subprocessor on additional safeguards to reduce the likelihood of similar issues in the future.

Read the full incident report →

Started Apr 15, 2026, 05:10 PM UTC· resolved Apr 15, 2026, 05:30 PM UTC

1. investigating Apr 15, 2026, 05:10 PM UTC

   We are investigating timeouts to the following API endpoints related to Notetaker: GET /v3/grants/:grant_id/notetakers GET /v3/notetakers

2. resolved Apr 15, 2026, 05:30 PM UTC

   We have deployed a fix and the Notetaker endpoints are communicating correctly now.

Read the full incident report →

Started Apr 14, 2026, 03:19 PM UTC· resolved Apr 15, 2026, 12:20 AM UTC

1. investigating Apr 14, 2026, 03:19 PM UTC

   We are currently investigating an issue where some Nylas Notetakers are not correctly joining Google Meet events. This does not appear to affect other meeting providers or any other parts of the API.

2. monitoring Apr 14, 2026, 06:28 PM UTC

   We have made improvements and Notetakers are joining correctly. We are continuing to monitor the Notetakers to ensure they continue to operate correctly.

3. resolved Apr 15, 2026, 02:39 AM UTC

   Notetaker join rates for Google Meet events have returned to normal levels following deployed remediations in response to recent Google changes in production (US and EU). We have confirmed stability with sustained recovery of join rates and are no longer observing elevated failures.

Read the full incident report →

Started Feb 24, 2026, 07:30 PM UTC· resolved Feb 24, 2026, 09:25 PM UTC

1. investigating Feb 24, 2026, 07:30 PM UTC

   We are currently experiencing elevated API error rates and increased latency in the US v3 production environment, affecting a subset of customers. This may result in intermittent 500 errors and delayed webhooks. Our engineering team has identified the issue and is actively working on mitigation. We will continue to share updates here.

2. identified Feb 24, 2026, 08:08 PM UTC

   We have identified the underlying issue contributing to elevated API error rates and increased latency in the US v3 production environment. Our engineering team is actively working on mitigation. Customers may continue to experience intermittent 500 errors and delayed webhooks while mitigation efforts are underway. We will continue to provide updates as progress is made.

3. monitoring Feb 24, 2026, 09:16 PM UTC

   Mitigation steps have been successfully implemented, and API error rates and latency in the US v3 production environment have returned to normal levels. We are continuing to closely monitor the environment to ensure stability. We will provide a final update once we confirm the issue is fully resolved.

4. resolved Feb 24, 2026, 09:25 PM UTC

   API error rates and latency in the US v3 production environment have returned to normal levels. The mitigation steps implemented earlier have stabilized the system. We will continue to monitor closely and are implementing additional preventative measures to increase capacity and reduce the risk of recurrence during peak traffic. Thank you for your patience.

Read the full incident report →