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

Incident

07/10/2026, 01:57pm EDT

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

Status: closed

Start: 07/10/2026, 12:17pm EDT

End: 07/10/2026, 01:11pm EDT

Duration: 54 minutes

Affected Components:

Quickbase Service - US Region Quickbase Service - EU Region Quickbase Audit Logs - US Region Quickbase Audit Logs - EU Region Quickbase Automations - US Region Quickbase Billing - EU Region Quickbase Billing - US Region Quickbase Extensions - EU Region Quickbase Fastfield - EU Region Quickbase Extensions - US Region Quickbase Pipelines - EU Region Quickbase Fastfield - US Region Quickbase Pipelines - US Region Quickbase Platform Analytics - EU Region Quickbase RESTful APIs - EU Region Quickbase Platform Analytics - US Region Quickbase RESTful APIs - US Region Quickbase Sync - EU Region Quickbase Sync - US Region Quickbase Webhooks - EU Region Quickbase Webhooks - US Region

Update

07/10/2026, 12:17pm EDT

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.

Resolved

07/10/2026, 01:11pm EDT

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

Root Cause

07/10/2026, 01:57pm EDT

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 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.