Nylas Outage History

There were 5 Nylas outages since February 13, 2026 totaling 16h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nylas.com

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

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

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

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

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

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

Looking to track Nylas downtime and outages?

Pingoru polls Nylas's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Nylas reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Nylas alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Nylas for free

5 free monitors · No credit card required