Monitoring - Microsoft has re-opened a previous incident for an issue that is affecting third party connections to a small number of Outlook.com mailboxes and other free Microsoft email accounts (link to their status page is below).
This issue can cause Nylas accounts connected to these mailboxes to abruptly go invalid and require re-authentication to continue. Our system automatically retries the credentials before setting accounts Invalid, but Microsoft's servers are still incorrectly rejecting them at times. This has been occurring sporadically since late January.
Until Microsoft resolves this issue, our recommended work-around is to ensure that the users are authenticating these accounts with App Passwords and re-authenticate when the Nylas account goes Invalid.
Completed -
The scheduled maintenance has been completed.
Mar 15, 09:50 PDT
Scheduled -
This message serves as notification that we have added new Subprocessor(s) listed below to our systems. These subprocessors have been carefully selected and vetted to ensure they meet our high standards for data security and privacy.
Effective April 2024, we will be partnering with the following new subprocessor(s) to further enhance our services:
&Open Apollo Hubspot
You can find all of the details regarding what data is being processed by or passed through each subprocessor, as well as the applicable components, locations, and entities on our updated Nylas Subprocessor page on our website at https://www.nylas.com/security/subprocessors/
If you have any questions or concerns, please contact our Security Team at security@nylas.com.
Mar 15, 09:31 PDT
Completed -
The scheduled maintenance has been completed.
Mar 10, 01:30 PST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 10, 01:00 PST
Scheduled -
We will be conducting a rolling database schema update in the US and EU regions (March 10th, 13:00 PST/ 14:00 MST / 16:00 EST / 21:00 CEST), which may cause temporary elevated 503 responses and delays in webhooks.
Mar 4, 12:16 PST
Resolved -
This incident has been resolved.
Mar 5, 03:52 PST
Monitoring -
We have implemented measures to mitigate the issue and are now closely monitoring the results.
Mar 5, 03:38 PST
Update -
We are continuing to investigate this issue.
Mar 5, 03:22 PST
Investigating -
We are currently experiencing an increase of 500 errors affecting several endpoints. We are actively investigating the issue.
Mar 5, 02:49 PST