Nylas 中断历史

1. 2026年8月19日 UTC 16:11investigating

   我们正在调查美国地区微软和Google赠款的网络选择缺失或延迟的问题。 欧盟区域以及IMAP和EWS为这两个区域提供的所有赠款正在正确运作.

2. 2026年8月19日 UTC 17:00investigating

   我们正在继续调查失踪或被拖延的网络攻击。 根据我们的调查,我们扩大了这一问题的范围,将美国和欧盟地区的所有供应商都包括在内。 我们将在调查进展时提供另一个最新情况.

3. 2026年8月19日 UTC 17:26identified

   我们正在努力解决这个问题,导致美国和欧盟地区供应商之间出现缺失或延误。 随着这项工作的进展,我们将提供另一个最新情况.

4. 2026年8月19日 UTC 18:01identified

   我们正继续努力恢复对受影响赠款的网上支付。 随着复苏的进展,我们将提供另一个最新情况.

5. 2026年8月19日 UTC 20:20monitoring

   减轻 - 我们收回了所有受影响的赠款,网上支付已恢复正常水平。 一些先前被延误的信息仍在处理中,我们正在密切监测所剩积压,以确保顺利交付.

6. 2026年8月19日 UTC 23:28resolved

   所有服务已恢复正常运作,网络故障和交付量已恢复到预期水平。 所有受影响的网络呼声都成功恢复和交付。 谢谢你在我们努力解决这一问题期间的耐心.

自动翻译自官方事件更新。

1. 2026年8月14日 UTC 14:15investigating

   We are experiencing elevated error rates for the /attachment API endpoint affecting EWS grants for on-premises and hosted Microsoft Exchange providers in both the US and EU regions. Other grant types, including Microsoft Graph, Google, and IMAP, are not affected.

2. 2026年8月14日 UTC 14:39monitoring

   Mitigated - We have implemented changes to address the elevated error rates affecting /attachment API requests for Microsoft Exchange (EWS) grants and are seeing recovery. We are continuing to monitor performance to confirm full recovery across both the US and EU regions.

3. 2026年8月14日 UTC 15:02monitoring

   Error rates have returned to normal levels for /attachment API requests affecting Microsoft Exchange (EWS) grants in both the US and EU regions. We are continuing to monitor performance to confirm the issue remains fully resolved.

4. 2026年8月14日 UTC 17:13monitoring

   Error rates for /attachment API requests affecting Microsoft Exchange (EWS) grants remain at normal levels across both the US and EU regions. We are continuing to monitor closely to confirm the issue remains fully resolved.

5. 2026年8月14日 UTC 17:21resolved

   Error rates for /attachment API requests affecting Microsoft Exchange (EWS) grants have remained at normal levels across both the US and EU regions, and our monitoring confirms that the issue is no longer affecting customers. Thank you for your patience while we worked to address this issue. If you require additional assistance, please contact [email protected].

1. 2026年8月11日 UTC 19:53monitoring

   We have observed a large increase in notification traffic from Microsoft Graph today, which resulted in higher latencies for new and updated messages across providers in the US region. We have made changes to our infrastructure to better handle the increased traffic, and latencies have reduced. We are continuing to monitor performance and investigate the source of the unusually high notification traffic. The EU region is not affected.

2. 2026年8月11日 UTC 20:12monitoring

   Mitigated - Sync latencies for new and updated messages in the US region have returned to normal operating levels following the infrastructure changes implemented earlier. We have mitigated the customer impact and are continuing to monitor performance while we investigate the unusually high notification traffic that contributed to the incident. The EU region remains unaffected.

3. 2026年8月11日 UTC 22:16resolved

   Sync latencies for new and updated messages in the US region have remained at normal operating levels, and our systems are stable. The changes implemented during the incident have mitigated the impact of the unusually high notification traffic. We will continue to monitor and address that traffic as part of our normal operations, but it is no longer affecting broader message synchronization performance. The EU region was not affected. This incident is now resolved. Thank you for your patience while we worked to address this issue.

1. 2026年8月6日 UTC 14:37investigating

   We are investigating elevated rates of HTTP 500 responses for the /messages API endpoint affecting IMAP grants in the US region. Some requests may fail as a result. The issue is not affecting grants for other providers, other API endpoints, or the EU region. The overall error rate remains low. We will provide another update as our investigation progresses.

