Nylas Outage History

Nylas is up right now

Nylas had 12 outages in the last 2 years totaling 36h 29m of downtime — averaging 0.5 incidents per month.

There were 12 Nylas outages since January 23, 2026 totaling 36h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nylas.com

Critical June 4, 2026

[US & EU] Grant Creation and Authorization Errors

Detected by Pingoru
Jun 04, 2026, 11:27 PM UTC
Resolved
Jun 04, 2026, 11:52 PM UTC
Duration
25m
Timeline · 2 updates
  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 →

Minor May 20, 2026

[US & EU] Notetakers Failing to Join Zoom & Google Meet

Detected by Pingoru
May 20, 2026, 04:00 PM UTC
Resolved
May 20, 2026, 04:49 PM UTC
Duration
49m
Timeline · 3 updates
  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 →

Major May 15, 2026

Sending errors with Transactional Send (Beta) and Agent Account (Beta) features

Detected by Pingoru
May 15, 2026, 07:05 AM UTC
Resolved
May 15, 2026, 04:05 AM UTC
Duration
Timeline · 2 updates
  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 →

Minor May 6, 2026

US - Gmail Realtime - Pub/Sub - Elevated Latency & Delayed Webhooks

Detected by Pingoru
May 06, 2026, 03:28 PM UTC
Resolved
May 06, 2026, 04:39 PM UTC
Duration
1h 11m
Timeline · 2 updates
  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 →

Minor May 4, 2026

High number of 504 API errors for EWS grants

Detected by Pingoru
May 04, 2026, 02:03 PM UTC
Resolved
May 04, 2026, 03:25 PM UTC
Duration
1h 22m
Timeline · 2 updates
  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 →

Minor April 30, 2026

Increased Latency for Notetaker Meeting join Events (US & EU Regions)

Detected by Pingoru
Apr 30, 2026, 12:30 PM UTC
Resolved
Apr 30, 2026, 01:30 PM UTC
Duration
59m
Timeline · 3 updates
  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 →

Major April 15, 2026

Some Notetaker API endpoints timing out

Detected by Pingoru
Apr 15, 2026, 05:10 PM UTC
Resolved
Apr 15, 2026, 05:30 PM UTC
Duration
20m
Timeline · 2 updates
  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 →

Major April 14, 2026

Notetakers failing to join some Google Meet events

Detected by Pingoru
Apr 14, 2026, 03:19 PM UTC
Resolved
Apr 15, 2026, 12:20 AM UTC
Duration
9h 1m
Timeline · 3 updates
  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 →

Critical February 24, 2026

US – Elevated API Errors and Increased Latency

Detected by Pingoru
Feb 24, 2026, 07:30 PM UTC
Resolved
Feb 24, 2026, 09:25 PM UTC
Duration
1h 54m
Timeline · 4 updates
  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 →

Minor February 13, 2026

US - Increased Webhook Latency

Detected by Pingoru
Feb 13, 2026, 05:17 PM UTC
Resolved
Feb 13, 2026, 09:57 PM UTC
Duration
4h 39m
Timeline · 5 updates
  1. investigating Feb 13, 2026, 05:17 PM UTC

    We are currently experiencing increased sync latency in the US environment affecting a subset of customers. This may result in delays of up to approximately one hour for email and calendar updates, primarily for Google and Microsoft accounts. We are actively investigating the root cause and will continue to share updates here.

  2. identified Feb 13, 2026, 06:14 PM UTC

    We continue to experience increased webhook latency and delays in the US environment affecting a subset of customers. We have identified a significant increase in API request volume from a small number of integrations, which has resulted in elevated processing latency for Google and Microsoft Graph webhooks. The traffic remains within established rate limits, and core API performance remains normal with no additional request latency. The impact is limited to delayed notification and webhook processing. We are actively implementing performance optimizations and coordinating with affected integrations to better understand expected usage patterns. Updates will be posted here as they become available.

  3. identified Feb 13, 2026, 07:07 PM UTC

    We continue to optimize system performance in response to the increased API traffic identified earlier. We are seeing a reduction in webhook backlog in the US environment. Sync latency remains elevated while the backlog continues to clear. Core API performance remains normal. We are closely monitoring progress and implementing additional optimizations to accelerate recovery. Updates will be shared here as they become available.

  4. monitoring Feb 13, 2026, 07:54 PM UTC

    We have mitigated the webhook latency incident in the US environment. We are observing significant improvement, and webhook backlogs are decreasing steadily. Core API performance has remained normal throughout. We are continuing to monitor recovery to ensure full normalization. Further updates will be shared if needed.

  5. resolved Feb 13, 2026, 09:57 PM UTC

    Webhook latency in the US environment has returned to normal levels. We implemented performance optimizations in response to the elevated API traffic identified earlier, and the webhook backlog has fully cleared. Core API performance remained normal throughout the incident. We will continue to monitor system performance closely to ensure continued stability. Thank you for your patience.

Read the full incident report →