This article explains how Quickbase makes updates to the product and communicates changes.
In this article
Note: All times mentioned in this article are in Eastern US Time.
Updates
Quickbase performs regular updates to introduce new functionality and fix defects. Updates are made during a planned monthly release or on a periodic basis, and do not require downtime.
Monthly releases
Monthly releases include new features, enhancements, and bug fixes, and follow a consistent schedule:
- Updates are pushed Sunday mornings between 9:30 AM and 11:30 AM for all regions except for EU.
- Updates for EU regions are pushed 1 day after the release date. Learn more about Quickbase hosting.
- Updates to pipelines are typically pushed 2 days after the release date.
Quickbase monthly releases are planned to follow this schedule in 2025 (subject to change):
- January 12, 2025
- February 9, 2025
- March 16, 2025
- April 13, 2025
- May 18, 2025
- June 22, 2025
- July 20, 2025
- August 17, 2025
- September 14, 2025
- October 12, 2025
- November 16, 2025
- December 14, 2025
Stay informed on monthly releases by subscribing to our release notes, which are published the Tuesday prior to the release date.
We also announce these update windows on our service page 4-5 calendar days prior to the actual release date. We trigger notice to subscribers of the service page 2 calendar days prior and 1 hour prior to the release date.
Planned periodic updates
There are generally two types of periodic updates that do not occur during scheduled monthly releases:
- Patches for non-customer facing defects, product upgrades, very minor functionality changes, or functionality changes that are behind a “feature switch” and won’t become visible to customers until a later date. This type of update is typically done during US business hours. When possible, we proactively communicate details of these updates in our release notes. Otherwise, the information is included retroactively in the next month's release notes.
- Patches for high priority customer facing defects. This type of update is typically done between 11:00 PM and 12:00 AM on the day on which the patch is ready for release and is typically announced on our service page with 1-6 hours of notice. We trigger notice to subscribers of the service page if the defect is impacting a significant percentage of customers, typically classified as more than 20%.
Maintenance
Maintenance is performed on a planned basis to ensure systems are up to date, and on an unplanned basis to respond to incidents or other issues.
Planned maintenance
About 4-6 times a year, Quickbase plans downtime to perform maintenance such as updating the infrastructure and switching data centers. These updates are done on Saturday mornings between 12:10 AM and 2:00 AM, but are typically finished earlier.
These maintenance windows almost always involve downtime for the platform. Downtime windows are always determined by the lowest points of volume. We strive to announce these maintenance windows on our service page 10 calendar days prior to the actual maintenance window. We trigger notice to subscribers of the service page for this type of maintenance 2 calendar days prior and 1 hour prior to the maintenance.
Unplanned downtime
Unplanned downtime or unplanned degradation in functionality or performance is announced on our service page as the incident happens. We trigger a notice to subscribers of the service page if the incident is impacting a significant percentage of customers, typically classified as more than 20%.
Emergency maintenance
Emergency maintenance is performed as necessary to address issues outside of our control. These updates are done whenever needed to protect the stability and security of the platform, but we make every effort to execute them during periods of lower platform usage. Emergency maintenance may or may not require downtime, depending on the incident.
- We announce these maintenance windows on our service page as soon as possible. This could range from several days of notice to just a few minutes of notice. We always trigger a notice to subscribers of the service page for downtime emergency maintenance.
- We will sometimes trigger a notice for non-downtime emergency maintenance if we believe there is substantial risk of some customer facing impact, e.g., customers seeing brief instances of errors or performance being degraded.
Note: For customer facing defects or incidents, or for upcoming maintenance activity that only impacts one or a small number of customers, we typically rely on direct communication to the impacted customers, either via cases those customers have opened with Technical Support, or through a direct e-mail and/or phone call to the applicable customer contacts (e.g., account admin, realm admin, app admin).
Service page
Quickbase uses a service page to communicate current and future updates, maintenance activity, and incidents impacting the platform: https://service.quickbase.com.
We encourage all customers to use the service page as the first place they look to learn about upcoming maintenance or if they suspect an incident is occurring on the platform.
Customers can subscribe on the service page to receive notifications through e-mail or text whenever Quickbase posts an announcement on the service page that triggers a notification to subscribers.
Note: Out of respect for our customers’ time, we don't always trigger a notification to subscribers for minor issues or maintenance not causing down time.
To subscribe to receive notifications, follow the instructions in Subscribing to the Service Page.
How uptime is calculated on the service page
By default, the service page displays the total uptime for the last 90 days. This is calculated based on the total amount of time the Quickbase platform is available, excluding incidents outside of our control.
In other words, for unplanned downtime, we consider the source of the downtime when calculating our platform's availability. If the source of the downtime is within our control, the incident is included in our availability calculation. If it is not within the control of Quickbase or one of our subprocessors or subcontractors, we do not include the incident in our availability calculation. This follows common practice for Internet sites that track their availability.
It can sometimes take a week or more to determine the root cause of an incident. Until the root cause is known, we exclude a downtime incident from the availability calculation. If we ultimately conclude the root cause was within the control of Quickbase or one of our subprocessors or subcontractors, we update the incident and any downtime will immediately be reflected in the uptime calculation.
You can view the uptime history for time intervals during the current and previous year on using the Uptime feature on the service page. Uptime history can be viewed for: This Week, This Month, This Year, Last Week, Last Month, Last Year, or a custom date range.