Is Plain down?

Status: Investigating We are investigating an issue where some thread events are being processed late. Affected threads may not update as expected, for example a thread may not be assigned or reopened, or an SLA timer may not stop when a reply is sent. Messages are still being received. We are working to identify the cause and will share an update as soon as we have more information.

Status: Investigating We're continuing to investigate delayed processing of some thread events. Affected threads may not update as expected. For example, a thread may not be assigned or reopened, an SLA timer may not stop when a reply is sent, or a snoozed thread may not move back to needing a response when a customer replies. Messages are still being received. We've found the part of our system that's blocked and are carefully working on a recovery, so that catching up doesn't trigger a burst of delayed actions. We'll share another update as soon as we have more information. Affected components app.plain.com (Partial outage) Webhooks (Partial outage)

Status: Identified We've identified the cause. A single malformed record was blocking one of the queues we use to process thread events, which affects a small share of thread events (around 2%) across workspaces. Messages are still being received as normal. We're preparing to clear the backlog shortly, and when we do you may see a short burst of catch-up activity. We'll post another update once the backlog has been processed. Affected components app.plain.com (Degraded performance) Webhooks (Degraded performance)

Status: Monitoring We've deployed a fix, and delayed thread events are now being processed. Affected threads are catching up, so you may still see some catch-up activity for a short while. Messages were received as normal throughout. We're monitoring closely and will post another update once everything has fully caught up. Affected components app.plain.com (Degraded performance) Webhooks (Degraded performance)

Status: Resolved This issue is resolved. From 08:09 UTC on 13 October, a single malformed record blocked one of the queues we use to process thread events, which delayed a small share of thread updates across workspaces. Messages were received as normal throughout. We've deployed a fix and processed the delayed events, and everything is back to normal. If a thread still looks out of place, please get in touch and we'll take a look. Affected components app.plain.com (Operational) Webhooks (Operational)

Status: Investigating Since 13:50 UTC, some Slack, Discord and Microsoft Teams messages have been late or missing in Plain. New messages are coming through again, and we're replaying the ones that were missed. Sidekick could have experienced some outages as well. Signing in, the Plain web app, email and the rest of the product aren't affected. We'll post another update once all missed messages have been delivered. Affected components Microsoft Teams (Degraded performance) Slack (Degraded performance)

Status: Resolved This issue is resolved. Starting at 13:50 UTC, some Slack, Discord and Microsoft Teams messages were delayed or missing in Plain. Every affected message has now been delivered, and new messages are arriving normally. Email, the Plain web app and the rest of the product weren't affected. You don't need to do anything. Affected components Slack (Operational) Microsoft Teams (Operational)

Status: Investigating Since 15:41 UTC, listing threads through the Plain MCP server fails with an error. The Plain app and API are working normally. We've identified the cause and are deploying a fix. We'll update this page once it's live. Affected components MCP (Degraded performance)

Status: Identified We've found the cause and are rolling out a fix. Listing threads via the Plain MCP server will keep failing until it's live. The Plain app and API aren't affected. Affected components MCP (Partial outage)

Status: Monitoring We've deployed a fix, and listing threads via the Plain MCP server is working again. We're monitoring to make sure it stays that way. Affected components MCP (Operational)

Status: Resolved Listing threads via the Plain MCP server is working again. Between 15:41 and 16:45 UTC, these requests failed. The Plain app and API weren't affected. If your AI client still shows errors, start a new session and try again. Affected components MCP (Operational)

Status: Investigating We're investigating an issue that may prevent some customers from accessing or using Plain. We'll share more as soon as we know what's going on. Affected components app.plain.com (Full outage)

Status: Resolved This issue is resolved. It only affected the Plain web app frontend (signing in and using the app in the browser). Channel ingestion and the rest of the product kept working throughout. If the app still looks broken, refresh and try again. Affected components app.plain.com (Operational)

Status: Investigating We're investigating a problem that can stop people from enabling Authorize replies or connecting Microsoft Teams. If you hit an error while authorizing Teams, our team is looking into it now. We'll post another update here as soon as we know more.

Status: Identified We've identified the issue affecting Microsoft Teams Authorize replies and new connections. A fix is being deployed now. We'll update this page once the change is live and we've confirmed connections work again.

Status: Monitoring The fix is deployed. We're verifying that Microsoft Teams Authorize replies and new connections work as expected, and we'll update this page once we've confirmed everything is back to normal. Affected components Microsoft Teams (Degraded performance)

Status: Resolved The fix for Microsoft Teams Authorize replies and Teams message failures is deployed and verified. New connections and replies should be working normally again. If you still see issues, contact us and we'll help right away. Affected components Microsoft Teams (Operational)