[Quickbase Status] Notice: Service Functionality Degraded (Unplanned) - No Down Time

Update timeline

1. investigating Apr 23, 2026, 08:00 AM UTC

   Starting around 4:00 AM Eastern US Time, a subset of Pipelines are failing with the following errors, though similar variations of these messages may also be observed: "Pipeline execution failed." "Internal error. Abort execution." These errors are causing certain Pipelines to fail and are impacting successful completion of scheduled and on-demand executions. Users may notice increased error rates in logs and failed Pipeline runs until this issue is resolved. We are actively investigating the cause. We will continue to monitor this incident and will provide an update as soon as we have one.

2. investigating Apr 24, 2026, 11:44 AM UTC

   At 7:44 AM Eastern US Time, we deployed a fix for this issue. We are continuing to monitor this issue and will provide another update as soon as we have one.

3. investigating Apr 24, 2026, 12:43 PM UTC

   As of 8:43 AM Eastern US Time, we are seeing improvements in our logs from our last update. We are still actively investigating this issue and will provide another update as soon as we have one.

4. investigating Apr 24, 2026, 01:43 PM UTC

   As of 9:43 AM Eastern US Time, we continue to actively work on the issue and are still investigating the root cause. We will provide another update as soon as more information becomes available.

5. investigating Apr 24, 2026, 02:43 PM UTC

   As of 10:43 AM Eastern US Time, we remain actively engaged in resolving the issue and continue to investigate the root cause. We will provide the next update as soon as we have more details to share.

6. investigating Apr 24, 2026, 03:43 PM UTC

   As of 11:43 AM Eastern US Time, we are still working to resolve the issue and continue investigating the root cause. We will share an update as soon as more information becomes available.

7. investigating Apr 24, 2026, 04:55 PM UTC

   The incident is largely resolved, and the majority of executions are now operating as expected. We are still investigating a small number of related, lower-frequency issues and continue to work toward full resolution. As impact has significantly decreased, updates to this post will be less frequent. We will continue to share meaningful progress as it becomes available.

8. investigating Apr 24, 2026, 08:57 PM UTC

   The incident remains largely resolved, with most functionality operating as expected. We are continuing to review any subset of related failures, and our team will continue to investigate and monitor closely. We will provide meaningful updates if and when new information becomes available.

9. investigating Apr 27, 2026, 02:07 PM UTC

   The incident remains largely resolved, with most functionality operating as expected. We continue to review a subset of related failures and are working closely with our hosting provider to identify and fully resolve the issue. Our team will continue to monitor closely as we work toward full resolution. We will provide meaningful updates if and when new information becomes available.

10. investigating Apr 27, 2026, 09:08 PM UTC

    We are continuing to investigate a small subset of intermittent failures that persist under some conditions. Our team is actively working with our hosting provider to validate the underlying cause and confirm a permanent resolution. At this stage, we continue to monitor closely and will share updates as new substantive information becomes available. Our next update is planned for Tuesday 4/27/26 at 10:00 AM ET

11. investigating Apr 28, 2026, 02:00 PM UTC

    System performance is stable and the majority of functionality is operating as expected. We are continuing to assess a subset of related failures and are actively collaborating with our hosting provider to drive toward full resolution. Our team remains engaged and is monitoring the situation closely. We will share additional updates as meaningful information becomes available.

12. investigating Apr 29, 2026, 12:49 PM UTC

    We have identified a mitigation for the issue and began deploying it on April 28. As part of validation, this update was applied to a small set of Pipelines that had experienced some of the highest failure rates during the incident. These Pipelines have since run successfully without errors, including through scheduled overnight executions. Based on these results, we completed a controlled rollout of this change across all customers while continuing to actively monitor system performance. We will continue to share updates as we progress toward a final resolution.

13. resolved Apr 29, 2026, 08:26 PM UTC

    This incident has been resolved. A mitigation was successfully deployed across all environments, and Pipeline executions are now operating normally. We have continued to monitor system performance following the rollout and are no longer observing elevated error rates related to this issue. We are completing a detailed review of execution data to identify impacted Pipelines and customers. Our team will conduct targeted follow-up with affected customers to provide additional context and support as needed. A separate root cause analysis will be published once our investigation is complete. Thank you for your patience while we worked to resolve this issue.