Mar <var data-var='date'>28</var>, <var data-var='time'>03:00</var> PDT Completed - The scheduled maintenance has been completed.Mar <var data-var='date'>28</var>, <var data-var='time'>01:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'>13</var>, <var data-var='time'>07:09</var> PDT Scheduled - A maintenance window is scheduled for Saturday, March 28 at 1:00 AM PT for portions of the production environment. During this time, we will perform infrastructure upgrades and optimizations. Some customers may experience brief service interruptions or intermittent 5xx errors while affected services restart and reconnect during the maintenance window. Any interruptions are expected to last only a few minutes at a time. Our team will actively monitor the system throughout the maintenance window and will post updates here as progress continues. If you experience issues outside of the expected brief interruptions during this window, please contact support@nylas.com.

[US/EU] Scheduled Maintenance -- Infrastructure Optimization

Mar <var data-var='date'> 5</var>, <var data-var='time'>19:00</var> PST Completed - The scheduled maintenance has been completed.Mar <var data-var='date'> 5</var>, <var data-var='time'>18:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'> 4</var>, <var data-var='time'>07:45</var> PST Scheduled - A maintenance window is scheduled for Thursday, March 5 at 6:00 PM PT for the US production environment and will last approximately one hour. During this time, we will perform infrastructure optimizations to our caching systems. For brief periods during the maintenance window, some customers may experience short bursts of increased latency or intermittent 5xx errors as connections reset. These interruptions are expected to last less than a minute at a time. Our team will actively monitor the system throughout the maintenance window and provide updates here if needed.

[Scheduled Maintenance] US - API v3 - Caching Infrastructure Optimization

Mar <var data-var='date'> 4</var>, <var data-var='time'>13:52</var> PST Completed - This message serves as notification that the following updates have been made to the Nylas Subprocessors page. The following subprocessors are being added: - Anthropic - Cyberhaven - Google Gemini - OpenAI You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.Mar <var data-var='date'> 4</var>, <var data-var='time'>13:52</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'> 4</var>, <var data-var='time'>13:51</var> PST Scheduled - This message serves as notification that we are making changes to Nylas' Subprocessors page today

Update to Nylas' Subprocessors page

Feb <var data-var='date'>24</var>, <var data-var='time'>13:25</var> PST 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.Feb <var data-var='date'>24</var>, <var data-var='time'>13:16</var> PST Monitoring - 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.Feb <var data-var='date'>24</var>, <var data-var='time'>12:08</var> PST Identified - 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.Feb <var data-var='date'>24</var>, <var data-var='time'>11:30</var> PST Investigating - 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.

US – Elevated API Errors and Increased Latency

Feb <var data-var='date'>13</var>, <var data-var='time'>13:57</var> PST Resolved - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>11:54</var> PST Monitoring - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>11:07</var> PST Update - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>10:14</var> PST Identified - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>09:17</var> PST Investigating - 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.

US - Increased Webhook Latency

Jan <var data-var='date'>29</var>, <var data-var='time'>11:48</var> PST Resolved - 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.Jan <var data-var='date'>29</var>, <var data-var='time'>10:42</var> PST Update - 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.Jan <var data-var='date'>29</var>, <var data-var='time'>10:25</var> PST Investigating - 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/

Degraded - NoteTaker Transcription

Jan <var data-var='date'>23</var>, <var data-var='time'>06:48</var> PST Resolved - Microsoft has confirmed that they have resolved this issue. We are seeing normal API behavior for all Microsoft grants. https://x.com/MSFT365Status/status/2014586340969529365Jan <var data-var='date'>22</var>, <var data-var='time'>17:56</var> PST Monitoring - 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.Jan <var data-var='date'>22</var>, <var data-var='time'>16:25</var> PST Investigating - 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

Microsoft Graph API incident affecting Nylas API

Jan <var data-var='date'>22</var>, <var data-var='time'>08:53</var> PST Completed - This message serves as notification that the following updates have been made to the Nylas Subprocessors page. The following subprocessors are being added: Orca Security The following subprocessors are being removed: DataGroomr, Inflection.io, Instrumental Group You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.Jan <var data-var='date'>22</var>, <var data-var='time'>08:52</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>22</var>, <var data-var='time'>08:51</var> PST Scheduled - This message serves as notification that we are making changes to Nylas' Subprocessors page today

