Istoricul incidentelor Nylas

1. 19 august 2026 la 16:11 UTCinvestigating

   Investigăm o problemă legată de lipsa sau întârzierea site-urilor web pentru granturile Microsoft și Google în regiunea SUA. Regiunea UE și toate granturile IMAP și EWS pentru ambele regiuni funcționează corect.

2. 19 august 2026 la 17:00 UTCinvestigating

   Continuăm să investigăm lipsa sau întârzierile site-ului web. Pe baza investigaţiei noastre, am extins domeniul de aplicare al problemei pentru a include toţi furnizorii din SUA şi din regiunile UE. Vom oferi o altă actualizare pe măsură ce ancheta noastră progresează.

3. 19 august 2026 la 17:26 UTCidentified

   Ne străduim să punem în aplicare o soluţie pentru această problemă care cauzează lipse sau întârzieri la nivelul furnizorilor din SUA şi din regiunile UE. Vom oferi o altă actualizare pe măsură ce această activitate progresează.

4. 19 august 2026 la 18:01 UTCidentified

   Continuăm să lucrăm la restabilirea livrării prin webhook pentru granturile afectate. Vom oferi o altă actualizare pe măsură ce redresarea progresează.

5. 19 august 2026 la 20:20 UTCmonitoring

   Mitigat - Am recuperat toate granturile afectate, și livrarea webhook a revenit la niveluri normale. Unele mesaje întârziate anterior sunt încă în curs de procesare, și noi monitorizăm îndeaproape backlog-ul rămas pentru a asigura livrarea completă cu succes.

6. 19 august 2026 la 23:28 UTCresolved

   Toate serviciile au revenit la operațiunile normale, iar latența webhook și volumul de livrare au revenit la nivelurile preconizate. Toate site-urile afectate au fost recuperate și livrate cu succes. Vă mulțumim pentru răbdare în timp ce am lucrat pentru a aborda această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 14 august 2026 la 14:15 UTCinvestigating

   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. 14 august 2026 la 14:39 UTCmonitoring

   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. 14 august 2026 la 15:02 UTCmonitoring

   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. 14 august 2026 la 17:13 UTCmonitoring

   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. 14 august 2026 la 17:21 UTCresolved

   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. 11 august 2026 la 19:53 UTCmonitoring

   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. 11 august 2026 la 20:12 UTCmonitoring

   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. 11 august 2026 la 22:16 UTCresolved

   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.

Traducere automată din actualizarea oficială a incidentului.

1. 6 august 2026 la 14:37 UTCinvestigating

   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. 6 august 2026 la 16:36 UTCmonitoring

   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. 6 august 2026 la 18:30 UTCresolved

   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. 24 iulie 2026 la 21:25 UTCresolved

   Traficul Webhook a revenit la normal și toate sistemele funcționează corect. Având în vedere intervalul de timp scurs de la emisiune, nu mai suntem în măsură să accepte orice cereri suplimentare de a reda webhooks. Vă rugăm să ajungeţi la Nylas Support pentru asistenţă pentru recuperarea obiectelor care pot fi încă lipsesc din acest moment.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 16:59 UTCmonitoring

   Am identificat o problemă care a afectat furnizarea unui procent mic de site-uri web pentru unele aplicații Nylas în regiunea UE. Problema a avut loc în primul rând între 06:00 și 11:00 UTC la 24 iulie 2026. Livrarea Webhook a revenit, iar noile site-uri sunt trimise cu succes. Aplicațiile Nylas din regiunea SUA nu au fost afectate. Clienţii care ar dori să redăm mesajele webhooks ar trebui să contacteze [email protected] cât mai curând posibil şi să includă ID-urile lor de aplicaţie Nylas, atunci când sunt disponibile. Vă rugăm să rețineți că nu putem reda doar site-urile web care nu au fost livrate cu succes. O reluare va retrimite toate mesajele webhooks de la începutul incidentului prin timpul în care reluarea este efectuată și va genera duplicate. Înainte de a solicita o reluare, clienții ar trebui să se asigure că sistemele lor pot identifica și gestiona în siguranță evenimente duplicate de webhook. Continuăm să investigăm cauza de bază și să monitorizăm îndeaproape livrarea webhook.