2. 2026年8月6日 UTC 16:36monitoring

   Error rates and request latency for the /messages API endpoint have returned to normal operating levels. We will continue to monitor performance to confirm the mitigation remains effective.

3. 2026年8月6日 UTC 18:30resolved

   Error rates and request latency for the /messages API endpoint have remained at normal operating levels, and our monitoring confirms that the issue is no longer affecting customers. This incident is now resolved. Thank you for your patience while we worked to address it. If you require additional assistance, please contact [email protected].

1. 2026年7月24日 UTC 21:25resolved

   Webhook流量已恢复正常,所有系统运行正常. 由于这个问题已经过去很长时间,我们不再能够接受任何关于重新播放网络呼声的额外请求。 请联系Nylas支助公司, 要求协助收回目前可能仍然丢失的物品.

自动翻译自官方事件更新。

1. 2026年7月24日 UTC 16:59monitoring

   我们确定了一个影响欧盟区域一些Nylas应用的微小比例信息发送的问题。 发行时间主要为协调世界时2026年7月24日06:00至11:00. Webhook 发送已恢复,新的webhooks 正在成功发送中. 美国地区的Nylas应用没有受到影响。 希望我们重新播放消息的客户应尽快与支持@nylas.com联系,并在有Nylas应用程序ID时加入。 请注意, 我们不能只重放未成功交付的网络呼号 。 重放会从事件开始到重放时重新发送所有消息webhooks,并产生重复. 在请求重播之前,客户应当确保其系统能够安全地识别和处理重复的webhook事件. 我们正在继续调查其根本原因并密切监测网上信息发送情况.

2. 2026年7月24日 UTC 21:30resolved

   Webhook流量继续正常运行,所有系统正常运行. 由于这个问题已经过去很长时间,我们不再能够接受更多关于重新播放网络呼号的请求。 请联系Nylas, 寻求援助.

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 14:32investigating

   我们目前正在调查Zoom会议(其他会议提供者不受影响)的Notaker的退化加入率。 了解更多信息后,我们将分享最新情况.

2. 2026年7月17日 UTC 17:21investigating

   我们继续与我们的服务提供者和内部工程小组合作,调查这一问题并评估可能的缓解措施。 随着调查的进展,我们将提供更多的最新情况.

3. 2026年7月17日 UTC 20:32investigating

   我们的工程小组继续积极调查这一问题,并同时走多种补救道路。 迄今所实施的措施没有导致持续改善,我们仍侧重于确定有效的缓解措施。 一旦我们取得有意义的进展,我们将提供另一个最新情况.

4. 2026年7月23日 UTC 16:09monitoring

   减轻 - 我们进行了一些改革,这些改革大大改善了会议的成功率。 我们正在继续密切监测执行情况并逐步扩大缓解工作,同时评估进一步的改进。 随着这项工作的进展,我们将提供另一个最新情况.

5. 2026年7月23日 UTC 20:54resolved

   所部署的改变使Notetaker会议恢复了Zoom的结合性能,达到正常的操作水平,我们的监测证实,这个问题不再影响客户。 我们将继续监测执行情况并寻求进一步改善,作为我们正常业务的一部分。 这一事件现在已经得到解决。 谢谢你在我们努力解决这一问题期间的耐心.

自动翻译自官方事件更新。

1. 2026年7月7日 UTC 15:03investigating

   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.

2. 2026年7月7日 UTC 16:58monitoring

   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.

3. 2026年7月7日 UTC 17:17resolved

   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.

1. 2026年7月3日 UTC 13:29investigating

   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.

2. 2026年7月3日 UTC 13:32investigating

   We are continuing to investigate this issue.

3. 2026年7月3日 UTC 14:17resolved

   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.

1. 2026年6月25日 UTC 17:34identified

   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.

2. 2026年6月25日 UTC 17:36monitoring

   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.

3. 2026年6月25日 UTC 17:36monitoring

   We are continuing to monitor for any further issues.

4. 2026年6月25日 UTC 17:45resolved

   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.

