Authentication Disruption

Login is functional again for most users.

User login remains impacted. All other functionality is unaffected.

While we are fully recovered: if you are currently logged into Plain, do not manually refresh the page in order to avoid being impacted. You can keep using it. Opening new tabs with Plain or refreshing your current one will most likely fail.

We are still waiting for a resolution from our auth provider. We will update this page as soon as we know more. Until then, please remember:

• if you were already logged into Plain, you might still be able to use it normally
• all inbound message processing remains operational, no messages will be lost during the incident
• if you use email, you can temporarily add additional routing to your inbox to keep communicating with your customers
• for any messaging channel, if you have slack or email notifications enabled, you will still get them, allowing you to identify who is getting in touch

Slack, email, MS Teams, discord, chat and any other messaging channel remain fully operational. No messages will be lost.

If you have email configured as a channel in your Plain workspace and you use Google Workspace, check the instructions here: https://help.plain.com/article/email-receiving and check 'Also route to original destination' to get inbound support emails in your Gmail inbox.

• API usage with machine users remains live
• The support app is completely down
• MCP is unavailable

We're getting in touch with customers to find ways to mitigate this.

We are currently investigating an issue affecting login to Plain. Our authentication provider is experiencing a disruption that is preventing users from signing in.

Our team is actively investigating and monitoring the situation. We will post updates as we have more information.