Courier Status
Real-time updates of Courier issues and outages
Courier status is Operational
Active Incidents
No active incidents
Recently Resolved Incidents
No recent incidents
Courier Outage Survival Guide
Courier Components
Courier
Web Application
API
Automations
Observability
Courier Hosting Infrastructure
AWS dynamodb-us-east-1
AWS elasticsearch-us-east-1
AWS kinesis-us-east-1
AWS lambda-us-east-1
AWS sqs-us-east-1
Integrations: Outbound from Courier
Mailgun API
Mailgun Outbound Delivery
Mailjet REST API
Mailjet SEND API
Nexmo Outbound SMS
Plivo SMS API
Segment Data Ingestion (Tracking) API
Segment Cloud Sources
SendGrid API
SendGrid SMTP
Slack Apps/Integrations/APIs
SparkPost SMTP API - USA
SparkPost SMTP API - EUROPE
SparkPost SMTP Delivery - USA
SparkPost SMTP Delivery - EUROPE
Twilio AUTOPILOT
Twilio SMS
Integrations: Inbound to Courier
Segment Destinations
Courier Alternatives
Outlook.com
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.
More information: https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-unable-to-connect-to-outlook-com-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef
