[Quickbase US Status] Notice: Service Functionality Degraded (Unplanned) - No Down Time
[Quickbase US Status] Notice: Service Functionality Degraded (Unplanned) - No Down Time
12/04/2025, 05:00pm EST
12/04/2025, 05:00pm EST
Starting on Thursday, December 4, at about 5:00 PM Eastern US Time, Quickbase has received various reports from customers of intermittent issues when making API requests to the Quickbase platform. We are actively investigating this issue. This service page posting was created at 4:10 PM Eastern US Time on Friday, December 5.
We will provide an update by 8:00 PM Eastern US Time on Friday, December 5.
12/05/2025, 06:00pm EST
12/05/2025, 06:00pm EST
We have reproduced the issue and it appears to be related to clients using the header named "transfer-encoding: chunked". The problem is likely isolated to the following situations:
- API requests from a server-side utility (not a browser)
- API requests using the Quickbase XML API (not the JSON RESTful API)
- API requests with large payloads (or those including files)
The "transfer-encoding: chunked" header is commonly used in applications with Node.js using the HTTPS library.
We've confirmed that Quickbase has not changed any software or infrastructure that is directly within our control, that may have led to this issue. We've also confirmed that we received no notice of any related changes from any of our service providers with infrastructure that sits in front of the Quickbase platform. We are now contacting those service providers to report our findings and ask them if they've made any undocumented changes that may have altered how the "transfer-encoding: chunked" header is being handled. We will evaluate any responses they provide that may help resolve this issue.
We will update this post when we have additional information from our service providers.
12/05/2025, 09:21pm EST
12/05/2025, 09:21pm EST
As of 9:21 PM Eastern US Time, the issue is resolved. One of our service providers made a configuration change on December 4 at 5:52 PM Eastern US Time. We do not yet know the reason they made that configuration change but they are a major service provider and regularly make changes to their infrastructure that they do not communicate. That is common practice for every SaaS provider, including Quickbase. In any event, once we were able to reproduce the issue, and determine what was happening, and rule out all infrastructure and software that Quickbase controls, we were able to give our service providers the necessary technical information for them to research if they had made a change that negatively impacted Quickbase. One of the providers replied that they suspected one of their changes may have caused the problem for Quickbase, and they reverted that change at 9:20 PM Eastern US Time. Within one minute, we confirmed, via our logs, that the errors had stopped.
We will provide more information on the root cause of this issue, once our service provider responds with more details.
This incident is closed.
12/05/2025, 10:30pm EST
12/05/2025, 10:30pm EST
The preliminary root cause is that one of our service providers, Cloudflare, deployed a software change on December 4, that changed the structure of specific types of API requests for the Quickbase platform (listed above in this incident). Once we were able to isoldate and reproduce the problem, and reported it to Cloudflare, they rolled back the software change they had made which immediately fixed our problem. Their initial response is that there is a software defect in that deployment. Their engineering team will investigate and they've committed to providing us with more information on the root cause by mid-late next week.