Status Updates

No unscheduled downtime in 2022.

Average application response time (seconds), by quarter: Q1: 0.179, Q2: 0.303, Q3: 0.280, Q4: 0.309

Tuesday, August 24th, 2021 6:11 PM PDT
CDD Vault was unavailable for approximately 11 minutes.
Friday, July 16th, 2021 4:46 PM PDT
CDD Vault was unavailable for approximately 15 minutes.
Saturday, February 20th, 2021 1:01 PM PST
CDD Vault was unavailable for approximately 15 minutes.

Average application response time (seconds), by quarter: Q1: 0.187, Q2: 0.146, Q3: 0.169, Q4: 0.178

Thursday November 5th, 2020 10:48 PM PST
CDD Vault was unavailable for approximately 4 minutes.
Friday October 16th, 2020 3:18 PM PDT
CDD Vault was partially unavailable for approximately 10 minutes.
Thursday, July 17th, 2020 2:23 PM PDT
DNS lookups for CDD Vault were failing in some geographies for about 25 minutes due to an outage at Cloudflare.
Monday, June 8th, 2020 4:00 AM PDT
CDD Vault was unavailable for 7 minutes.
Sunday, June 7th, 2020 3:25 PM PDT
CDD Vault was unavailable for approximately 25 minutes.
Sunday, January 19th, 2020 8:02 PM PST
CDD Vault was partially unavailable for approximately 18 minutes, and unavailable for 6 minutes.

Average application response time (seconds), by quarter: Q1: 0.211, Q2: 0.222, Q3: 0.201, Q4: 0.193

Tuesday, August 20th, 2019 11:06 PM PDT
CDD Vault was partially unavailable for approximately 16 minutes.

Average application response time (seconds), by quarter: Q1: 0.323, Q2: 0.236, Q3: 0.230, Q4: 0.223

No unscheduled downtime in 2018.

Average application response time (seconds), by quarter: Q1: 0.387, Q2: 0.229, Q3: 0.349, Q4: 0.365

Saturday, April 15, 2017 11:00 PM PDT
CDD Vault was offline for approximately 55 minutes due to a hardware issue.
Saturday, January 21, 6:18 AM PST
CDD Vault was offline for 10 minutes due to a storage issue.

Average application response time (seconds), by quarter: Q1: 0.318, Q2: 0.534, Q3: 0.533, Q4: 0.503

Monday December 5, 9:27 AM PST
CDD Vault was offline for 5 minutes due to IO contention between search queries. Major infrastructure improvements are underway to improve search performance and availability.
Tuesday May 17, 5:58 AM PDT
CDD Vault was offline for 5 minutes due to IO contention between search queries.

No unscheduled downtime in 2015.

Saturday August 16, 3:03 AM PDT
CDD Vault was slow or unavailable for several minutes due to resource contention during the database backup.
Monday August 4, 9:22 AM PDT
CDD Vault was unavailable for six minutes due to high request load.
Wednesday July 23, 3:40 AM PDT
CDD Vault was unavailable for fourteen minutes due to a storage issue.
Friday June 27, 8:30 PM PDT
Scheduled downtime extended 32 minutes longer than planned due to a hardware issue.
Friday March 7, 12:23 PM PST
CDD Vault was offline for three minutes due to high request load.
Saturday March 1, 2:28 AM PST
CDD Vault was offline for a few minutes due to resource contention during the database backup.
Friday February 14, 1:40 PM PST
CDD Vault was offline for fifty minutes due to a power outage at our primary data center (the battery backup shut down during maintenance).

Saturday November 23, 1:58 AM PST
CDD Vault was offline for five hours due to a storage issue.
Monday July 8, 10:51 PM PDT
CDD Vault was offline for ten minutes due to a software defect.
Monday June 24, 7:08 PM PDT
For 35 minutes, requests to create or update molecules resulted in exceptions due to an issue with search indexing.
Tuesday June 11, 3:35 PM PDT
CDD Vault was unavailable for approximately three minutes due to unusual request load.
Monday April 1, 1:43 PM PDT
CDD Vault was unavailable for approximately fourteen minutes due to a software defect.
Wednesday March 13, 2:27 PM PDT
CDD Vault was unavailable for approximately two minutes due to a network issue.

Monday December 17, 3:12 PM PST
CDD Vault may have been unavailable to customers whose network traffic routed through Palo Alto for eight minutes due to an upstream network issue.
Thursday September 13, 11:40 PM PST
For approximately one hour, the CDD Vault application only responded successfully to 75% of requests.

Beginning of incident log