Overview
In order to ensure the availability and security of the Quick base platform, we will be enabling the use of the Cloudflare DDOS Protection Service on Monday, March 19, 2018 at 8:00 PM Eastern US Time. DDOS stands for Distributed Denial of Service and a DDOS attack is when multiple systems flood the network bandwidth or resources of a targeted web site in an effort to take the web site offline. For more information about DDOS attacks, goto https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/.
Key Messages
1. There will be NO change in how Quickbase functions or performs and NO change in Quickbase's availability, disaster recovery, security, or compliance (https://www.quickbase.com/security-and-compliance).
2. There will be NO change in the outbound IP addresses used by Quickbase, i.e., no change in the IP addresses from which you would see Quickbase responding to your requests.
3. The overwhelming majority of Quickbase customers (99%) will not need to take any action as a result of our enabling the use of Cloudflare.
4. A small number of customers (1%) may be impacted by one or more of the following issues when Cloudflare is enabled:
4.1. The specific IP address that is resolved by your browser or API program when you access Quickbase will change but your company's name resolution (DNS) servers should automatically return a valid IP address for the Quickbase platform. In some cases, your browser or API program may continue to resolve to the original, non-Cloudflare IP addresses for the Quick Base platform. The original IP addresses will continue to be supported for several weeks following the enablement of Cloudflare. If your browser or API program is resolving to the original IP addresses, you should restart your browser or API program.
4.2. The Quick Base platform, when enabled to use Cloudflare, will resolve to one of the following 2 destination IP addresses. The specific destination IP address resolved to from the list below can change from session to session but all 2 destination IP addresses should always be available to handle Quick Base platform requests.
4.3. Although not a commonly used practice, customers and partners who use IP routing rules to control the network path that requests take to reach Quick Base, should note that the 2 new destination IP addresses listed above should be added to their existing rule base. Any existing destination IP addresses in the rule base for Quick Base should be left intact.
4.4. Although not a practice that Quick Base officially supports, customers and partners who allowlist the destination IP address ranges their browser or API programs can access, should note that the 2 new destination IP addresses listed above should be added to their existing allowlist. Any existing destination IP addresses in the allowlist for Quick Base should be left intact.
4.5. Although not a commonly used practice, customers and partners who override the default trusted certificate authorities, and/or only allow specific SSL certificates in their browsers or API programs, should note that the SSL certificate for the Quickbase platform will change as follows:
4.5.1. The Common Name (also known as "CN") associated with the SSL certificate presented by the Quickbase Platform will continue to be the following wildcard value:*.quickbase.com.
4.5.2. The Certificate Authority(CA) will change to "COMODO" from "Go Daddy".
4.5.3. For those looking for more details about the current SSL certificates, you can inspect the certificates presented by the following resources:
á SSL Certificate After Enabling Cloudflare: https://help.quickbase.com/user-assistance/
In order to ensure the availability and security of the Quick base platform, we will be enabling the use of the Cloudflare DDOS Protection Service on Monday, March 19, 2018 at 8:00 PM Eastern US Time. DDOS stands for Distributed Denial of Service and a DDOS attack is when multiple systems flood the network bandwidth or resources of a targeted web site in an effort to take the web site offline. For more information about DDOS attacks, goto https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/.
Key Messages
1. There will be NO change in how Quickbase functions or performs and NO change in Quickbase's availability, disaster recovery, security, or compliance (https://www.quickbase.com/security-and-compliance).
2. There will be NO change in the outbound IP addresses used by Quickbase, i.e., no change in the IP addresses from which you would see Quickbase responding to your requests.
3. The overwhelming majority of Quickbase customers (99%) will not need to take any action as a result of our enabling the use of Cloudflare.
4. A small number of customers (1%) may be impacted by one or more of the following issues when Cloudflare is enabled:
4.1. The specific IP address that is resolved by your browser or API program when you access Quickbase will change but your company's name resolution (DNS) servers should automatically return a valid IP address for the Quickbase platform. In some cases, your browser or API program may continue to resolve to the original, non-Cloudflare IP addresses for the Quick Base platform. The original IP addresses will continue to be supported for several weeks following the enablement of Cloudflare. If your browser or API program is resolving to the original IP addresses, you should restart your browser or API program.
4.2. The Quick Base platform, when enabled to use Cloudflare, will resolve to one of the following 2 destination IP addresses. The specific destination IP address resolved to from the list below can change from session to session but all 2 destination IP addresses should always be available to handle Quick Base platform requests.
- 104.18.100.30
- 104.18.101.30
4.3. Although not a commonly used practice, customers and partners who use IP routing rules to control the network path that requests take to reach Quick Base, should note that the 2 new destination IP addresses listed above should be added to their existing rule base. Any existing destination IP addresses in the rule base for Quick Base should be left intact.
4.4. Although not a practice that Quick Base officially supports, customers and partners who allowlist the destination IP address ranges their browser or API programs can access, should note that the 2 new destination IP addresses listed above should be added to their existing allowlist. Any existing destination IP addresses in the allowlist for Quick Base should be left intact.
4.5. Although not a commonly used practice, customers and partners who override the default trusted certificate authorities, and/or only allow specific SSL certificates in their browsers or API programs, should note that the SSL certificate for the Quickbase platform will change as follows:
4.5.1. The Common Name (also known as "CN") associated with the SSL certificate presented by the Quickbase Platform will continue to be the following wildcard value:*.quickbase.com.
4.5.2. The Certificate Authority(CA) will change to "COMODO" from "Go Daddy".
4.5.3. For those looking for more details about the current SSL certificates, you can inspect the certificates presented by the following resources:
á SSL Certificate After Enabling Cloudflare: https://help.quickbase.com/user-assistance/
Published 7 years ago
Version 1.0
