Plain Outage History

Started Aug 19, 2026, 02:47 PM UTC· resolved Aug 19, 2026, 03:13 PM UTC

1. identified Aug 19, 2026, 02:47 PM UTC

   Notifications for multiple workspaces are delayed. We are investigating this.

2. resolved Aug 19, 2026, 03:13 PM UTC

   Notifications are fully operational again. We had a big backlog on notifications which have since resolved. We will continue monitoring the health of Slack Notifications.

Read the full incident report →

Started Aug 18, 2026, 12:10 AM UTC· resolved Aug 18, 2026, 02:40 AM UTC

1. investigating Aug 18, 2026, 12:10 AM UTC

   We are currently investigating reports of delays to webhook delivery.

2. resolved Aug 18, 2026, 02:40 AM UTC

   Webhook delivery has returned to normal.

Read the full incident report →

Started Aug 17, 2026, 02:50 PM UTC· resolved Aug 17, 2026, 04:34 PM UTC

1. identified Aug 17, 2026, 02:50 PM UTC

   We are investigating an issue causing search to be unavailable in the support app. A fix has been identified and is ready to deploy.

2. monitoring Aug 17, 2026, 03:32 PM UTC

   Search in the Plain web app is working normally again. The issue causing a full page reload when typing in search has been fixed and deployed. We are monitoring its behavior. Sorry for the disruption.

3. resolved Aug 17, 2026, 04:34 PM UTC

   A fix has been merged for the issue which caused a full page refresh on search

Read the full incident report →

Started Aug 04, 2026, 03:58 PM UTC· resolved Aug 04, 2026, 04:22 PM UTC

1. investigating Aug 04, 2026, 03:58 PM UTC

   We are investigating an issue affecting the reporting features in Plain. Some users may have seen stale or delayed data in their Insights dashboards, particularly around 15:14 UTC today.

2. identified Aug 04, 2026, 03:58 PM UTC

   We have identified the source of the issue and are working with our data infrastructure provider to investigate. We will post an update once we have more information.

3. resolved Aug 04, 2026, 04:22 PM UTC

   We have resolved the issue. All data in reporting is now up to date.

Read the full incident report →

Started Jul 30, 2026, 10:01 AM UTC· resolved Jul 30, 2026, 11:43 AM UTC

1. investigating Jul 30, 2026, 10:01 AM UTC

   We're currently investigating an issue affecting Reporting in Plain. Reporting data may appear stale or incomplete for activity after approximately 06:17 UTC this morning. All other Plain features are working normally, including thread management, messaging, and integrations. Our team has identified the source of the issue and is actively working to resolve it. We'll share an update as soon as data has been restored to normal. Sorry for the disruption.

2. identified Jul 30, 2026, 10:26 AM UTC

   We've identified the cause of the reporting delay. It's related to a third-party service we use for data processing, and we're in contact with their team now. Reporting data may still show stale figures for activity after 06:17 UTC this morning. Everything else in Plain is working normally. We'll post another update once we have a fix or a clearer timeline.

3. monitoring Jul 30, 2026, 11:15 AM UTC

   A fix is being applied for the reporting delay we flagged earlier today. We're keeping an eye on things to confirm data is processing normally again. If you're still seeing stale figures for activity after 06:17 UTC this morning, that should clear up shortly. We'll post a final update once everything is back to normal.

4. resolved Jul 30, 2026, 11:43 AM UTC

   Reporting is back to normal. The issue affecting data processing has been fixed and we've confirmed reports are up to date again. Sorry for the disruption today.

Read the full incident report →

Started Jul 28, 2026, 03:23 PM UTC· resolved Jul 28, 2026, 03:56 PM UTC

1. investigating Jul 28, 2026, 03:23 PM UTC

   We are investigating an issue affecting Sidekick's ability to search and query codebases (GitHub repositories). Sidekick responses that rely on code lookups may be incomplete or return errors.

2. identified Jul 28, 2026, 03:25 PM UTC

   We have identified the root cause (a misprovisionment of the Sidekick agent environment) and a fix is currently being deployed. We will post an update once service is restored.

3. identified Jul 28, 2026, 03:48 PM UTC

   We have identified the root cause and a corrected build is now being deployed to production. Sidekick's codebase query functionality should be restored shortly. We will confirm once the deployment is complete.

4. resolved Jul 28, 2026, 03:56 PM UTC

   Sidekick's GitHub/codebase query functionality has been fully restored. We rebuilt and redeployed the affected agent environment using the correct provisioning process. All codebase queries are working normally across all workspaces. We apologize for the disruption.

Read the full incident report →

Started Jul 28, 2026, 10:04 AM UTC· resolved Jul 28, 2026, 10:34 AM UTC

1. identified Jul 28, 2026, 10:04 AM UTC

   Workflows that include steps that interact with Sidekick are currently not running. We have identified the issue and are working on a fix.

2. identified Jul 28, 2026, 10:07 AM UTC

   Sidekick conversations generally are unaffected, only workflow steps that run a Sidekick conversation in the background are impacted.

3. monitoring Jul 28, 2026, 10:24 AM UTC

   The fix has been deployed and we are monitoring the situation.

4. resolved Jul 28, 2026, 10:34 AM UTC

   The fix has been confirmed working, sidekick discussions in workflows should be running as expected again. Please don't hesitate to reach out to us if you are still experiencing any unexpected behavior.

Read the full incident report →

Started Jul 24, 2026, 08:50 AM UTC· resolved Jul 24, 2026, 09:08 AM UTC

1. identified Jul 24, 2026, 08:50 AM UTC

   A recent deployment shipped a new schema for a data model which is backwards incompatible. The deployment is currently being rolled back.

2. resolved Jul 24, 2026, 09:08 AM UTC

   The deployment has been rolled back. Impact of this change was limited to workspaces using CRM sync.

Read the full incident report →