2. 24 iulie 2026 la 21:30 UTCresolved

   Traficul Webhook a continuat să funcționeze normal și toate sistemele funcționează corect. Datorita timpului scurs de la problema, nu mai putem accepta cereri suplimentare de reluare a site-urilor web. Vă rugăm să contactaţi Nylas Support pentru asistenţă în recuperarea elementelor care pot fi încă lipsă din această perioadă.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iulie 2026 la 14:32 UTCinvestigating

   Investigăm în prezent ratele de aderare degradate pentru Notetaker la reuniunile Zoom (alţi furnizori de întâlniri nu sunt afectaţi). Vom face schimb de actualizări deoarece avem mai multe informații.

2. 17 iulie 2026 la 17:21 UTCinvestigating

   Continuăm să lucrăm cu furnizorii noștri de servicii și cu echipele noastre de inginerie internă pentru a investiga problema și a evalua posibilele atenuări. Vom furniza actualizări suplimentare pe măsură ce investigaţia noastră progresează.

3. 17 iulie 2026 la 20:32 UTCinvestigating

   Echipele noastre de inginerie continuă să investigheze în mod activ problema și urmăresc mai multe căi de remediere în paralel. Măsurile puse în aplicare până în prezent nu au dus la o îmbunătățire susținută și ne concentrăm în continuare pe identificarea unei atenuări eficiente. Vom furniza o altă actualizare de îndată ce vom avea progrese semnificative pentru a împărtăși.

4. 23 iulie 2026 la 16:09 UTCmonitoring

   Mitigat - Am implementat schimbări care au îmbunătăţit semnificativ ratele de succes. Continuăm să monitorizăm îndeaproape performanța și extindem treptat atenuarea, evaluând în același timp îmbunătățiri suplimentare. Vom oferi o altă actualizare pe măsură ce această activitate progresează.

5. 23 iulie 2026 la 20:54 UTCresolved

   Modificările efectuate au restabilit întâlnirea Notetaker se alăture performanței pentru Zoom la niveluri normale de operare, iar monitorizarea noastră confirmă faptul că problema nu mai afectează clienții. Vom continua să monitorizăm performanța și să continuăm îmbunătățirile ca parte a operațiunilor noastre normale. Acest incident este acum rezolvat. Vă mulțumim pentru răbdare în timp ce am lucrat pentru a aborda această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 15:03 UTCinvestigating

   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. 7 iulie 2026 la 16:58 UTCmonitoring

   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. 7 iulie 2026 la 17:17 UTCresolved

   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. 3 iulie 2026 la 13:29 UTCinvestigating

   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. 3 iulie 2026 la 13:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 iulie 2026 la 14:17 UTCresolved

   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. 25 iunie 2026 la 17:34 UTCidentified

   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. 25 iunie 2026 la 17:36 UTCmonitoring

   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. 25 iunie 2026 la 17:36 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25 iunie 2026 la 17:45 UTCresolved

   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. 24 iunie 2026 la 21:21 UTCinvestigating

   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. 24 iunie 2026 la 21:50 UTCresolved

   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. 4 iunie 2026 la 23:27 UTCidentified

   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. 4 iunie 2026 la 23:52 UTCresolved

   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. 20 mai 2026 la 18:50 UTCidentified

   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. 20 mai 2026 la 18:52 UTCmonitoring

   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. 20 mai 2026 la 18:56 UTCresolved

   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. 14 mai 2026 la 18:09 UTCinvestigating

   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. 15 mai 2026 la 12:57 UTCresolved

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

1. 6 mai 2026 la 15:28 UTCmonitoring

   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. 6 mai 2026 la 16:39 UTCresolved

   We have updated our systems and webhooks have returned to normal

1. 4 mai 2026 la 14:03 UTCinvestigating

   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. 4 mai 2026 la 15:25 UTCresolved

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

1. 30 aprilie 2026 la 12:30 UTCinvestigating

   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. 30 aprilie 2026 la 12:39 UTCmonitoring

   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. 30 aprilie 2026 la 15:45 UTCresolved

   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. 15 aprilie 2026 la 17:10 UTCinvestigating

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

2. 15 aprilie 2026 la 17:30 UTCresolved

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

1. 14 aprilie 2026 la 15:19 UTCinvestigating

   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. 14 aprilie 2026 la 18:28 UTCmonitoring

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

3. 15 aprilie 2026 la 02:39 UTCresolved

   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. 24 februarie 2026 la 19:30 UTCinvestigating

   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. 24 februarie 2026 la 20:08 UTCidentified

   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. 24 februarie 2026 la 21:16 UTCmonitoring

   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. 24 februarie 2026 la 21:25 UTCresolved

   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.