Cronologia delle interruzioni di Nylas

1. 19 agosto 2026 alle ore 16:11 UTCinvestigating

   Stiamo indagando su un problema con webhooks mancanti o ritardati per le borse Microsoft e Google nella regione degli Stati Uniti. La regione dell'UE e tutte le sovvenzioni IMAP e EWS per entrambe le regioni stanno funzionando correttamente.

2. 19 agosto 2026 alle ore 17:00 UTCinvestigating

   Stiamo continuando a indagare sui webhook mancanti o ritardati. Sulla base della nostra indagine, abbiamo ampliato la portata della questione per includere tutti i fornitori sia nelle regioni degli Stati Uniti che dell'UE. Forneremo un altro aggiornamento mentre la nostra indagine progredisce.

3. 19 agosto 2026 alle ore 17:26 UTCidentified

   Stiamo lavorando per implementare una soluzione per il problema causando webhooks mancanti o ritardati tra i fornitori nelle regioni degli Stati Uniti e dell'UE. Forneremo un altro aggiornamento mentre questo lavoro progredisce.

4. 19 agosto 2026 alle ore 18:01 UTCidentified

   Stiamo continuando a lavorare per ripristinare la consegna webhook per le sovvenzioni interessate. Forneremo un altro aggiornamento come progressi di recupero.

5. 19 agosto 2026 alle ore 20:20 UTCmonitoring

   Mitigati - Abbiamo recuperato tutti i contributi interessati, e la consegna webhook è tornato a livelli normali. Alcuni messaggi precedentemente ritardati sono ancora in fase di elaborazione, e stiamo monitorando attentamente il backlog rimanente per garantire la consegna completa con successo.

6. 19 agosto 2026 alle ore 23:28 UTCresolved

   Tutti i servizi sono tornati alle normali operazioni, e webhook latenza e il volume di consegna sono tornati ai livelli previsti. Tutti i webhooks interessati sono stati recuperati e consegnati con successo. Grazie per la vostra pazienza mentre abbiamo lavorato per affrontare questo problema.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 14 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 luglio 2026 alle ore 21:25 UTCresolved

   Il traffico Webhook è tornato alla normalità e tutti i sistemi funzionano correttamente. A causa dell'intervallo di tempo trascorso dal problema, non siamo più in grado di accettare ulteriori richieste di rigiocare i webhooks. Si prega di raggiungere il supporto Nylas per l'assistenza di recupero oggetti che possono ancora essere mancanti da questo momento.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 16:59 UTCmonitoring

   Abbiamo identificato un problema che ha interessato la consegna di una piccola percentuale di messaggi webhooks per alcune applicazioni Nylas nella regione dell'UE. Il problema si è verificato principalmente tra le 06:00 e le 11:00 UTC il 24 luglio 2026. Webhook consegna ha recuperato, e nuovi webhooks vengono inviati con successo. Le applicazioni di Nylas nella regione degli Stati Uniti non sono state interessate. I clienti che vorrebbero rifare i messaggi webhooks dovrebbero contattare [email protected] il prima possibile e includere i loro ID applicativi Nylas, quando disponibili. Si prega di notare che non possiamo riprodurre solo i webhooks che non sono stati consegnati con successo. Un replay risenderà tutti i webhooks del messaggio dall'inizio dell'incidente attraverso il tempo che la riproduzione viene eseguita e genererà duplicati. Prima di richiedere un replay, i clienti dovrebbero garantire che i loro sistemi possano identificare e gestire in modo sicuro gli eventi webhook duplicati. Stiamo continuando a indagare la causa sottostante e monitorare da vicino la consegna webhook.

2. 24 luglio 2026 alle ore 21:30 UTCresolved

   Il traffico Webhook ha continuato a funzionare normalmente e tutti i sistemi sono operativi correttamente. A causa del tempo trascorso dal problema, non siamo più in grado di accettare ulteriori richieste di rigiocare i webhooks. Si prega di contattare Nylas Support per il recupero di articoli che potrebbero ancora mancare da questo periodo.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 17 luglio 2026 alle ore 14:32 UTCinvestigating

   Attualmente stiamo indagando sui tassi di aggregazione degradati per i Notetaker sulle riunioni di Zoom (altri fornitori di riunioni non sono interessati). Condividiamo gli aggiornamenti come abbiamo più informazioni.

2. 17 luglio 2026 alle ore 17:21 UTCinvestigating

   Continuiamo a lavorare con i nostri fornitori di servizi e team di ingegneria interna per indagare il problema e valutare le potenziali mitigazioni. Vi forniremo ulteriori aggiornamenti come la nostra indagine progredisce.

3. 17 luglio 2026 alle ore 20:32 UTCinvestigating

   I nostri team di ingegneria continuano a indagare attivamente il problema e stanno perseguendo più percorsi di bonifica in parallelo. Le misure attuate finora non hanno portato ad un miglioramento sostenuto, e noi rimaniamo concentrati sull'individuazione di una mitigazione efficace. Forneremo un altro aggiornamento non appena avremo progressi significativi da condividere.

4. 23 luglio 2026 alle ore 16:09 UTCmonitoring

   Mitigati - Abbiamo implementato modifiche che hanno migliorato materialmente i tassi di successo. Stiamo continuando a monitorare attentamente le prestazioni e stiamo espandendo progressivamente la mitigazione, valutando miglioramenti aggiuntivi. Forneremo un altro aggiornamento mentre questo lavoro progredisce.

5. 23 luglio 2026 alle ore 20:54 UTCresolved

   Le modifiche implementate hanno ripristinato l'incontro Notetaker unire le prestazioni per Zoom a livelli operativi normali, e il nostro monitoraggio conferma che il problema non riguarda più i clienti. Continueremo a monitorare le prestazioni e a perseguire ulteriori miglioramenti nell'ambito delle nostre normali operazioni. Questo incidente è ora risolto. Grazie per la vostra pazienza mentre abbiamo lavorato per affrontare questo problema.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 13:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 luglio 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 17:36 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 12:57 UTCresolved

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

1. 6 maggio 2026 alle ore 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 maggio 2026 alle ore 16:39 UTCresolved

   We have updated our systems and webhooks have returned to normal

1. 4 maggio 2026 alle ore 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 maggio 2026 alle ore 15:25 UTCresolved

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

1. 30 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 17:30 UTCresolved

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

1. 14 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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.