Quick Base incident
[Quickbase Status] Notice: Service Functionality Degraded (Unplanned) - No Down Time
Quick Base experienced a major incident on May 14, 2026 affecting Quickbase Service - US Region and Quickbase Automations - US Region and 1 more component, lasting 12d 14h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 14, 2026, 03:49 AM UTC
Starting around 11:49 PM Eastern US Time, Pipelines are experiencing a state where they are delayed or fail to start. We are currently investigating the issue.
- resolved May 14, 2026, 07:55 AM UTC
The issue was identified and it has been resolved. The potentially impacted services were Pipelines Quickbase webhooks Automations Actions Emails We are still investigating further and will provide more information in the root cause analysis.
- resolved May 15, 2026, 05:24 PM UTC
Related Quickbase services remain operating normally. An issue introduced during a release interrupted the processing of certain workflow trigger events. As a result, some workflows triggered by changes in Quickbase tables may not have run as expected. This may have impacted: Pipelines Automations Actions Quickbase Webhooks The affected workflows were those triggered by table activity such as record creation, edits, or deletions. No scheduled workflows were impacted by this. Customers may not see errors or other indicators for workflows that did not run. We recommend reviewing critical activity during the impacted window and validating any downstream processes that should have been triggered by record changes. No action is required for workflows triggered outside the impacted timeframe. We are continuing to finalize impact analysis and will provide additional information to impacted customers as appropriate.
- resolved May 26, 2026, 05:50 PM UTC
An issue introduced during a production release modified a critical configuration setting responsible for sending table-triggered workflow events into Quickbase’s internal queueing system. With that setting absent, the system defaulted to not queueing those events, causing some Pipelines, Webhooks, Automations, and Actions triggered by record changes to not run during the impacted window. Scheduled workflows were not impacted. The issue was resolved by restoring the configuration setting, but some events from the impacted period could not be replayed because they were never successfully queued.