Is Nylas v3 Down Right Now? Check if there is a current outage ongoing.

We’re currently experiencing service degradation due to an ongoing issue with Google, which appears to be system-wide including GCP and Workspace accounts. This is causing high latencies and error rates, and impacting the delivery all of Google services. We’re actively monitoring updates from Google and will provide more information as it becomes available.

We’ve been in contact with Microsoft support regarding the ongoing issue with their Graph Calendar API. Microsoft has acknowledged the problem and confirmed that their engineering team is actively working on a resolution. We’ll continue to monitor the situation and provide updates as new information becomes available. Thank you for your patience.

We’ve implemented a workaround to mitigate the impact caused by an issue with Microsoft Graph API. As a result, the affected functionality has been restored, and users should no longer experience errors when accessing related features. Please note that this is a temporary mitigation, and the root cause remains unresolved on Microsoft’s side. We are actively monitoring for updates and will revert our changes once Microsoft provides a permanent fix. We appreciate your patience and will continue to keep you informed.

We are still observing the ongoing issue with the Microsoft Graph API, which continues to affect some Microsoft grants. Impacted users may experience 500 and 504 errors on calendar-related endpoints, including delays or failures in webhook delivery. As of now, there has been no resolution or update from Microsoft. Our team will continue monitoring and will provide further updates as soon as we detect meaningful changes. This will be our final status page update for today unless there is a significant development. Thank you for your patience.

We are continuing to monitor the ongoing issue with the Microsoft Graph API, which is impacting some Microsoft grants. The issue is still causing 500 and 504 errors on calendar-related endpoints, and delays or failures in webhook delivery for affected users. There has been no meaningful change since our last update. Our team remains in contact with Microsoft and is actively monitoring for improvements. We will provide further updates as soon as we see progress or receive new information.

We are currently experiencing service degradation caused by an issue with the Microsoft Graph API. As a result, some Microsoft graph grants are experiencing 500 and 504 errors. For affected users, this may impact webhooks and the following API calls: <b>calendars</b> <b>event</b> <b>scheduler</b> Our team is actively monitoring the situation and has reported the issue to Microsoft. We will continue to provide updates as more information becomes available

We’ve implemented a workaround to mitigate the impact caused by an issue with Microsoft Graph API. As a result, the affected functionality has been restored, and users should no longer experience errors when accessing related features.Please note that this is a temporary mitigation, and the root cause remains unresolved on Microsoft’s side. We are actively monitoring for updates and will revert our changes once Microsoft provides a permanent fix.We appreciate your patience and will continue to keep you informed.

We are still observing the ongoing issue with the Microsoft Graph API, which continues to affect some Microsoft grants. Impacted users may experience 500 and 504 errors on calendar-related endpoints, including delays or failures in webhook delivery.As of now, there has been no resolution or update from Microsoft. Our team will continue monitoring and will provide further updates as soon as we detect meaningful changes.This will be our final status page update for today unless there is a significant development. Thank you for your patience.

We are continuing to monitor the ongoing issue with the Microsoft Graph API, which is impacting some Microsoft grants. The issue is still causing 500 and 504 errors on calendar-related endpoints, and delays or failures in webhook delivery for affected users.There has been no meaningful change since our last update. Our team remains in contact with Microsoft and is actively monitoring for improvements. We will provide further updates as soon as we see progress or receive new information.

We are currently experiencing service degradation caused by an issue with the Microsoft Graph API. As a result, some Microsoft graph grants are experiencing 500 and 504 errors. For affected users, this may impact webhooks and the following API calls:calendarseventschedulerOur team is actively monitoring the situation and has reported the issue to Microsoft. We will continue to provide updates as more information becomes available

The underlying issue has been resolved by our service provider, and we have confirmed that the Notetaker service is now joining Google Meet meetings as expected. All systems are operating normally. Thank you for your patience during this incident.

While we await a response and resolution from the affected subprocessor, we are also actively exploring fallback mechanisms to mitigate the impact of this incident more quickly. Our goal is to restore Notetaker functionality for Google Meet meetings as soon as possible. We will continue to provide updates as we make progress.

We have identified the root cause of the issue as being related to one of our subprocessors. We have submitted an urgent Priority 1 support request with the provider and are awaiting their response. Our team continues to monitor the situation closely and will share updates as they become available. Thank you for your continued patience.

We are currently investigating an issue where our Notetaker service is failing to join Google Meet meetings. Our team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will provide updates as soon as more information is available. Thank you for your patience.

The underlying issue has been resolved by our service provider, and we have confirmed that the Notetaker service is now joining Google Meet meetings as expected.All systems are operating normally. Thank you for your patience during this incident.