1. 2026年6月24日 UTC 21:21investigating

   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.

2. 2026年6月24日 UTC 21:50resolved

   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.

1. 2026年6月4日 UTC 23:27identified

   We have identified an issue affecting grant creation and authorization requests in our v3 environments (US and EU). Some customers may experience errors when attempting to create or authorize grants. Our Engineering team has identified the likely cause and is currently deploying a hotfix. We will continue monitoring the deployment and will provide the next update within 30 minutes, or sooner if we have meaningful progress to share.

2. 2026年6月4日 UTC 23:52resolved

   The issue has been resolved, and grant creation and authorization requests are operating normally. Our engineering team identified and corrected an issue introduced by a recent billing system deployment. We have validated recovery and will continue monitoring to ensure ongoing stability. Thank you for your patience during this incident. If you have any questions or concerns, please contact [email protected].

1. 2026年5月20日 UTC 18:50identified

   Starting at approximately 8:59 AM PT, our 3rd party provider Oxylabs experienced an outage that is preventing Nylas Notetakers from joining some Zoom and Google Meet meetings. We are working with the provider and deploying internal mitigation steps now

2. 2026年5月20日 UTC 18:52monitoring

   We have deployed mitigation steps while we wait on Oxylabs, and join rates are improving once again. We will continue to monitor and post updates as available.

3. 2026年5月20日 UTC 18:56resolved

   Oxylabs has fully restored their services, and we are seeing join rates returning to normal levels. We will continue to monitor closely, and working with Oxylabs to ensure this does not happen in the future. Thank you for your patience during this incident. If you have any further questions or concerns, please contact [email protected].

1. 2026年5月14日 UTC 18:09investigating

   We are investigating sending failures with our Transactional Send (Beta) and Agent Account (Beta) features. The Nylas API is not affected and is still running correctly. This issue is strictly limited to those two beta features.

2. 2026年5月15日 UTC 12:57resolved

   The incident has been resolved by our third party subprocessor. We will continue to monitor closely.

1. 2026年5月6日 UTC 15:28monitoring

   We are currently investigating elevated latency affecting Gmail realtime (Pub/Sub) event delivery in the US region. Customers may experience delayed webhooks notifications. The issue was initially caused by an expired SSL certificate, which has since been addressed. However, the system has not fully recovered and latency remains elevated. We will provide an update soon.

2. 2026年5月6日 UTC 16:39resolved

   We have updated our systems and webhooks have returned to normal

1. 2026年5月4日 UTC 14:03investigating

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

2. 2026年5月4日 UTC 15:25resolved

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

1. 2026年4月30日 UTC 12:30investigating

   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.

2. 2026年4月30日 UTC 12:39monitoring

   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.

3. 2026年4月30日 UTC 15:45resolved

   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.

1. 2026年4月15日 UTC 17:10investigating

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

2. 2026年4月15日 UTC 17:30resolved

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

1. 2026年4月14日 UTC 15:19investigating

   We are currently investigating an issue where some Nylas Notetakers are not correctly joining Google Meet events. This does not appear to affect other meeting providers or any other parts of the API.

2. 2026年4月14日 UTC 18:28monitoring

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

3. 2026年4月15日 UTC 02:39resolved

   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.

1. 2026年2月24日 UTC 19:30investigating

   We are currently experiencing elevated API error rates and increased latency in the US v3 production environment, affecting a subset of customers. This may result in intermittent 500 errors and delayed webhooks. Our engineering team has identified the issue and is actively working on mitigation. We will continue to share updates here.

2. 2026年2月24日 UTC 20:08identified

   We have identified the underlying issue contributing to elevated API error rates and increased latency in the US v3 production environment. Our engineering team is actively working on mitigation. Customers may continue to experience intermittent 500 errors and delayed webhooks while mitigation efforts are underway. We will continue to provide updates as progress is made.

3. 2026年2月24日 UTC 21:16monitoring

   Mitigation steps have been successfully implemented, and API error rates and latency in the US v3 production environment have returned to normal levels. We are continuing to closely monitor the environment to ensure stability. We will provide a final update once we confirm the issue is fully resolved.

4. 2026年2月24日 UTC 21:25resolved

   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.