Jan <var data-var='date'>13</var>, <var data-var='time'>14:00</var> PST Resolved - Microsoft has resolved the issue and the errors are no longer occurring.Jan <var data-var='date'> 5</var>, <var data-var='time'>10:38</var> PST Update - 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.Dec <var data-var='date'>30</var>, <var data-var='time'>14:01</var> PST Investigating - 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.

Small number of API Calls returning 400 JSON input errors for Miscrosoft...

Dec <var data-var='date'> 1</var>, <var data-var='time'>13:31</var> PST Completed - This message serves as notification that the following updates have been made to the Nylas Subprocessors page. The following subprocessor is being added: Spekit You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.Dec <var data-var='date'> 1</var>, <var data-var='time'>13:30</var> PST Scheduled - This message serves as notification that we are making changes to Nylas' Subprocessors page today

Nov <var data-var='date'>18</var>, <var data-var='time'>13:00</var> PST Resolved - 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.Nov <var data-var='date'>18</var>, <var data-var='time'>09:04</var> PST Update - 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/8gmgl950y3h7Nov <var data-var='date'>18</var>, <var data-var='time'>06:51</var> PST Update - 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/8gmgl950y3h7Nov <var data-var='date'>18</var>, <var data-var='time'>05:41</var> PST Monitoring - We are continuing to monitor the widespread Cloudflare global network disruption.Nov <var data-var='date'>18</var>, <var data-var='time'>04:54</var> PST Investigating - Cloudflare Global Network experiencing issues.

[EU & US] Global Cloudflare Outage

Oct <var data-var='date'>30</var>, <var data-var='time'>12:43</var> PDT Resolved - 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/Oct <var data-var='date'>30</var>, <var data-var='time'>07:35</var> PDT Monitoring - 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/Oct <var data-var='date'>29</var>, <var data-var='time'>12:33</var> PDT Identified - 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/

[External] Microsoft 365 Outage Affecting Nylas Integrations

Oct <var data-var='date'>29</var>, <var data-var='time'>19:58</var> PDT Resolved - The restoration has been completed, and all Notetaker media is fully available. This incident is now resolved.Oct <var data-var='date'>29</var>, <var data-var='time'>16:02</var> PDT Update - 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.Oct <var data-var='date'>29</var>, <var data-var='time'>12:31</var> PDT Update - 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.Oct <var data-var='date'>29</var>, <var data-var='time'>09:48</var> PDT Update - We’re continuing to restore missing Notetaker media. The process is ongoing, and we’ll share further updates as progress continues.Oct <var data-var='date'>29</var>, <var data-var='time'>07:12</var> PDT Identified - 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.

[EU & US] Notetaker Media Unavailable

Oct <var data-var='date'>24</var>, <var data-var='time'>00:00</var> PDT Completed - The scheduled maintenance has been completed.Oct <var data-var='date'>23</var>, <var data-var='time'>21:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct <var data-var='date'>22</var>, <var data-var='time'>10:34</var> PDT Update - We will be undergoing scheduled maintenance during this time.Oct <var data-var='date'>22</var>, <var data-var='time'>10:33</var> PDT Scheduled - We are performing a system update to enhance the reliability and efficiency of our services. While we do not anticipate any downtime during the maintenance window, there is a possibility of delayed or duplicated webhooks. We appreciate your understanding as we continue to optimize our infrastructure. If you have any questions or concerns, please contact our support team at support@nylas.com.

[Scheduled Maintenance] US & EU - API v3 - Service Optimization

Sep <var data-var='date'>17</var>, <var data-var='time'>15:00</var> PDT Completed - The scheduled maintenance has been completed.Sep <var data-var='date'>17</var>, <var data-var='time'>13:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Sep <var data-var='date'> 3</var>, <var data-var='time'>10:40</var> PDT Scheduled - On Wednesday September 17th between 8:00-10:00 PM UTC, Nylas will perform scheduled maintenance to upgrade our IMAP High Speed Cache to improve performance and reliability. During this window, customers may experience up to 20 minutes of delays in IMAP sync and webhook delivery. In addition, some duplicate webhooks may be sent during this period. No customer action is required, and impact is expected to be low aside from these temporary delays and duplicate webhooks.

[Scheduled Maintenance] EU - API v3 - IMAP Sync & Webhooks

