Störungsverlauf von Nylas

1. 19. August 2026 um 16:11 UTCinvestigating

   Wir untersuchen ein Problem mit fehlenden oder verzögerten Webhooks für Microsoft- und Google-Zuschüsse in der US-Region. Die EU-Region und alle IMAP- und EWS-Zuschüsse für beide Regionen funktionieren korrekt.

2. 19. August 2026 um 17:00 UTCinvestigating

   Wir untersuchen weiterhin fehlende oder verzögerte Webhooks. Auf der Grundlage unserer Untersuchung haben wir den Umfang des Problems auf alle Anbieter sowohl in den USA als auch in der EU erweitert. Wir werden ein weiteres Update zur Verfügung stellen, wenn unsere Untersuchung fortschreitet.

3. 19. August 2026 um 17:26 UTCidentified

   Wir arbeiten daran, eine Lösung für das Problem zu finden, das fehlende oder verzögerte Webhooks bei Anbietern in den USA und den EU-Regionen verursacht. Wir werden ein weiteres Update zur Verfügung stellen, wenn diese Arbeit fortschreitet.

4. 19. August 2026 um 18:01 UTCidentified

   Wir arbeiten weiter daran, die Webhook-Lieferung für betroffene Zuschüsse wiederherzustellen. Wir werden ein weiteres update zur verfügung stellen, wenn die wiederherstellung fortschreitet.

5. 19. August 2026 um 20:20 UTCmonitoring

   Gemindert - Wir haben alle betroffenen Zuschüsse zurückerhalten, und die Webhook-Lieferung ist auf ein normales Niveau zurückgekehrt. Einige zuvor verspätete Nachrichten werden immer noch verarbeitet, und wir überwachen den verbleibenden Rückstand genau, um sicherzustellen, dass die Lieferung erfolgreich abgeschlossen wird.

6. 19. August 2026 um 23:28 UTCresolved

   Alle Dienste sind in den normalen Betrieb zurückgekehrt, und die Webhook-Latenz und das Liefervolumen sind auf das erwartete Niveau zurückgekehrt. Alle betroffenen Webhooks wurden erfolgreich geborgen und geliefert. Vielen Dank für Ihre Geduld, während wir daran gearbeitet haben, dieses Problem anzugehen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 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 um 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 um 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 um 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 um 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 um 19:53 UTCmonitoring

   Wir haben heute einen starken anstieg der benachrichtigungen von microsoft graph beobachtet, und dies hat sich auf unsere infrastruktur ausgewirkt, was zu höheren latenzen für neue und aktualisierte nachrichten für alle zuschüsse bei allen anbietern führt. Wir haben Änderungen an unserer Infrastruktur vorgenommen, um diesen erhöhten Benachrichtigungsverkehr besser zu bewältigen, und wir sehen, dass sich die Latenzen verringert haben. Wir überwachen weiterhin diesen ungewöhnlich hohen Benachrichtigungsverkehr und untersuchen die Quelle dieses höheren Benachrichtigungsverkehrs.

2. 11. August 2026 um 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 um 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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. August 2026 um 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 um 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 um 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 um 21:25 UTCresolved

   Der Webhook-Verkehr ist wieder normal und alle Systeme funktionieren korrekt. Aufgrund der seit dem Problem verstrichenen Zeitspanne können wir keine zusätzlichen Anfragen mehr zur Wiederholung der Webhooks akzeptieren. Bitte wenden Sie sich an den Nylas Support, um Hilfe beim Abrufen von Artikeln zu erhalten, die in dieser Zeit möglicherweise noch fehlen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 16:59 UTCmonitoring

   Wir haben ein Problem identifiziert, das die Bereitstellung eines kleinen Prozentsatzes von Nachrichten-Webhooks für einige Nylas-Anwendungen in der EU-Region beeinflusst hat. Das Problem trat hauptsächlich zwischen 06:00 und 11:00 UTC am 24. Juli 2026 auf. Die Webhook-Lieferung hat sich erholt und neue Webhooks werden erfolgreich verschickt. Nylas-Anwendungen in der US-Region waren nicht betroffen. Kunden, die möchten, dass wir Webhooks wiederholen, sollten sich so schnell wie möglich an [email protected] wenden und ihre Nylas-Anwendungs-IDs angeben, wenn diese verfügbar sind. Bitte beachten Sie, dass wir nicht nur die Webhooks wiederholen können, die nicht erfolgreich geliefert wurden. Eine Wiederholung sendet alle Nachrichten-Webhooks vom Beginn des Vorfalls bis zum Zeitpunkt der Wiederholung und erzeugt Duplikate. Bevor Kunden eine Wiederholung anfordern, sollten sie sicherstellen, dass ihre Systeme doppelte Webhook-Ereignisse sicher identifizieren und handhaben können. Wir untersuchen weiterhin die zugrunde liegende Ursache und überwachen die Webhook-Lieferung genau.

