Nylas kesinti geçmişi

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 support@nylas.com.

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 support@nylas.com.

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

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

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

We are currently investigating an issue in our US & EU environments 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.

We have mitigated an issue in our US & EU environments 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.

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.

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

We are aware of an issue affecting Notetaker transcriptions for US-based Nylas applications. Meetings can still be joined and recorded, but transcription, summaries, and action items, is currently delayed. This is caused by an ongoing outage with a third-party AI provider impacting their North American API endpoints. Their team is actively investigating and working toward resolution. All transcriptions will be automatically processed once the outage is resolved to produce the transcript, summaries, & action items. No recordings will be lost — customers should expect a delay in receiving their transcriptions but no action is required on their part. We are monitoring the situation closely and will provide updates as more information becomes available. What is impacted: - Notetaker transcription processing (delayed) What is NOT impacted: - Meeting joining and recording - Notetakers sent from an EU-based Nylas application - All other Nylas platform services For latest updates on AssemblyAI, please follow: https://status.assemblyai.com/

Our backup transcription service kicked in successfully & we are reporting no loss of transcriptions. Our primary service has indicated that they're recovering from their incident.

According to our third-party service provider, the backlog has been fully cleared and processing times have returned to normal. If you have any questions or continue to experience issues, please reach out to Support.

We are aware that Microsoft is currently experiencing service degradation affecting Microsoft 365 services. This is impacting Nylas customers with Microsoft grants.. What's happening: Microsoft has identified issues with their infrastructure in North America that is affecting access to Microsoft 365 services including Exchange Online, Outlook, and Teams. Impact to Nylas customers: - API requests to Microsoft grants may experience timeouts or errors - Syncing of emails, contacts, and calendar events from Microsoft grants may be delayed or temporarily unavailable - This affects customers using Microsoft grants. What we're doing: The Nylas API is operating normally. This issue is with Microsoft's upstream services. We are actively monitoring Microsoft's status and will provide updates as their services recover. What you can do: - Implement retry logic with exponential backoff for API calls to Microsoft-connected accounts - Monitor https://x.com/MSFT365Status for direct updates from Microsoft We will update this status page as more information becomes available. --- Next update: In 1 hour or when Microsoft provides resolution status

We see that the Microsoft Graph API traffic has returned to normal. We are continuing to monitor the situation as we await the all clear from Microsoft. All grants and API endpoints should now be working correctly.

Microsoft has confirmed that they have resolved this issue. We are seeing normal API behavior for all Microsoft grants. https://x.com/MSFT365Status/status/2014586340969529365

We are currently investigating a rise of 400 unexpected end of JSON input for Microsoft grants. We have traced to Microsoft Graph response and we are reaching out to MS.

We have informed Microsoft Support of this issue and they have escalated it and are investigating. They have not reported their findings to us yet. We also have found that this issue appears to only occur for API calls to retrieve all messages or threads when using the parameters "any_email", "from", "to", "cc", "bcc", or "subject" This issue is not affecting EWS grants. Only some Microsoft grants. It also is only affecting 0.18% of all API calls for Microsoft grants.

Microsoft has resolved the issue and the errors are no longer occurring.

Cloudflare Global Network experiencing issues.

We are continuing to monitor the widespread Cloudflare global network disruption.

Cloudflare experienced a global outage that impacted several services across the internet. As a result, some Nylas systems that rely on Cloudflare were temporarily unreachable. Specifically: • developer.nylas.com (Docs Site) • book.nylas.com (Hosted Scheduler Pages) Core Nylas API services were not impacted. Cloudflare has implemented a fix and we are seeing full recovery. We will continue to monitor until we confirm complete stability. Cloudflare’s incident report can be found here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

This outage also appears to have impacted Microsoft, resulting in delays in notifications sent to Nylas. We observed a large spike in inbound notifications, which we believe was a catch-up from their earlier delays. We have fully processed the remaining backlog, and latencies are back to normal. Cloudflare is continuing to report that some customers are still experiencing issues and that their incident is not yet fully resolved. We will continue to monitor closely and provide updates as conditions evolve. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

We are pleased to report that the incident impacting services via Cloudflare has now been fully resolved. Cloudflare posted their resolution at 11:28 a.m. PT on November 18, 2025 (19:28 UTC). Cloudflare Status: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 During this incident, only the following Nylas services were affected: • developer.nylas.com (Documentation site) • book.nylas.com (Hosted Scheduler Pages) • Microsoft webhook delivery delays from the provider (temporary backlog) All core Nylas API services remained fully operational throughout. If you continue to experience any irregularities or delays, please contact our support team for assistance. Thank you for your patience and understanding.

Cloudflare has posted a detailed Postmortem for their outage here: [https://blog.cloudflare.com/18-november-2025-outage/](https://blog.cloudflare.com/18-november-2025-outage/)

We’re aware of an ongoing Microsoft 365 outage that is impacting some Nylas integrations relying on this provider. Our systems remain operational, but users connected to Microsoft 365 may experience intermittent errors or degraded performance. We’re closely monitoring Microsoft’s updates and will provide more information as it becomes available. For more details please visit: https://status.cloud.microsoft/

Microsoft has reported that their services are now operational. Nylas integrations relying on Microsoft 365 are functioning normally again, and we’re no longer observing related errors or degraded performance. We’ll continue to monitor to ensure full stability, but no further impact is expected. For more details, please visit: https://status.cloud.microsoft/

Microsoft services have fully recovered, and all Nylas integrations relying on Microsoft 365 are operating normally. This incident has been resolved. For additional details, please visit: https://status.cloud.microsoft/

We found an issue causing Notetaker media to be temporarily unavailable and experiencing elevated latencies for processing. Transcriptions remain accessible, and all other Notetaker functionality remains operational. A fix was deployed to resolve this, and we’re currently working to restore the missing media as soon as possible.

We’re continuing to restore missing Notetaker media. The process is ongoing, and we’ll share further updates as progress continues.

We’re still making progress on restoring missing Notetaker media. Our teams continue to work on the recovery, and we’ll provide more updates as progress is made.

We’re finalizing validations before completing the restoration process. Our teams remain focused on recovery efforts, and we’ll continue to share updates as progress continues.

The restoration has been completed, and all Notetaker media is fully available. This incident is now resolved.