Sep <var data-var='date'>10</var>, <var data-var='time'>22:14</var> PDT Resolved - The incident affecting Scheduler booking pages has been resolved. As of September 10, 2025, at 14:55 PDT / 17:55 EST, booking pages are loading as expected. Please note that the resolution occurred at the time specified above, and this update is being posted retrospectively.Sep <var data-var='date'>10</var>, <var data-var='time'>14:54</var> PDT Investigating - We are investigating reports that Scheduler booking pages are not loading in some browsers for some users.

Scheduler booking pages not loading for some users or browsers

Sep <var data-var='date'>10</var>, <var data-var='time'>09:46</var> PDT Resolved - Error rates have decreased significantly (approximately 10x lower than at the start of this incident) and have remained stable. While Google has not yet fully confirmed, we are treating this lower level of errors as the new normal. We will continue to monitor and work with Google as needed, but no further updates are expected.Sep <var data-var='date'> 9</var>, <var data-var='time'>12:17</var> PDT Monitoring - Error rates have decreased by approximately 10x since the start of this incident, though they remain elevated compared to pre-incident levels. Google has escalated the issue to their Product team for further review to determine whether this behavior represents a new baseline. We will continue monitoring closely, working with Google, and posting updates here as we learn more.Sep <var data-var='date'> 3</var>, <var data-var='time'>12:54</var> PDT Update - We remain actively engaged with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors continue to surface as 504 responses within the Nylas platform. The case is still under review by Google’s Gmail API team. While no significant updates have been provided yet, our monitoring confirms that error volumes remain elevated above normal levels. We will continue to closely track the situation and provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding.Aug <var data-var='date'>29</var>, <var data-var='time'>11:18</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. The case remains escalated to Google’s Gmail API team. While we are still awaiting their findings, our engineering team continues to closely monitor error volumes, which remain elevated above our normal baseline despite recent improvements. We will provide further updates as soon as Google shares additional details. Thank you for your continued patience and understanding.Aug <var data-var='date'>26</var>, <var data-var='time'>14:16</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. Google has escalated the case to their Gmail API team. While an update was initially expected by August 26th, our support partners have informed us that this has now been deferred to August 28th, 2025. In the meantime, our engineering team continues to closely monitor error volumes, which remain elevated above our normal baseline. We will provide further updates as soon as Google shares additional findings. Thank you for your continued patience and understanding.Aug <var data-var='date'>25</var>, <var data-var='time'>18:33</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. Google has escalated the case to their Gmail API team, and we are currently awaiting their findings. Our support partners have confirmed that an update from the Gmail API team is expected no later than August 26th, 2025. In the meantime, our engineering team continues to closely monitor error volumes, which remain above our normal baseline despite recent improvements. We will provide another update as soon as Google shares additional details. Thank you for your continued patience and understanding.Aug <var data-var='date'>22</var>, <var data-var='time'>14:54</var> PDT Update - We remain actively engaged with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. At this time, we have not yet received any additional updates from Google following their escalation to the Gmail API team. Our latest monitoring indicates that error volumes have increased compared to yesterday. While current levels remain below the peak volumes observed earlier in the incident, they are still well above our normal baseline. Our engineering team continues to track the situation closely and will provide further updates as soon as new information becomes available. Thank you for your continued patience and understanding.Aug <var data-var='date'>21</var>, <var data-var='time'>14:36</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. Google has escalated the case to their Gmail API team for deeper investigation. In the meantime, our own monitoring shows that error volumes have decreased significantly over the past few days. While this represents clear improvement, the error rate remains above our normal baseline. Our engineering team is closely aligned with Google’s investigation and will continue to monitor the situation. We will provide further updates as soon as additional findings are shared. Thank you for your continued patience and understanding.Aug <var data-var='date'>20</var>, <var data-var='time'>13:08</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. Google has confirmed that no issues were identified at the network level and has now escalated the case to their Gmail API team for deeper investigation. Our engineering team remains closely aligned with theirs and will continue monitoring the situation. We will provide another update as soon as Google shares additional findings, expected within the next 24–48 hours. Thank you for your continued patience and understanding.Aug <var data-var='date'>19</var>, <var data-var='time'>15:18</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. Google has confirmed that the issue originates on their side. Our engineering team is collaborating closely with theirs to support the ongoing investigation and resolution efforts. We will continue to monitor closely and provide updates as soon as new information becomes available. Thank you for your continued patience and understanding.Aug <var data-var='date'>18</var>, <var data-var='time'>15:55</var> PDT Update - We continue to actively engage with Google Workspace Support regarding elevated 503 “Service Unavailable” responses across multiple Google APIs, including both Gmail and Calendar. These upstream errors surface as 504 responses within the Nylas platform. At this time, there has been no improvement in error rate, and we have not yet received any indication of the root cause from Google. Our engineering team is continuing to exchange diagnostic data with theirs in an effort to accelerate resolution. We will share additional updates as soon as new information becomes available. Thank you for your continued patience and understanding.Aug <var data-var='date'>15</var>, <var data-var='time'>11:59</var> PDT Update - We continue to actively monitor the elevated 503 “Service Unavailable” responses from the Google API, which surface as 504 errors in the Nylas platform. Our engineering team is working closely with Google Support to help identify and resolve the issue. We have narrowed the impacted operations to the following endpoints: • Message list • Folder list • Thread list • Clean Conversation • Draft list • Event list • Calendar free-busy • Thread retrieve This Google API issue primarily affects list operations, but also others that involve batch calls to Google. Other operations, including Send, are not currently impacted. At this time, the scope and severity of impact remain unchanged. We will continue to provide updates as new information becomes available. Thank you for your continued patience and understanding.Aug <var data-var='date'>14</var>, <var data-var='time'>13:12</var> PDT Identified - We are currently investigating an increase in 503 "Service Unavailable" responses from the Google API, which surface as 504 errors in the Nylas platform. This appears to be due to a temporary issue on Google’s side. Our engineering team is actively monitoring the situation and has opened a support case with Google to obtain more details. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