2. 24. Juli 2026 um 21:30 UTCresolved

   Der Webhook-Verkehr funktioniert weiterhin normal und alle Systeme funktionieren korrekt. Aufgrund der seit dem Problem verstrichenen Zeit sind wir nicht mehr in der Lage, zusätzliche Anfragen zur Wiederholung der Webhooks anzunehmen. Bitte wenden Sie sich an den Nylas Support, um Hilfe beim Abrufen von Artikeln zu erhalten, die in diesem Zeitraum möglicherweise noch fehlen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juli 2026 um 14:32 UTCinvestigating

   Wir untersuchen derzeit degradierte Teilnahmeraten für Notetaker bei Zoom-Meetings (andere Meeting-Anbieter sind nicht betroffen). Wir werden Updates teilen, da wir mehr Informationen haben.

2. 17. Juli 2026 um 17:21 UTCinvestigating

   Wir arbeiten weiterhin mit unseren Dienstleistern und internen Engineering-Teams zusammen, um das Problem zu untersuchen und mögliche Minderungsmaßnahmen zu bewerten. Wir werden zusätzliche Updates bereitstellen, wenn unsere Untersuchung fortschreitet.

3. 17. Juli 2026 um 20:32 UTCinvestigating

   Unsere Ingenieurteams untersuchen das Problem weiterhin aktiv und verfolgen parallel mehrere Sanierungspfade. Die bisher umgesetzten Maßnahmen haben nicht zu einer nachhaltigen Verbesserung geführt, und wir konzentrieren uns weiterhin auf die Ermittlung einer wirksamen Abschwächung. Wir werden ein weiteres Update bereitstellen, sobald wir bedeutende Fortschritte zu teilen haben.

4. 23. Juli 2026 um 16:09 UTCmonitoring

   Gemindert - Wir haben Änderungen eingeführt, die die Erfolgsquoten von Meeting Join wesentlich verbessert haben. Wir überwachen die Leistung weiterhin genau und erweitern schrittweise die Abschwächung und bewerten zusätzliche Verbesserungen. Wir werden ein weiteres Update zur Verfügung stellen, wenn diese Arbeit fortschreitet.

5. 23. Juli 2026 um 20:54 UTCresolved

   Die eingeführten Änderungen haben die Leistung der Notetaker-Meetings für Zoom auf ein normales Betriebsniveau wiederhergestellt, und unsere Überwachung bestätigt, dass das Problem die Kunden nicht mehr betrifft. Wir werden die Leistung weiterhin überwachen und im Rahmen unseres normalen Betriebs weitere Verbesserungen verfolgen. Dieser Vorfall ist nun gelöst. Vielen Dank für Ihre Geduld, während wir daran gearbeitet haben, dieses Problem anzugehen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. Juli 2026 um 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 um 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 um 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 um 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 um 13:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 3. Juli 2026 um 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 um 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 um 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 um 17:36 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 25. Juni 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 12:57 UTCresolved

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

1. 6. Mai 2026 um 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 um 16:39 UTCresolved

   We have updated our systems and webhooks have returned to normal

1. 4. Mai 2026 um 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 um 15:25 UTCresolved

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

1. 30. April 2026 um 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 um 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 um 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 um 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 um 17:30 UTCresolved

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

1. 14. April 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 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.