Historial de interrupciones de Nylas

1. 19 de agosto de 2026 a las 16:11 UTCinvestigating

   Estamos investigando un problema con fallos web perdidos o retrasados para las subvenciones de Microsoft y Google en la región de Estados Unidos. La región de la UE y todos los subsidios IMAP y EWS para ambas regiones están funcionando correctamente.

2. 19 de agosto de 2026 a las 17:00 UTCinvestigating

   Seguimos investigando los fallos web desaparecidos o retrasados. Sobre la base de nuestra investigación, hemos ampliado el alcance de la cuestión para incluir a todos los proveedores tanto en las regiones de EE.UU. como en la UE. Proporcionaremos otra actualización a medida que avance nuestra investigación.

3. 19 de agosto de 2026 a las 17:26 UTCidentified

   Estamos trabajando para implementar una solución para el problema causando faltas o retrasos webhooks a través de proveedores en las regiones de EE.UU. y UE. Proporcionaremos otra actualización a medida que este trabajo avance.

4. 19 de agosto de 2026 a las 18:01 UTCidentified

   Seguimos trabajando en la restauración de la entrega de ganchos web para las subvenciones afectadas. Proporcionaremos otra actualización a medida que avance la recuperación.

5. 19 de agosto de 2026 a las 20:20 UTCmonitoring

   Mitigated - Hemos recuperado todas las subvenciones afectadas, y la entrega de webhook ha regresado a niveles normales. Aún se están tramitando algunos mensajes retrasados anteriormente, y estamos monitoreando de cerca el atraso restante para asegurar que la entrega se complete con éxito.

6. 19 de agosto de 2026 a las 23:28 UTCresolved

   Todos los servicios han regresado a las operaciones normales, y el volumen de latencia y entrega de webhook ha regresado a los niveles previstos. Todos los webhooks afectados fueron recuperados y entregados con éxito. Gracias por su paciencia mientras trabajamos para abordar este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 19:53 UTCmonitoring

   Hemos observado un gran aumento de las notificaciones de Microsoft Graph hoy y esto ha afectado nuestra infraestructura para dar lugar a mayores retrasos en los mensajes nuevos y actualizados para todas las subvenciones de todos los proveedores. Hemos hecho cambios en nuestra infraestructura para manejar mejor este aumento del tráfico de notificaciones y vemos que las demoras se han reducido. Seguimos vigilando este tráfico de notificaciones inusualmente elevado e investigando la fuente de este tráfico de notificaciones más elevado.

2. 11 de agosto de 2026 a las 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 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 6 de agosto de 2026 a las 14:37 UTCinvestigating

   Estamos investigando tasas elevadas de respuestas HTTP 500 para el punto final /messages API que afecta las subvenciones IMAP en la región de los Estados Unidos. Algunas solicitudes pueden fallar como resultado. La cuestión no está afectando subvenciones para otros proveedores, otros puntos finales de API, o la región de la UE. La tasa general de error sigue siendo baja. Proporcionaremos otra actualización a medida que avance nuestra investigación.

2. 6 de agosto de 2026 a las 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 de agosto de 2026 a las 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].

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de julio de 2026 a las 21:25 UTCresolved

   El tráfico de Webhook ha regresado a la normalidad y todos los sistemas funcionan correctamente. Debido al tiempo transcurrido desde el problema, ya no podemos aceptar ninguna solicitud adicional para reproducir los webhooks. Póngase en contacto con Nylas Support para recibir asistencia que pueda seguir faltando desde este momento.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de julio de 2026 a las 16:59 UTCmonitoring

   Identificamos un problema que afectó la entrega de un pequeño porcentaje de webhooks de mensajes para algunas aplicaciones de Nylas en la región de la UE. El problema ocurrió principalmente entre las 06:00 y las 11:00 UTC el 24 de julio de 2026. La entrega de Webhook se ha recuperado, y se envían nuevos webhooks con éxito. Las aplicaciones de Nylas en la región de Estados Unidos no se vieron afectadas. Los clientes que deseen volver a reproducir mensajes webhooks deben ponerse en contacto con [email protected] tan pronto como sea posible e incluir sus IDs de aplicación de Nylas, cuando estén disponibles. Tenga en cuenta que no podemos volver a reproducir sólo los webhooks que no fueron entregados con éxito. Una repetición reenviará todos los mensajes webhooks desde el inicio del incidente a través del tiempo que se realiza la repetición y generará duplicados. Antes de solicitar una repetición, los clientes deben asegurarse de que sus sistemas puedan identificar y manejar los eventos duplicados de webhook. Seguimos investigando la causa subyacente y vigilando de cerca la entrega de webhook.

2. 24 de julio de 2026 a las 21:30 UTCresolved

   El tráfico de Webhook ha seguido funcionando normalmente y todos los sistemas están funcionando correctamente. Debido al tiempo transcurrido desde la cuestión, ya no podemos aceptar solicitudes adicionales para volver a reproducir los webhooks. Sírvase comunicarse con Nylas Support para recibir asistencia que pueda seguir faltando desde este período.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de julio de 2026 a las 14:32 UTCinvestigating

   Actualmente estamos investigando tasas de afiliación degradadas para Notetaker en reuniones de Zoom (otros proveedores de reuniones no están afectados). Compartiremos actualizaciones ya que tenemos más información.

2. 17 de julio de 2026 a las 17:21 UTCinvestigating

   Seguimos trabajando con nuestros proveedores de servicios y equipos de ingeniería interna para investigar la cuestión y evaluar posibles mitigación. Proporcionaremos actualizaciones adicionales a medida que avance nuestra investigación.

3. 17 de julio de 2026 a las 20:32 UTCinvestigating

   Nuestros equipos de ingeniería siguen investigando activamente la cuestión y están siguiendo múltiples vías de rehabilitación en paralelo. Las medidas aplicadas hasta ahora no han dado lugar a una mejora sostenida y seguimos centrándonos en identificar una mitigación efectiva. Proporcionaremos otra actualización tan pronto como tengamos avances significativos para compartir.

4. 23 de julio de 2026 a las 16:09 UTCmonitoring

   Mitigated - Hemos desplegado cambios que han mejorado significativamente las tasas de éxito de las reuniones. Seguimos vigilando de cerca el desempeño y estamos ampliando progresivamente la mitigación y evaluando mejoras adicionales. Proporcionaremos otra actualización a medida que este trabajo avance.

5. 23 de julio de 2026 a las 20:54 UTCresolved

   Los cambios desplegados han restaurado el rendimiento de la reunión de Notetaker para Zoom a niveles operativos normales, y nuestro monitoreo confirma que el problema ya no afecta a los clientes. Seguiremos monitoreando el desempeño y seguiremos mejorando como parte de nuestras operaciones normales. Este incidente ya está resuelto. Gracias por su paciencia mientras trabajamos para abordar este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 13:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 de julio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 17:36 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 12:57 UTCresolved

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

1. 6 de mayo de 2026 a las 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 de mayo de 2026 a las 16:39 UTCresolved

   We have updated our systems and webhooks have returned to normal

1. 4 de mayo de 2026 a las 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 de mayo de 2026 a las 15:25 UTCresolved

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

1. 30 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 17:30 UTCresolved

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

1. 14 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 2: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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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.