US - Increased 503 Errors from Google API Services affecting Nylas API v3

Sep <var data-var='date'> 9</var>, <var data-var='time'>15:48</var> PDT Resolved - Sync and webhook latencies in our US data center remain at normal levels, and the backlog of pending webhook deliveries has been fully cleared. Our engineering team will continue to monitor for stability, but no further impact is expected. Thank you for your patience throughout this incident.Sep <var data-var='date'> 9</var>, <var data-var='time'>14:08</var> PDT Update - Sync and webhook latencies in our US data center have returned to normal levels. The backlog of pending webhook deliveries is expected to clear over the next few hours, and we will post an update once this process is complete. Our engineering team will continue to monitor closely to ensure stability, but no further impact is expected at this time. Thank you for your patience while we worked to resolve this issue.Sep <var data-var='date'> 9</var>, <var data-var='time'>13:30</var> PDT Monitoring - Sync and webhook latencies are improving. We are continuing to investigate the root cause and are working to ensure performance remains stable.Sep <var data-var='date'> 9</var>, <var data-var='time'>12:55</var> PDT Investigating - We are investigating elevated sync and webhook latencies in our US data center, primarily impacting Microsoft-connected accounts, with some impact also observed on Google accounts. Our engineering team is analyzing the issue and working to identify the root cause. We will share further updates as more information becomes available. Thank you for your patience.

US – Service Degradation: Elevated Webhook Latencies Primarily Affecting Microsoft Accounts

