Monitoring - Microsoft has disabled Basic (Non-OAuth) authentication for Exchange Online mailboxes using Free or Family licenses - also known as Personal Accounts. These include free email addresses using the domains outlook.com, hotmail.com, live.com, msn.com, and others.
Microsoft only allows these mailboxes to use Exchange Web Services and Exchange ActiveSync using Basic authentication, so these mailboxes are no longer able to utilize those services. Our API v2 uses both of those services to communicate with all Microsoft mailboxes.
Microsoft has provided no work-around for continuing to use those services, so these mailboxes can no longer use our API v2 and must start using our API v3. We use Microsoft Graph API for our API v3 and that is not affected.
This does NOT affect paid mailboxes using Microsoft's Business or School licenses. This also does NOT affect on-premise Exchange mailboxes. Only free mailboxes using Microsoft's Free or Family licenses are affected.
Oct 01, 2024 - 13:09 PDT
We will be performing a scheduled upgrade of our AWS RDS (Relational Database Service) instances to the latest version. This upgrade is essential to maintain optimal performance, enhance security, and provide access to the latest features.
While the upgrade will be conducted as a rolling update to minimize disruption, you may experience elevated error rates for periods lasting up to 15 minutes. We apologize for any inconvenience this may cause and appreciate your patience.
Our team will be closely monitoring the process to ensure a smooth transition. If you have any questions or concerns, please do not hesitate to contact our support team (support@nylas.com). Posted on
Oct 17, 2024 - 16:50 PDT
Resolved -
We have confirmed that the elevated error rates have returned to normal levels, but will continue to monitor closely. You may experience some delays in webhooks while we work through the backlog of messages to process. We traced the issue to a Nylas subprocessor, and have requested an RCA from them. We will post the Postmortem for this incident here once we complete the process.
Oct 8, 09:06 PDT
Monitoring -
We have addressed the issue and are now monitoring. API v2 is operating normally now.
Oct 8, 08:10 PDT
Investigating -
We are investigating issues with our API v2 returning errors.
Oct 8, 07:42 PDT