While we await a response and resolution from the affected subprocessor, we are also actively exploring fallback mechanisms to mitigate the impact of this incident more quickly.Our goal is to restore Notetaker functionality for Google Meet meetings as soon as possible. We will continue to provide updates as we make progress.

We have identified the root cause of the issue as being related to one of our subprocessors.We have submitted an urgent Priority 1 support request with the provider and are awaiting their response. Our team continues to monitor the situation closely and will share updates as they become available.Thank you for your continued patience.

We are currently investigating an issue where our Notetaker service is failing to join Google Meet meetings.Our team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will provide updates as soon as more information is available.Thank you for your patience.

The scheduled maintenance has been completed.

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

This message serves as notification that we have added new Subprocessor(s) listed below to our systems. These subprocessors have been carefully selected and vetted to ensure they meet our high standards for data security and privacy. Effective 4 June 2025, we will be partnering with the following new subprocessor to further enhance our services: PlayerZero You can find all of the details regarding what data is being processed by or passed through each subprocessor, as well as the applicable components, locations, and entities on our updated Nylas Subprocessor page on our website at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns, please contact our Security Team at security@nylas.com.

OVHcloud has finally confirmed to us that all issues related to this incident were resolved as of May 1st. Since that time, Nylas has observed no increase in timeout rates or related anomalies. With stable metrics and provider confirmation, we are now marking this incident as resolved.

Following our last update, timeout rates continued to improve but had not fully returned to normal. We submitted a support ticket with OVHcloud and escalated it to the highest priority. While we have not yet received a response or confirmation of resolution from OVHcloud support, all relevant metrics have now returned to normal levels on our side. We will continue to monitor closely. Once OVHcloud confirms the issue is fully resolved, we will mark this incident as resolved as well.

As part of their incident mitigation efforts, OVHcloud appears to have made significant changes to their DNS records. In response, we cleared all relevant DNS caches and restarted our servers to ensure the most up-to-date routing information is in use. Since these changes, IMAP connectivity has largely stabilized and timeout rates have decreased overall. However, we are still actively tuning connectivity to certain OVHcloud servers and will continue monitoring closely.

OVHcloud has reported that the <a href="https://network.status-ovhcloud.com/incidents/5bhg2l9cd7z5">network incident</a> impacting their Madrid and Paris points of presence has been resolved. <b>Start Time:</b> April 28, 2025, at 8:08 AM PT <b>End Time:</b> April 28, 2025, at 3:00 PM PT <b>Root Cause:</b> Regional power outage affecting Spain and Portugal. While OVHcloud has closed their incident, we continue to observe occasional IMAP timeouts. We are closely monitoring the situation and will provide further updates if necessary. Thank you for your continued patience and understanding.

OVHcloud has provided an update on their <a href="https://network.status-ovhcloud.com/incidents/5bhg2l9cd7z5">ongoing incident</a>. Their Madrid Point of Presence (PoP) became accessible again at approximately 2:40 PM Pacific Time. However, they are still experiencing peering issues, which may continue to impact connectivity. The provider’s teams are actively working to fully restore service. We are continuing to monitor the situation and any potential impacts to IMAP connectivity. Further updates will be posted here as we learn more. We appreciate your patience and understanding.

Starting at approximately 1:30 AM Pacific Time, we began observing elevated timeouts when connecting to the third-party IMAP provider, <a href="https://www.ovhcloud.com/en-gb/mail/"><b>OVHcloud</b></a>. OVHcloud has reported an <a href="https://network.status-ovhcloud.com/incidents/5bhg2l9cd7z5">active incident</a> related to widespread power outages across Peninsular Spain and other regions. We are actively monitoring this situation and any related impacts on email service providers. Updates will be posted here as more information becomes available.

<b>Update on Microsoft's Graph API Fix</b> The issue impacting the sending of emails with large attachments via the Graph API using <tt><small><b>multipart/form-data</b></small></tt> due to a Microsoft bug has been addressed. It appears the fix is now fully rolled out, and there have been no errors of this specific type in over 12 hours in both the US and EU regions. We are confident that the issue has been resolved, but we will continue to monitor the system to ensure stability. Thank you for your patience throughout this incident.

<b>Update on Microsoft's Graph API Fix</b> We are seeing significant progress with the fix rolled out by Microsoft for their issue impacting the sending of emails with large attachments via the Graph API using <tt><small><b>multipart/form-data</b></small></tt>. Over the past 48 hours, the error rate has dropped substantially, and we are monitoring the improvements closely. <b>US Region</b>: The error rate has decreased to 0.047% over the past 24 hours. <b>EU Region:</b> The error rate has decreased to 0.060% over the same period. We will continue to monitor the situation and provide updates as needed. Thank you for your patience as Microsoft works to fully deploy the fix.