Sep <var data-var='date'> 8</var>, <var data-var='time'>12:15</var> PDT Resolved - The Nylas Notetaker is once again fully operational on Google Meet. We have not observed any new issues for over an hour, and no further outage reports are appearing across the web. This incident is now resolved.Sep <var data-var='date'> 8</var>, <var data-var='time'>11:20</var> PDT Monitoring - We are observing successful joins again for the Nylas Notetaker on Google Meet, and early reports indicate the upstream Google Meet outage may be resolved (https://downdetector.com/status/google-meet/). We will continue to monitor closely to confirm stability before marking this incident as resolved.Sep <var data-var='date'> 8</var>, <var data-var='time'>11:04</var> PDT Identified - We have identified an ongoing Google Meet service outage that is preventing the Nylas Notetaker from joining meetings. This issue is limited to Google Meet; all other platforms are operating normally. We are monitoring Google’s recovery efforts and will restore full functionality once the upstream service stabilizes. Further updates will be posted as they become available.

Google Meet outage impacting Notetaker

Aug <var data-var='date'>23</var>, <var data-var='time'>11:00</var> PDT Completed - The scheduled maintenance has been completed.Aug <var data-var='date'>23</var>, <var data-var='time'>09:44</var> PDT Verifying - All planned changes for this maintenance have been completed. We are currently verifying system stability and monitoring closely before closing the maintenance window. Further updates will be shared here as needed.Aug <var data-var='date'>23</var>, <var data-var='time'>09:02</var> PDT Update - Between 8:10–8:30 AM PT, we observed a low volume of unexpected "500 Internal Server Errors". Our systems are currently stable, and we will provide any further updates here as needed.Aug <var data-var='date'>23</var>, <var data-var='time'>08:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Aug <var data-var='date'>13</var>, <var data-var='time'>12:57</var> PDT Scheduled - On Saturday August 23rd between 8:00-11:00 AM PT, Nylas will perform scheduled maintenance to upgrade our IMAP High Speed Cache to improve performance and reliability. During this window, customers may experience up to 20 minutes of delays in IMAP sync and webhook delivery. In addition, some duplicate webhooks may be sent during this period. No customer action is required, and impact is expected to be low aside from these temporary delays and duplicate webhooks.

[Scheduled Maintenance] US - API v3 - IMAP Sync & Webhooks

Aug <var data-var='date'>14</var>, <var data-var='time'>12:49</var> PDT Resolved - Over the past 14 days, error rates for Google Send have remained stable and well below pre-incident levels. We have not yet received a formal root cause or remediation details from Google Workspace Support. Once that information is provided, we will publish a Post Mortem to this incident with additional context. Thank you again for your patience throughout this issue.Jul <var data-var='date'>30</var>, <var data-var='time'>14:42</var> PDT Update - Over the past 24 hours, we have continued to observe normal levels of 502 errors from Google Workspace. In fact, the error rate has decreased by more than 5x compared to the period prior to the initial incident. We are still awaiting confirmation from Google regarding the root cause and any remediations that were applied. As such, we will keep this incident in Monitoring status until we receive more information. We will continue to monitor closely and provide updates as new information becomes available. Thank you for your continued patience and understanding.Jul <var data-var='date'>30</var>, <var data-var='time'>08:03</var> PDT Monitoring - As of 11:00 AM PT on July 29, Nylas observed that the rate of Google 502 errors had returned to normal levels. Given prior instances where error rates temporarily subsided before spiking again, we continued active monitoring and reached out to Google Workspace Support for confirmation. At 11:25 PM PT on July 29, Google Support contacted us to ask whether we were still seeing improvement. We confirmed that error rates remained stable and again requested confirmation of any changes made on their end, along with a formal root cause. We are now moving the incident status to Monitoring and will continue to track the situation closely while pressing Google for additional details. Thank you for your continued patience and understanding.Jul <var data-var='date'>28</var>, <var data-var='time'>10:51</var> PDT Update - We are observing a new spike in error rates related to Google’s services, which may result in 504 responses from Nylas APIs. Our team is actively monitoring the situation and remains engaged with Google Workspace Support to obtain clarification and work toward a permanent resolution. We will continue to provide updates as we learn more or receive additional information from Google. Thank you for your patience and understanding.Jul <var data-var='date'>25</var>, <var data-var='time'>13:26</var> PDT Update - Error rates have returned to normal levels and have remained stable, even during peak periods. However, we are keeping this incident open until we receive formal confirmation and additional details from Google. Our team continues to monitor the situation closely and is in active communication with Google Workspace Support to ensure a permanent resolution. Thank you for your continued patience and understanding. We will share further updates as soon as we have new information.Jul <var data-var='date'>24</var>, <var data-var='time'>13:42</var> PDT Identified - We have reopened this incident after observing a recurrence of intermittent 502 errors from Google, which surface as 504 Gateway Timeout responses in the Nylas API. While the error volume is lower than during the initial incident, it has again reached unacceptable levels during peak traffic hours. These upstream errors are impacting message send operations for a subset of users. Most requests succeed on retry; however, we are now also receiving reports of some messages being sent despite a 502 response from Google, which may result in unintended duplicates when retries occur. Our engineering team is actively monitoring the situation and has re-engaged Google Workspace Support. We are escalating through all available channels and providing additional diagnostic data at their request to help identify the root cause and prevent further disruptions. We will continue to share updates as we learn more or receive further information from Google. Thank you for your continued patience and understanding.

Reopened: Intermittent 504 Errors in Nylas Due to Upstream Google 502 Responses

Jul <var data-var='date'>21</var>, <var data-var='time'>12:41</var> PDT Completed - This message serves as notification that the following updates have been made to the Nylas Subprocessors page. The following subprocessors are being added: ClickHouse, Inkeep and Temporal. The following subprocessors are being removed: Datasiv, PartnerPortal, Salesloft. You can find the details regarding what data is being processed by each subprocessor, as well as the applicable components, locations, and entities on the Nylas Subprocessor page at https://www.nylas.com/security/subprocessors/ If you have any questions or concerns about the new subprocessor additions or removals, please contact our Security Team at security@nylas.com.Jul <var data-var='date'>21</var>, <var data-var='time'>12:36</var> PDT Scheduled - This message serves as notification that we are making changes to Nylas' Subprocessors page today

Jul <var data-var='date'>17</var>, <var data-var='time'>15:03</var> PDT Resolved - We are now resolving this incident, as error rates have returned to pre-incident levels and have remained stable—even during peak usage periods. While we have not received formal confirmation or a root cause analysis (RCA) from Google Workspace Support, we continue to follow up with their team and will share any relevant findings if and when they become available. Thank you for your patience throughout this issue.Jul <var data-var='date'>16</var>, <var data-var='time'>09:31</var> PDT Monitoring - While we have not yet received an update from Google, we are now observing that the rate of 502 errors from the Gmail API (which surface as 504 errors via Nylas) has returned to normal levels as of this morning—even during peak usage periods. Given the sustained improvement, we are moving this incident into a Monitoring state. We are continuing to push Google for confirmation of a fix on their side, as well as a root cause analysis (RCA). We will post additional updates here as they become available. If you are still experiencing elevated error rates, please contact us at support@nylas.com.Jul <var data-var='date'>16</var>, <var data-var='time'>05:49</var> PDT Update - We continue to work directly with Google Workspace Support—the team responsible for the Gmail API—and are providing additional logs and data to support their ongoing investigation. While Google has not yet provided an ETA for resolution, we are actively escalating the issue on our end. In parallel, the Nylas engineering team is exploring potential workarounds to reduce the impact of these intermittent errors. We will continue to share updates here as they become available. Thank you for your continued patience—we understand the impact this may have on your workflows and are treating this with the highest urgency.Jul <var data-var='date'>10</var>, <var data-var='time'>17:02</var> PDT Update - We have submitted a high priority bug ticket to Google for further investigation into the intermittent 502 errors (returned by Gmail, surfaced as 504s by Nylas). Along with the ticket, we included detailed logs and a sample payload to support their analysis. We’re continuing to monitor the situation closely and will provide updates as soon as we receive a response from Google. Thank you for your continued patience.Jul <var data-var='date'>10</var>, <var data-var='time'>11:55</var> PDT Update - We’ve observed a noticeable decrease in the number of 502 errors from Google when sending messages (Nylas 504s). However, some errors are still occurring. Our team continues to monitor the situation closely, and we’ll share another update as soon as we have more information. Thank you for your continued patience.Jul <var data-var='date'>10</var>, <var data-var='time'>10:51</var> PDT Investigating - We are currently investigating an increase in 504 errors when sending messages through Google accounts via the v3/message/send endpoint. This appears to be related to a temporary error on Google’s side, as we are receiving the following response from their servers: <tt>502. That's an error. "The server encountered a temporary error and could not complete your request. Please try again in 30 seconds. That's all we know."</tt> Our engineering team is monitoring the situation closely and has opened a support ticket with Google to gain further insights. We will provide updates as more information becomes available. Thank you for your patience and understanding.

Elevated 504 Errors When Sending Messages via Google

Jul <var data-var='date'>14</var>, <var data-var='time'>11:25</var> PDT Resolved - We’ve received an official update from Microsoft confirming that their engineering team has deployed a fix to address the Graph Calendar API issues. This fix has been fully validated for business (work/school) accounts. However, Microsoft has stated they are unable to confirm the behavior for personal Outlook.com accounts. Based on our own monitoring, we’ve observed that while some 500 errors may still occur for personal accounts, our existing safeguards have been effective in mitigating customer impact. As a result, we’ve made these protections permanent within the Nylas platform. We are now resolving this incident but will continue to monitor for any recurrence affecting personal accounts. Thank you for your continued patience and understanding.Jun <var data-var='date'>17</var>, <var data-var='time'>18:29</var> PDT Update - We’ve received confirmation from Microsoft that their backend team has made partial progress toward resolving the upstream Graph Calendar API issue. Specifically, they’ve reported that the API fix is approximately halfway saturated through their infrastructure. Microsoft has extended the tentative ETA for full production rollout to June 30, 2025. In the meantime, our existing workaround remains in place, and core functionality continues to operate with minimal disruption. We will continue to monitor for any changes and provide updates as we receive them from Microsoft. Thanks for your continued patienceJun <var data-var='date'> 6</var>, <var data-var='time'>10:07</var> PDT Update - We’re still monitoring the issue impacting Microsoft’s Graph Calendar API, which affects access to some calendar data. Microsoft has completed internal testing and is now working on finalizing a fix. Although this issue lies outside of our product, we remain in close communication with their support team and are pushing for timely updates. We’ll continue to share more information as it becomes available. Thanks for your patience.Jun <var data-var='date'> 4</var>, <var data-var='time'>10:21</var> PDT Update - 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.Jun <var data-var='date'> 3</var>, <var data-var='time'>10:04</var> PDT Monitoring - 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.Jun <var data-var='date'> 2</var>, <var data-var='time'>17:30</var> PDT Update - 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.Jun <var data-var='date'> 2</var>, <var data-var='time'>16:13</var> PDT Update - 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.Jun <var data-var='date'> 2</var>, <var data-var='time'>12:00</var> PDT Identified - 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: calendars event scheduler 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

Temporary workaround in place for Microsoft Graph API issue

Jul <var data-var='date'>14</var>, <var data-var='time'>07:54</var> PDT Resolved - Microsoft has confirmed that the Graph API errors affecting calendar and event creation were caused by a backend issue related to the deprecation of Skype. This introduced a conflict in the code used to retrieve calendar information, particularly for shared calendars. A fix has now been fully deployed across their infrastructure, and internal testing by Microsoft has validated that the issue was resolved as of July 8, 2025. We have observed no further errors on our side since the fix was applied. Microsoft has also indicated that they are reviewing the impacted code paths to improve testing and prevent similar issues in the future. This incident is now considered resolved. Thank you for your patience throughout this issue.Jun <var data-var='date'>23</var>, <var data-var='time'>14:03</var> PDT Update - The issue remains ongoing, with no change in behavior observed. We have submitted a Severity A support ticket with Microsoft and are currently awaiting their response regarding the Graph API errors impacting a subset of calendar and event creation requests. Our engineering team continues to monitor closely and will provide updates as soon as new information becomes available.Jun <var data-var='date'>23</var>, <var data-var='time'>10:55</var> PDT Identified - We are seeing `ErrorInternalServerError` API errors from a small number of Microsoft grants when attempting to create new events or new calendars in the Nylas API. We have confirmed that these errors are coming from Microsoft Graph API email servers and have reached out to Microsoft to address this issue. Additionally, if you retry a failed API call to create a new calendar, a different error 409 `ErrorFolderExists` may be returned. This error is also from Microsoft Graph API. This does not appear to be affecting any on-premise Exchange (EWS) grants or other email providers.

Is Nylas down?

Nylas status is UP

Lastest published events

[US/EU] Scheduled Maintenance -- Infrastructure Optimization

[Scheduled Maintenance] US - API v3 - Caching Infrastructure Optimization

Update to Nylas' Subprocessors page

Nylas Services, Components and Regions

Recent Nylas events

[US/EU] Scheduled Maintenance -- Infrastructure Optimization

[Scheduled Maintenance] US - API v3 - Caching Infrastructure Optimization

Update to Nylas' Subprocessors page

US – Elevated API Errors and Increased Latency

US - Increased Webhook Latency

Degraded - NoteTaker Transcription

Get your FREE account now,
5 monitors included!

Is Nylas down?

Nylas status is UP

Lastest published events

[US/EU] Scheduled Maintenance -- Infrastructure Optimization

[Scheduled Maintenance] US - API v3 - Caching Infrastructure Optimization

Update to Nylas' Subprocessors page

Nylas Services, Components and Regions

Recent Nylas events

[US/EU] Scheduled Maintenance -- Infrastructure Optimization

[Scheduled Maintenance] US - API v3 - Caching Infrastructure Optimization

Update to Nylas' Subprocessors page

US – Elevated API Errors and Increased Latency

US - Increased Webhook Latency

Degraded - NoteTaker Transcription

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!