Nylas driftsforstyrrelser

1. 19. august 2026 kl. 16.11 UTCinvestigating

   Vi undersøger et problem med manglende eller forsinkede webkroge til Microsoft og Google tilskud i den amerikanske region. EU-regionen og alle IMAP- og EWS-tilskud til begge regioner fungerer korrekt.

2. 19. august 2026 kl. 17.00 UTCinvestigating

   Vi fortsætter med at undersøge forsvundne eller forsinkede webkroge. På baggrund af vores undersøgelse har vi udvidet emnets anvendelsesområde til at omfatte alle udbydere i både USA og EU 's regioner. Vi vil give en anden opdatering som vores undersøgelse skrider frem.

3. 19. august 2026 kl. 17.26 UTCidentified

   Vi arbejder på at implementere et fix for det problem, der forårsager manglende eller forsinkede webkroge på tværs af udbydere i USA og EU-regioner. Vi vil give en anden opdatering som dette arbejde skrider frem.

4. 19. august 2026 kl. 18.01 UTCidentified

   Vi fortsætter med at arbejde på at genoprette webhook levering for berørte tilskud. Vi vil give en anden opdatering som opsving skrider frem.

5. 19. august 2026 kl. 20.20 UTCmonitoring

   Mislykkede... Vi har genvundet alle berørte tilskud, og webhook levering er vendt tilbage til normale niveauer. Nogle tidligere forsinkede meddelelser er stadig under behandling, og vi overvåger nøje den resterende forsinkelse for at sikre, at leveringen lykkes.

6. 19. august 2026 kl. 23.28 UTCresolved

   Alle tjenester er vendt tilbage til normale operationer, og webhook latency og levering volumen er vendt tilbage til forventede niveauer. Alle berørte webkroge blev fundet og leveret. Tak for Deres tålmodighed, mens vi arbejdede på at løse dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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.

1. 6. august 2026 kl. 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 kl. 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 kl. 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. juli 2026 kl. 21.25 UTCresolved

   Webhook trafik er vendt tilbage til normal og alle systemer fungerer korrekt. På grund af den tid, der er gået siden spørgsmålet, er vi ikke længere i stand til at acceptere yderligere anmodninger om at genspille webkroge. Kontakt venligst Nylas Support for hjælp hentning elementer, der kan stadig mangler fra dette tidspunkt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 16.59 UTCmonitoring

   Vi identificerede et problem, der påvirkede leveringen af en lille procentdel af beskeder webkroge til nogle Nylas applikationer i EU-regionen. Spørgsmålet opstod primært mellem 06: 00 og 11: 00 UTC den 24 juli 2026. Webhook levering er kommet sig, og nye webkroge bliver sendt med succes. Nylas-ansøgningerne i den amerikanske region blev ikke berørt. Kunder, der gerne vil have os til at genafspille beskeder webkrogs bør kontakte support @ nylas.com så hurtigt som muligt og inkludere deres Nylas ansøgning ID, når det er muligt. Bemærk venligst, at vi ikke kun kan genspille de webkroge, der ikke blev leveret med succes. En replay vil genstarte alle beskeder webkroge fra starten af hændelsen gennem det tidspunkt, replay udføres og vil generere duplikater. Før kunderne anmoder om et spil, bør de sikre, at deres systemer sikkert kan identificere og håndtere duplikerede webhook-arrangementer. Vi fortsætter med at undersøge den underliggende årsag og nøje overvåge webhook levering.

2. 24. juli 2026 kl. 21.30 UTCresolved

   Webhook trafik har fortsat med at fungere normalt og alle systemer fungerer korrekt. På grund af den tid, der er gået siden spørgsmålet, er vi ikke længere i stand til at acceptere yderligere anmodninger om at genspille webkroge. Du bedes kontakte Nylas Support for bistand hentning elementer, der kan stadig mangler fra denne periode.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 14.32 UTCinvestigating

   Vi er i øjeblikket ved at undersøge nedbrudte fælles satser for Notekaker på Zoom møder (andre møde udbydere er ikke berørt). Vi vil dele opdateringer, da vi har flere oplysninger.

2. 17. juli 2026 kl. 17.21 UTCinvestigating

   Vi fortsætter med at arbejde med vores serviceudbydere og interne ingeniørhold for at undersøge spørgsmålet og evaluere potentielle lempelser. Vi vil give yderligere opdateringer som vores undersøgelse skrider frem.

3. 17. juli 2026 kl. 20.32 UTCinvestigating

   Vores ingeniørhold fortsætter aktivt med at undersøge problemet og følger flere afværgeveje parallelt. De foranstaltninger, der er gennemført indtil nu, har ikke resulteret i en vedvarende forbedring, og vi fokuserer fortsat på at identificere en effektiv afbødning. Vi vil give endnu en opdatering, så snart vi har meningsfulde fremskridt at dele.

4. 23. juli 2026 kl. 16.09 UTCmonitoring

   Mislykkede... Vi har indført ændringer, der har forbedret mødehyppigheden væsentligt. Vi overvåger fortsat ydeevnen nøje og udvider gradvis afbødningen og vurderer yderligere forbedringer. Vi vil give en anden opdatering som dette arbejde skrider frem.

5. 23. juli 2026 kl. 20.54 UTCresolved

   De gennemførte ændringer har genoprettet Notetaker møde deltage ydeevne for Zoom til normale driftsniveauer, og vores overvågning bekræfter, at problemet ikke længere påvirker kunderne. Vi vil fortsat overvåge resultaterne og fortsætte med yderligere forbedringer som en del af vores normale operationer. Denne hændelse er nu løst. Tak for Deres tålmodighed, mens vi arbejdede på at løse dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 13.32 UTCinvestigating

   We are continuing to investigate this issue.

3. 3. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 17.36 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 12.57 UTCresolved

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

1. 6. maj 2026 kl. 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. maj 2026 kl. 16.39 UTCresolved

   We have updated our systems and webhooks have returned to normal

1. 4. maj 2026 kl. 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. maj 2026 kl. 15.25 UTCresolved

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

1. 30. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 17.30 UTCresolved

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

1. 14. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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.