Saturday November 1, 2025

Summary

Between 1:00 AM PDT and 2:45 AM PDT on November 1, 2025, some users were unable to upload files or create/use canvases in Slack, often resulting in an error.

We traced this back to an unexpected spike in error rates for the files.upload API endpoint, caused by database timeouts stemming from an ongoing backend job.

We temporarily paused the job to reduce traffic to the affected database and implemented additional logic handling to properly balance volume. This allowed the database to recover and correctly serve requests, resolving the issue for all affected users.

9:13 AM PST

Resolved

At around 1:00 AM PDT on November 1, 2025, we observed an error related to file upload. Users experienced issues while uploading files. This problem was caused by an ongoing incident triggered by a migration job running on the database. The issue self-resolved, consequently fixing the file upload problem. The issue was resolved at 2:45 AM PDT.

We've adjusted this entry to properly reflect impact & resolution timestamps. We apologize for any confusion.

3:13 AM PST

Summary

Between 1:00 AM PDT and 2:36 AM PDT on November 1, 2025, some users experienced trouble uploading files, using Slack AI, performing searches, using Slack Connect, or sending and receiving messages.

We traced this back to an unexpected spike in error rates for a backend database responsible for handling several Slack functions. This spike was caused by timeouts stemming from an ongoing backend job, resulting in higher-than-expected traffic.

We took similar mitigation steps as the related incident we reported on (https://slack-status.com/2025-11/d447af6bb8944796): We temporarily paused the problematic jobs to reduce traffic to the affected database and implemented logic adjustments to handle this high traffic more efficiently. Once the database recovered, all affected functionality was restored to users.

10:12 AM PST

Resolved

At approximately 1:00 AM PDT on November 1, 2025, some users may have experienced issues with the Files endpoint, SlackAI, Search, Messaging, and Slack Connect functionality. The issue was caused by a database job that resulted in high CPU utilization on the database. Stopping this job reduced CPU usage to within threshold limits, which resolved the issue. The issue was resolved at 2:36 AM PDT.

We've adjusted this entry to properly reflect impact & resolution timestamps. We apologize for any confusion.

3:47 AM PST