<b>Update from Microsoft:</b> <em>The cause of the issue has been identified, and a fix has been rolled out. It is expected to be fully deployed by early next week. We apologize for the disruption this has caused.</em> We will continue to monitor the situation and provide further updates as needed. Thank you for your patience.

To mitigate Microsoft's bug that only impacts attachments sent using <small><b><tt>multipart/form-data</tt></b></small>, we recommend using <small><b><tt>application/json</tt></b></small> instead for attachments under 3MB. This workaround will continue to work effectively even after Microsoft resolves their bug. <b>For more details, please refer to Nylas’ official guide:</b> <a href="https://support.nylas.com/hc/en-us/articles/18519426906781-Sending-attachments-in-API-V3-less-than-3MB-via-JSON">Sending attachments < 3MB via JSON (Nylas API v3)</a>

We have escalated the bug ticket to the highest priority with Microsoft Office 365. However, at the time of this update, they have only acknowledged receipt of the issue. We are actively working to get a response and status update from Microsoft, but they have yet to make a public acknowledgment. The number of users and organizations reporting these errors—particularly when sending larger attachments via the Graph API—on public Microsoft forums continues to rise. For reference, here is one of the public threads: https://learn.microsoft.com/en-us/answers/questions/2258885/graph-api-createuploadsession-returns-401-on-uploa At Nylas, we are exploring potential solutions to help mitigate these errors for our customers while Microsoft works on a fix. We will update this page as soon as we have progress to share.

We are still waiting on a response from Microsoft to our support ticket, but continue to find other MS Graph users facing the same errors from MS starting today: https://learn.microsoft.com/en-us/answers/questions/2258994/issue-with-sending-emails-with-large-attachments-v

We continue to investigate the root cause, however we are starting to see reports around the Internet of other Microsoft Graph users experiencing this net-new behavior and errors from MS. Below is one example: https://learn.microsoft.com/en-us/answers/questions/2258885/graph-api-createuploadsession-returns-401-on-uploa We are also opening a Bug Ticket with Microsoft.

We have narrowed the impact of this incident to include only calls to Send for Microsoft Graph for emails with large attachments using <small><b><tt>multipart/form-data</tt></b></small> (calls using <small><b><tt>application/json</tt></b></small> appear to be unaffected). We are continuing to investigate why Microsoft started returning these provider errors at approximately 1:00 AM today, and why the error messages themselves do not contain any error information.

We are still investigating the cause of this incident.

We are investigating higher levels of 401 errors for email sending. This appears to be limited to Microsoft grants sending emails with attachments.

The incident affecting API v3 latencies for provider calls and webhooks has been resolved. All mitigations have been successfully implemented, and latencies have returned to normal levels. The backlog of pending webhooks has been cleared, and all systems are functioning as expected. We will continue to monitor performance to ensure stability. Thank you for your patience and understanding.

All mitigations have been implemented, and latencies continue to improve. Our systems are working through the backlog of pending webhooks. We will continue to monitor the situation closely and consider the incident resolved once all outstanding webhooks have been sent.

Latencies are beginning to improve as we continue deploying the mitigations. We will keep monitoring the situation and provide further updates as necessary.

We have identified a potential root cause and are actively implementing mitigations to address the issue. We will continue to monitor the situation closely and provide updates as needed.

Our team is actively working on identifying the root cause and implementing mitigations. We will provide further updates as soon as we have more information. Thank you for your patience.

Starting at approximately 8:45 AM PT, we started to see increasing latencies for both Provider API calls and webhooks. We are investigating the root cause and working on mitigations and will post updates to this page.

Between 2025-04-08 14:00 PDT and 2025-04-08 18:04 PDT, customers may have experienced intermittent 503 errors across our services. This was due to an upstream incident affecting our subprocessor, Fastly. To mitigate the issue and restore stability, we’ve rerouted impacted traffic from Fastly to Cloudflare. This change has fully resolved the incident. We’re continuing to monitor closely and will conduct a full postmortem to ensure long-term resilience. Thank you for your patience

We incorrectly marked the earlier incident as resolved. The issue is still ongoing due to a third-party provider, Fastly. We are actively monitoring the situation and assessing any ongoing impact. We sincerely apologize for the confusion and will post regular updates here as we receive more information

