Quick Base incident

[Quickbase Status] Notice: Service Functionality Degraded (Unplanned)

Major Resolved View vendor source →

Quick Base experienced a major incident on July 10, 2026 affecting Quickbase Service - US Region and Quickbase Service - US Region and 1 more component, lasting 1h 40m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 04:17 PM UTC
Resolved
Jul 10, 2026, 05:57 PM UTC
Duration
1h 40m
Detected by Pingoru
Jul 10, 2026, 04:17 PM UTC

Affected components

Quickbase Service - US RegionQuickbase Service - US RegionQuickbase Automations - US RegionQuickbase Billing - US RegionQuickbase Fastfield - US RegionQuickbase Fastfield - US RegionQuickbase Automations - US RegionQuickbase Billing - US RegionQuickbase Service - US RegionQuickbase Audit Logs - US Region

Update timeline

  1. investigating Jul 10, 2026, 04:17 PM UTC

    Starting at 12:17 PM Eastern US Time, we have identified an issue affecting the loading of Forms and Dashboards in both the Quickbase US and Quickbase EU platforms. The Quickbase team is actively investigating the root cause and is working to restore normal functionality as quickly as possible. We will provide additional updates as more information becomes available.

  2. resolved Jul 10, 2026, 05:11 PM UTC

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

  3. resolved Jul 10, 2026, 05:57 PM UTC

    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.