02/02/2025, 06:10am EST

First, we realize we are an important part of your business, and you expect Quickbase to be available and performing well when you need it.  We apologize for the disruptions that have occurred over this past week.  We have not met the standard you expect of us, or that we expect of ourselves.

We have been working relentlessly over the past week to ensure that the new version of the Quickbase Load Balancer, or QLB, meets the standard of reliability and performance you expect from the Quickbase platform.  We are continuing our pursuit of that standard in the best interests of all users of the platform.  Please read on regarding details of an upcoming maintenance window.

The Quickbase team will be performing emergency maintenance on Sunday, February 2, between 6:10 AM and 8:00 AM Eastern US Time to upgrade several component services of the Quickbase load balancer supporting the Quickbase US platform.  The Quickbase Load Balancer, or QLB, is responsible for routing all requests made to the platform to the appropriate computers for processing.

This emergency maintenance is related to the two unplanned down time events that occurred this past week as follows:

• Monday, January 27, 5:45 AM to 7:05 AM Eastern US Time (80 Minutes)
• Thursday, January 30, 7:13 PM to 7:35 PM Eastern US Time (22 Minutes)

Just prior to the unplanned down time event on Thursday night, we upgraded one of the component services of QLB in order to successfully resolve a problem that had impacted about 1% of requests to the platform whereby customers were either getting slow response times or errors, specifically caused by QLB.

The emergency maintenance planned for Sunday is to correct the defect that caused the unplanned down time on Thursday.  It must be done with urgency or we risk having another unplanned down time event.  We are using our Sunday morning maintenance window because it is one of the times when the platform is used the least, and will least conflict with overnight processing done by many customers.

Although the down time duration specified in this post is 1 hour, 50 minutes, we will make every effort to complete it in much less time.

There is a possibility that the maintenance can be executed without down time.  If you attempt to use the platform during this maintenance, and you see the maintenance page we typically post during down time maintenance, you should expect the down time to last until at least 7:00 AM Eastern US Time.

However, if you are able to use the platform, i.e., you do not see the maintenance page, the only impact you may experience will be a 5 minute period where 4 specific actions will either result in an error or the actions will be slower than normal.  We cannot predict the exact point within the maintenance window when the 5 minutes of degraded functionality will occur.  If you encounter issues with any of these 4 actions during the maintenance window, please wait at least 5 minutes and try again.

• Accessing an application, or a table within the application, that is NOT already loaded prior to the 5 minute period.
• Cloning an application.
• Copying a table within an application.
• Importing records into an application that has a relationship with another application.

We will trigger an e-mail or text to all Quickbase US subscribers of the Quickbase service page when we complete the maintenance so that you will know when it is safe to use the platform.

Once again, we apologize for any disruption this maintenance may cause you and we appreciate your patience and understanding as we work hard to stabilize QLB.

02/02/2025, 06:25am EST

As of 6:26 AM Eastern US Time, the Quickbase US platform is available. We are continuing with the maintenance and we do not expect any further disruption to the Quickbase platform as we make these improvements.

02/02/2025, 07:15am EST

As of 7:08 AM Eastern US Time, the maintenance is complete and executed without down time. 

The only impact you may have experienced was a period from 6:13 AM to 6:18 AM where 4 specific actions might have been slower than normal. 

• Cloning an application.
• Copying a table within an application.
• Importing records into an application that has a relationship with another application.  
• Accessing an application, or a table within the application, that was NOT already loaded prior to 6:13 AM.