Fastly has posted the following update on their Status Page (https://www.fastlystatus.com/incident/377443): "A correction has been deployed to the NGWAF platform by Engineering, resulting in a phased recovery for affected customers. Deployment monitoring will persist until full service restoration is observed for all impacted services. This incident caused disruption to customers utilizing NGWAF services; all other products and services remained operational. Customers experiencing ongoing issues are encouraged to contact their assigned account teams or the support team through dedicated support chat or email at support@fastly.com if a case is not already in progress."

Fastly has posted the following update on their Status Page (https://www.fastlystatus.com/incident/377443): "Our engineers have identified the contributing factor and are applying a fix to our Next-Gen WAF (NGWAF) services."

Some customers may be experiencing elevated 503 errors when accessing our services on API v3. This is related to an active incident at our CDN provider, Fastly. Our team is closely monitoring the situation and working to mitigate impact where possible. You can track Fastly's progress on their Status Page here: https://www.fastlystatus.com/incident/377443

The fix has been successfully deployed.

The issue has been identified and a fix is being implemented.

A transient issue on Nylas infrastructure is causing a small percentage of webhooks to appear as timed out. We have identified the problem and are working on a fix. In the meantime, keep in mind, these Webhooks will be retried automatically and impact is low. The same issue is slightly decreasing Send API success rate and slightly increasing sync latencies We apologize for the inconvenience and appreciate your patience. If you have any questions or concerns, please contact our support team (support@nylas.com).

Microsoft has confirmed final resolution (see below) so we are marking this incident as resolved as well. "After a period of extended monitoring, we’ve confirmed through customer reports and service health telemetry that the issue is resolved."

Microsoft has posted the update below, and we also see error rates returned to normal levels. We will continue to monitor both our systems and Microsoft's status pages until they mark it as fully resolved. "From monitoring service telemetry, most users should now experience relief. We’ve completed our optimizations and we're continuing our period of extended monitoring to ensure the availability remains stable."

Below is the latest update from Microsoft: "The service is continuing to incrementally recover. We're forecasting that impact will be fully remediated by Tuesday, November 26, 2024, at 3:00 AM UTC, though we're closely monitoring our progress and will provide an updated timeline should the estimate change."

Microsoft is reporting a partial recovery. Their most recent update is below: "We’ve completed additional actions and are seeing some recovery. We’re continuing to monitor the service while we complete other workstreams intended to fully resolve the issue. Details can be found in the admin center under MO941162."

Microsoft is still working on resolving this incident on their end. Their most recent update is below: "We’re facing delays in our recovery efforts and are taking immediate action to address them. We understand the significant impact of this event to your businesses and are working to provide relief as soon as possible. More details can be found in the admin center under MO941162."

Microsoft has confirmed a severe degradation of their Outlook and Team services starting around 2:00 AM Pacific Time. This is impacting Nylas services calling their APIs for Email and Calendaring, resulting in an elevated number of 504 Gateway Timeout errors in our API responses, as well as elevated latencies. We are monitoring their progress closely and will post updates here as we receive them. https://x.com/MSFT365Status/status/1860973220662280356?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Etweet https://downdetector.com/status/microsoft-365/
 We apologize for the inconvenience and appreciate your patience. If you have any questions or concerns, please contact our support team (support@nylas.com).

This has been linked to an ongoing Microsoft incident that has prevented communication to mailboxes and calendars. Microsoft grants will have issues with some API calls until Microsoft can resolve this. https://x.com/MSFT365Status/status/1860973220662280356?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Etweet

We are seeing increases in 504 errors for API email sending requests for some Microsoft grants. We are investigating.

This incident has been resolved.

The fix has been deployed and we are monitoring the results.

We have identified a fix and are working on the deployment.

We are continuing to investigate this issue.

We are currently experiencing an issue where scheduler pages with Conferencing enabled are returning the following error: "Conference autocreate for [meeting provider] not supported with grant" This issue is impacting both our EU and US services. Current Status: Our team is actively investigating the root cause of this issue, and we are working towards a solution. We will provide updates as soon as additional information is available. We apologize for the inconvenience and appreciate your patience. If you have any questions or concerns, please contact our support team (support@nylas.com).

We have resolved this issue by reverting the change. If you experienced this issue, your system is sending over unsupported fields in the API payload and you need to review your API calls to ensure you are only sending us fields that are in our API documentation.

We have received reports of increased "Unsupported field" errors when trying to send via our API. We are investigating.

We have identified the root cause of the incident as an issue with a single Microsoft Graph end customer, impacting only one Nylas customer. We are marking this incident as resolved, but will continue assisting the affected customer in resolving their related backlog.

We have confirmed that this issue is limited to Microsoft grants that have been created using Bulk Authentication and App-based Permissions. Grants created by individual users authenticating are not affected.

We are investigating an unexpected increase in webhooks and slower API response times in our v3 APIs for Microsoft Graph accounts

The fix for the issue has been released. The send API calls are working correctly now. Please reach out to support if you have any questions.

We have identified the issue that was causing this. We are working on a fix now.

We have identified the issue that was causing this. We are working on a fix now.

We are investigating the internal error response returned when sending messages. The sends are still successful with 200 response code but an additional Internal Error is returned.

We are resolving this incident. Please reach out to support if you have questions or issues.

We are seeing improvements on both timeouts and 500 errors levels

We are investigating timeouts and 500 errors on most of our API endpoints. We will provide timely updates

The Google GMail API has returned to normal operations. If you have any additional questions or concerns, please contact our support team (support@nylas.com).

We continue to see error levels return to previous levels. We will continue to monitor closely before marking as Resolved.

We are starting to see the GMail service recover. We will continue to monitor and post updates here as soon as it has been mitigated by Google.

We are currently experiencing Google grants not syncing across our system, and our API for Google is currently not returning results. Reports are coming in around the Internet of the Google API being down, but Google has not posted anything to their status page at the time of this post. Our engineering team is actively investigating the issue and working to identify the root cause. Next Update: We will provide an update in 30 minutes or sooner if we have more information. We apologize for the inconvenience and appreciate your patience. If you have any questions or concerns, please contact our support team (support@nylas.com).

This incident has been resolved.

We have made some changes that have improved the situation. We are seeing errors back to normal levels. We will monitor to ensure things are keeping stable.

We are seeing an elevated rate of 5XX errors, mostly affecting the API v3 hosted authentication on the US datacenter. The team is looking into it.

After monitoring the results, we confirm that the fix is working and no further delays are being observed. We will mark this incident as resolved.

We have implemented mitigation measures to address the email synchronization delays. We are monitoring the results.

We are actively investigating this issue to identify the root cause.

We are currently experiencing delays in email synchronization for IMAP users in the EU region. Our team is investigating the issue.

We have confirmed that the remediation was successful and error rates have returned to normal levels. We sincerely apologize for the disruptions this may have caused. If you have any questions or concerns, please contact our support team (support@nylas.com).

We have identified an increase in 500 errors for some customers in our US data center on our /send endpoint. A fix has been identified and deployed, and we are monitoring the results. We will provide updates as soon as more information becomes available.

The incident has been resolved.

The incident is now mitigated we are monitoring the results and some workflows may be delayed.

We have identified the issue causing the 500 errors for some customers, we are working on the fix.

We keep investigating the issue and will provide further updates as soon as we have more information.

Our team is continuing to investigate this issue. Further updates will be provided as soon as we have more information.

We have narrowed down the issue to only affecting customers using scheduled send in the US datacenter. Our team is continuing to work on a resolution and will provide further updates as they become available.

We are currently investigating an issue where the Scheduled Send feature is not functioning as expected for a subset of customers. Our team is actively working to identify the root cause and implement a solution. We will provide updates as soon as more information becomes available.

At 7:45 AM PDT, we identified elevated "406 Not Acceptable" HTTP errors on our API service, primarily on our /send endpoint, starting at 4:45 AM PDT. The root cause was a misconfiguration of our Web Application Firewall settings. This setting was corrected at 8:30 AM PDT, and we resolved the incident at 8:45 AM PDT. We sincerely apologize for the disruptions this may have caused. If you have any questions or concerns, please contact our support team (support@nylas.com).

This incident has been resolved.

The team has deployed a fix and all users should now be able to login to the dashboard. Please reach out to support@nylas.com if it’s still not working.

We are receiving reports of customers not being able to access the v3 dashboard. The team is currently looking into it.

The incident has been resolved. Thank you for your patience and understanding.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue. We will post our next update in 1 hour.

We are continuing to investigate this issue. We will post our next update in 1 hour.

We are continuing to investigate this issue.

We are continuing to investigate this issue. The only impact is a delay in webhooks, with a maximum delay of up to 10 minutes.

We are currently investigating an issue that is causing increased webhook delays for Graph Calendar, Contacts, Email, and Google Calendar services. There will be increased webhook delays, but we are still sending all webhooks.

We confirmed that the issue was limited to Webhook API. It is working as expected now. We aren't seeing any more occurrences of the Internal Server Errors. We are marking this incident as resolved.

We are investigating "Internal Server Errors" in both US and EU for Webhook API