Quick Base Outage History

The Pave team has implemented a fix for the issue and as of 10:44 AM Eastern US Time, Pave is back online. Users may have been unable to access Pave apps between 10:12 and 10:44 AM Eastern US Time. The Pave team is actively investigating the root cause and will provide more information as it becomes available.

As of 7:12 AM Eastern US Time, the Quickbase US platform is operating normally. We are actively investigating the cause and will post a root cause once we have it. This incident is closed.

The preliminary root cause is a regional Internet outage in the Western Unites States, or a localized Internet outage in or around the hosting facility in which the Quickbase US platform is actively located. We are awaiting further updates from our hosting partner. As a reminder, in order to ensure the availability of the US instance of the Quickbase platform, Quickbase hosts the platform in two geographically diverse locations; Ohio (USA) and Oregon (USA). Quickbase US can run actively in only one location at a time with the other location running in standby mode. Since June 6, 2026, Quickbase US has been active in our Oregon location, which is in the Western United States. This outage was too shortlived to trigger a switch to our Ohio location. You can read more about how we ensure the availability of Quickbase US in our Trust Center.

The database maintenance is complete with no observed issues for Automations or Webhooks. The periods where errors occurred were less than 1 minute each. This incident is closed.

The issue affecting Forms and Dashboards was resolved as of 1:11 PM ET. The Quickbase US and Quickbase EU platforms are operating normally.

The preliminary root cause is that a vendor partner used by the Quickbase platform to manage feature settings had an incident that prevented some features (Forms and Dashboards) within the Quickbase platform from properly reading the proper settings that determine how a feature looks or acts. Quickbase platform features are typically able to manage the inability to read feature settings in real time by using the proper default values for the settings. In this incident, we did not have the proper default values. We are actively working to correct that. We will post a more detailed root cause once we complete our investigation into this issue and get further information from our vendor partner. We expect to post a final root cause by July 17.

Our hosting provider has deployed a fix for this issue and the Quickbase Community is working properly again. This incident is closed.

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.

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.

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.

Our hosting provider has deployed a fix for this issue and Quickbase University is working properly again. This incident is closed.

This issue was caused by an unexpected spike in traffic that impacted a vendor supporting the QB University platform. The spike triggered a failure in the vendor’s internal health checks, which temporarily affected login and access to parts of the platform. The vendor identified the issue and restored service shortly after. They have since implemented a fix to prevent this specific failure scenario from recurring. We are working with the vendor to ensure additional monitoring, scaling safeguards, and change management controls are in place to reduce the risk of similar disruptions in the future.

Quickbase Help is performing normally again. We will provide a root cause once it's available. This incident is closed.

This issue was caused by an unexpected increase in traffic that temporarily impacted the Quickbase Help site (help.quickbase.com). Our hosting provider quickly identified the issue and put protections in place to stabilize traffic. Performance returned to normal shortly after. Our hosting provider has created additional monitoring and safeguards to help prevent this kind of disruption in the future.