Vespa Cloud Status - Incident history https://status.vespa.ai Vespa Cloud Fri, 17 Apr 2026 09:00:00 +0000 Vespa Cloud Console Maintenance Type: Maintenance Duration: 57 minutes Affected Components: Console Apr 17, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Apr 17, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 17, 09:57:01 GMT+0 - Completed - Maintenance has completed successfully. Apr 17, 09:57:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 57 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:57:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>09:57:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Fri, 17 Apr 2026 09:00:00 +0000 https://status.vespa.ai/maintenance/cmo2n1d7q0cmwz3zj3cax0qhx https://status.vespa.ai/maintenance/cmo2n1d7q0cmwz3zj3cax0qhx Vespa Cloud metrics view is unaccessible Type: Incident Duration: 3 hours and 38 minutes Affected Components: Console Apr 9, 12:44:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 9, 14:50:18 GMT+0 - Investigating - We are currently investigating this incident. Apr 9, 16:22:23 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 38 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>12:44:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>14:50:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>16:22:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 9 Apr 2026 12:44:00 +0000 https://status.vespa.ai/incident/cmnrmmmtk00ccx4z76glkb4md https://status.vespa.ai/incident/cmnrmmmtk00ccx4z76glkb4md Authentication issues with Vespa Console Type: Incident Affected Components: Console Apr 8, 09:13:00 GMT+0 - Investigating - We are currently investigating issues with authentication in Vespa Console Apr 8, 09:28:00 GMT+0 - Resolved - This incident has been resolved. Apr 8, 09:25:00 GMT+0 - Identified - We are have identified the issue and proceeding with a fix Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>09:13:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating issues with authentication in Vespa Console.</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>09:28:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>09:25:00</var> GMT+0</small><br><strong>Identified</strong> - We are have identified the issue and proceeding with a fix.</p> ]]> Wed, 8 Apr 2026 09:13:00 +0000 https://status.vespa.ai/incident/cmnpulhk402xcx917ddu0xjpn https://status.vespa.ai/incident/cmnpulhk402xcx917ddu0xjpn Metrics pipeline broken — Grafana dashboards reporting no incoming data Type: Incident Duration: 2 hours and 6 minutes Affected Components: , AWS, staging.gcp-us-central1-f, prod.aws-eu-west-1a, prod.aws-us-west-2a, perf.aws-us-east-1c, Infrastructure, prod.aws-us-east-1c, prod.gcp-us-central1-f, test.aws-us-east-1c, dev.aws-euw1-az1, prod.aws-apne1-az1, prod.aws-cac1-az1, prod.aws-euw1-az1, prod.gcp-us-central1-c, prod.gcp-us-central1-a, GCP, staging.aws-us-east-1c, prod.aws-euc1-az1, prod.gcp-europe-west3-b, prod.gcp-us-central1-b, prod.aws-ap-northeast-1a, prod.aws-aps1-az1, prod.aws-euc1-az3, prod.aws-use1-az4, test.gcp-us-central1-f, , , , prod.aws-cac1-az2, , prod.aws-use2-az1, prod.aws-use2-az3, prod.aws-usw2-az3, , dev.aws-us-east-1c, dev.gcp-us-central1-f, Enclave → dev → prod → test → perf → Zones → Apr 1, 00:50:14 GMT+0 - Investigating - We are currently investigating this incident. Apr 1, 02:22:24 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 1, 02:56:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 6 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>00:50:14</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>02:22:24</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>02:56:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 1 Apr 2026 00:50:14 +0000 https://status.vespa.ai/incident/cmnfbx2ce0vr213atwrrjzslo https://status.vespa.ai/incident/cmnfbx2ce0vr213atwrrjzslo prod - prod.gcp-europe-west3-b isn't accessible at the moment (automated) Type: Incident Duration: 1 hour and 53 minutes Affected Components: prod.gcp-europe-west3-b Mar 27, 03:47:23 GMT+0 - Investigating - prod - prod.gcp-europe-west3-b cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 27, 05:40:43 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 53 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>03:47:23</var> GMT+0</small><br><strong>Investigating</strong> - prod - prod.gcp-europe-west3-b cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>05:40:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 27 Mar 2026 03:47:23 +0000 https://status.vespa.ai/incident/cmn8d1meu04a2k9ymoajvolsc https://status.vespa.ai/incident/cmn8d1meu04a2k9ymoajvolsc New nodes can fail to provision - Type: Incident Duration: 6 hours and 33 minutes Affected Components: AWS, prod.aws-eu-west-1a, prod.aws-us-west-2a, perf.aws-us-east-1c, prod.aws-us-east-1c, test.aws-us-east-1c, dev.aws-euw1-az1, prod.aws-apne1-az1, prod.aws-cac1-az1, prod.aws-euw1-az1, staging.aws-us-east-1c, prod.aws-euc1-az1, prod.aws-ap-northeast-1a, prod.aws-aps1-az1, prod.aws-euc1-az3, prod.aws-use1-az4, prod.aws-cac1-az2, prod.aws-use2-az1, prod.aws-use2-az3, prod.aws-usw2-az3, dev.aws-us-east-1c Mar 6, 07:30:00 GMT+0 - Investigating - We have observed that new nodes are failing to provision. **Existing nodes are unaffected.** Mar 6, 09:07:35 GMT+0 - Identified - We have identified the root cause and started working on a workaround. Mar 6, 10:06:58 GMT+0 - Identified - We are continuing to work on a fix for this incident, we have noticed failures in more zones for new hosts. _Ticket updated with the new Zones._ **Existing nodes are unaffected, only provisioning of new nodes is impacted.** Mar 6, 10:35:34 GMT+0 - Identified - We have implemented a fix and it is currently rolling out fleet-wide. Provision of **new nodes** is still impacted, but we should resolve within 30 minutes, we will post an update as soon as possible, or by 11:00 UTC in any case. **Existing nodes are not affected.** Mar 6, 11:09:03 GMT+0 - Identified - Rollout is still in progress, still impacting **new nodes on AWS**. **Existing nodes are not impacted.** Mar 6, 11:43:09 GMT+0 - Identified - We have found an edge-case which has been slowing down the rollout, we're in the process of mitigating this issue. For now **new hosts** are still impacted. New update at 12:15 or earlier. There is **no impact for existing nodes.** Mar 6, 12:47:19 GMT+0 - Monitoring - The rollout is compete and new nodes are able to provision. We are monitoring the situation and will post a final update later today. Mar 6, 14:03:22 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 hours and 33 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , ,

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>07:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We have observed that new nodes are failing to provision. **Existing nodes are unaffected.**.</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>09:07:35</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause and started working on a workaround..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>10:06:58</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident, we have noticed failures in more zones for new hosts. _Ticket updated with the new Zones._ **Existing nodes are unaffected, only provisioning of new nodes is impacted.**.</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>10:35:34</var> GMT+0</small><br><strong>Identified</strong> - We have implemented a fix and it is currently rolling out fleet-wide. Provision of **new nodes** is still impacted, but we should resolve within 30 minutes, we will post an update as soon as possible, or by 11:00 UTC in any case. **Existing nodes are not affected.**.</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>11:09:03</var> GMT+0</small><br><strong>Identified</strong> - Rollout is still in progress, still impacting **new nodes on AWS**. **Existing nodes are not impacted.**.</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>11:43:09</var> GMT+0</small><br><strong>Identified</strong> - We have found an edge-case which has been slowing down the rollout, we're in the process of mitigating this issue. For now **new hosts** are still impacted. New update at 12:15 or earlier. There is **no impact for existing nodes.**.</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>12:47:19</var> GMT+0</small><br><strong>Monitoring</strong> - The rollout is compete and new nodes are able to provision. We are monitoring the situation and will post a final update later today..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>14:03:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 6 Mar 2026 07:30:00 +0000 https://status.vespa.ai/incident/cmmepi8z4000d3xjzgbtmlg49 https://status.vespa.ai/incident/cmmepi8z4000d3xjzgbtmlg49 Issues with staging/system test deployments Type: Incident Duration: 22 days, 8 hours and 28 minutes Affected Components: staging.gcp-us-central1-f, test.aws-us-east-1c, staging.aws-us-east-1c, test.gcp-us-central1-f Mar 4, 23:15:00 GMT+0 - Identified - The root cause has been identified Mar 5, 05:45:00 GMT+0 - Monitoring - We deployed a fix and are currently monitoring the result. Mar 27, 07:43:29 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 22 days, 8 hours and 28 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>23:15:00</var> GMT+0</small><br><strong>Identified</strong> - The root cause has been identified.</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>05:45:00</var> GMT+0</small><br><strong>Monitoring</strong> - We deployed a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>07:43:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 4 Mar 2026 23:15:00 +0000 https://status.vespa.ai/incident/cmmdbpczm02cpx7bgt52w6ujt https://status.vespa.ai/incident/cmmdbpczm02cpx7bgt52w6ujt Node provisioning is failing, impacting all test and staging test runs, and node changes in deployments Type: Incident Duration: 5 hours and 41 minutes Affected Components: Infrastructure Mar 4, 12:01:01 GMT+0 - Resolved - This incident has been resolved. Mar 4, 06:20:00 GMT+0 - Identified - We are investigating Mar 4, 10:41:18 GMT+0 - Identified - We are continuing to work on a fix for this incident. We are currently testing an attempted mitigation Mar 4, 10:43:31 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 4, 10:53:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 5 hours and 41 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>12:01:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>06:20:00</var> GMT+0</small><br><strong>Identified</strong> - We are investigating.</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:41:18</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. We are currently testing an attempted mitigation.</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:43:31</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:53:07</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 4 Mar 2026 06:20:00 +0000 https://status.vespa.ai/incident/cmmbs9mim00nl10ssrdpw94vi https://status.vespa.ai/incident/cmmbs9mim00nl10ssrdpw94vi Issues with staging/system test deployments Type: Incident Duration: 7 hours and 40 minutes Affected Components: test.aws-us-east-1c, staging.gcp-us-central1-f, staging.aws-us-east-1c, test.gcp-us-central1-f Mar 3, 23:15:00 GMT+0 - Investigating - There was a period where some staging and system test deployments failed. Mar 4, 06:55:00 GMT+0 - Resolved - The root cause has been identified and mitigated. Type: Incident

Duration: 7 hours and 40 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>23:15:00</var> GMT+0</small><br><strong>Investigating</strong> - There was a period where some staging and system test deployments failed..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>06:55:00</var> GMT+0</small><br><strong>Resolved</strong> - The root cause has been identified and mitigated..</p> ]]> Tue, 3 Mar 2026 23:15:00 +0000 https://status.vespa.ai/incident/cmmbwbt670n5p50p1wokttahl https://status.vespa.ai/incident/cmmbwbt670n5p50p1wokttahl Issues with staging/system test deployments Type: Incident Duration: 1 day and 1 hour Affected Components: test.aws-us-east-1c, staging.gcp-us-central1-f, staging.aws-us-east-1c, test.gcp-us-central1-f Feb 28, 14:00:00 GMT+0 - Investigating - There was a period where some staging and system test deployments failed. The root cause has been identified and fixed. Mar 1, 15:00:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day and 1 hour

Affected Components: , , ,

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Investigating</strong> - There was a period where some staging and system test deployments failed. The root cause has been identified and fixed..</p> <p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 28 Feb 2026 14:00:00 +0000 https://status.vespa.ai/incident/cmm9dyv1w0af46l72zsgjqgfs https://status.vespa.ai/incident/cmm9dyv1w0af46l72zsgjqgfs Vespa Cloud Console Maintenance Type: Maintenance Duration: 12 minutes Affected Components: Console Feb 20, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 20, 11:11:58 GMT+0 - Completed - Maintenance has completed successfully. Feb 20, 11:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. No downtime is expected. Type: Maintenance

Duration: 12 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:11:58</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. No downtime is expected..</p> ]]> Fri, 20 Feb 2026 11:00:00 +0000 https://status.vespa.ai/maintenance/cmlthtoio04qj24hsd6x76jaq https://status.vespa.ai/maintenance/cmlthtoio04qj24hsd6x76jaq Issues with new host provisioning Type: Incident Duration: 3 hours and 48 minutes Affected Components: AWS, prod.gcp-europe-west3-b, test.aws-us-east-1c, staging.gcp-us-central1-f, staging.aws-us-east-1c, prod.aws-eu-west-1a, prod.aws-us-west-2a, perf.aws-us-east-1c, GCP, Infrastructure, prod.aws-us-east-1c, prod.gcp-us-central1-f, test.gcp-us-central1-f, dev.aws-us-east-1c, dev.gcp-us-central1-f, Console Feb 10, 11:28:07 GMT+0 - Investigating - We are experiencing a technical issue that is impacting provisioning of new Vespa hosts. Provisioning requests may fail or be delayed while we work to resolve the problem. **Existing deployments remain unaffected.** We are currently investigating this incident. Feb 10, 12:39:50 GMT+0 - Identified - We have identified the root cause and are taking the necessary steps to resolve the issue. Feb 10, 12:59:35 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 10, 15:15:59 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 48 minutes

Affected Components: , , , , , , , , , , , , , , ,

<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>11:28:07</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing a technical issue that is impacting provisioning of new Vespa hosts. Provisioning requests may fail or be delayed while we work to resolve the problem. **Existing deployments remain unaffected.** We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>12:39:50</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause and are taking the necessary steps to resolve the issue..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>12:59:35</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>15:15:59</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 10 Feb 2026 11:28:07 +0000 https://status.vespa.ai/incident/cmlgiost217l05p7vd6jowrgy https://status.vespa.ai/incident/cmlgiost217l05p7vd6jowrgy Vespa Cloud Console Slow or Unavailable Type: Incident Duration: 43 minutes Affected Components: Console Feb 5, 20:45:00 GMT+0 - Investigating - We are aware of slowdowns and downtime in the Vespa Console, we are currently investigating this incident. Feb 5, 21:07:46 GMT+0 - Identified - We have identified the issue and are working on a workaround. Feb 5, 21:28:21 GMT+0 - Resolved - This incident has been resolved, we have had a misconfiguration in autoscaling which prevented an immediate automatic resolution. We have implemented a workaround and will implement a permanent fix in the next days. Type: Incident

Duration: 43 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>20:45:00</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of slowdowns and downtime in the Vespa Console, we are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>21:07:46</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and are working on a workaround..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>21:28:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, we have had a misconfiguration in autoscaling which prevented an immediate automatic resolution. We have implemented a workaround and will implement a permanent fix in the next days..</p> ]]> Thu, 5 Feb 2026 20:45:00 +0000 https://status.vespa.ai/incident/cml9y5r7v00033m8w7z1ezl9u https://status.vespa.ai/incident/cml9y5r7v00033m8w7z1ezl9u Missing metrics from GCP and enclave Type: Incident Duration: 39 minutes Affected Components: Console Jan 17, 09:52:58 GMT+0 - Investigating - The metrics shown in console are incomplete for applications running in GCP and enclave. We are currently investigating this incident. Jan 17, 10:16:09 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 17, 10:31:32 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>09:52:58</var> GMT+0</small><br><strong>Investigating</strong> - The metrics shown in console are incomplete for applications running in GCP and enclave. We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>10:16:09</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>10:31:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 17 Jan 2026 09:52:58 +0000 https://status.vespa.ai/incident/cmki4pzur073e8nn6utsrf1x3 https://status.vespa.ai/incident/cmki4pzur073e8nn6utsrf1x3 Missing Metrics for GCP and Enclave Accounts Type: Incident Duration: 8 hours and 39 minutes Affected Components: prod.gcp-europe-west3-b, staging.gcp-us-central1-f, GCP, prod.gcp-us-central1-f, test.gcp-us-central1-f Jan 4, 12:20:00 GMT+0 - Investigating - We are currently investigating this incident. Jan 4, 19:57:49 GMT+0 - Monitoring - We have applied a fix and are currently monitoring the result. Jan 4, 20:58:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 8 hours and 39 minutes

Affected Components: , , , ,

<p><small>Jan <var data-var='date'> 4</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 4</var>, <var data-var='time'>19:57:49</var> GMT+0</small><br><strong>Monitoring</strong> - We have applied a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 4</var>, <var data-var='time'>20:58:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 4 Jan 2026 12:20:00 +0000 https://status.vespa.ai/incident/cmk03c8690123et5dbqlkmarl https://status.vespa.ai/incident/cmk03c8690123et5dbqlkmarl Missing Metrics for GCP and Enclave (All) Type: Incident Duration: 5 days and 30 minutes Affected Components: AWS, prod.gcp-europe-west3-b, staging.gcp-us-central1-f, GCP, prod.gcp-us-central1-f, dev.gcp-us-central1-f Dec 12, 11:09:00 GMT+0 - Investigating - We identified an issue which is preventing metrics to be published to our systems.. We are investigating the issue. Dec 17, 11:39:08 GMT+0 - Resolved - This incident has been resolved. Dec 16, 10:24:22 GMT+0 - Identified - The first attempts to resolve this failed We are continuing to work on a fix for this incident. Dec 12, 15:00:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the progress. Dec 16, 16:47:27 GMT+0 - Monitoring - We have applied a fix and are currently monitoring the result. Type: Incident

Duration: 5 days and 30 minutes

Affected Components: , , , , ,

<p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>11:09:00</var> GMT+0</small><br><strong>Investigating</strong> - We identified an issue which is preventing metrics to be published to our systems.. We are investigating the issue..</p> <p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>11:39:08</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>10:24:22</var> GMT+0</small><br><strong>Identified</strong> - The first attempts to resolve this failed We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the progress..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>16:47:27</var> GMT+0</small><br><strong>Monitoring</strong> - We have applied a fix and are currently monitoring the result..</p> ]]> Fri, 12 Dec 2025 11:09:00 +0000 https://status.vespa.ai/incident/cmj32ve7r070j12dnedon30sv https://status.vespa.ai/incident/cmj32ve7r070j12dnedon30sv Temporary downtime of sign in on Vespa Cloud Console Type: Maintenance Duration: 30 minutes Affected Components: Console Dec 9, 13:00:00 GMT+0 - Identified - We are preparing to perform maintenance on the sign-in functionality on the Vespa Cloud Console. Sign in functionality may be sporadically unavailable for up to 30 minutes. This will affect only the control plane login, data plane authentication will remain functional during this maintenance window. Dec 9, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 9, 13:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 30 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are preparing to perform maintenance on the sign-in functionality on the Vespa Cloud Console. Sign in functionality may be sporadically unavailable for up to 30 minutes. This will affect only the control plane login, data plane authentication will remain functional during this maintenance window..</p> <p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 9 Dec 2025 13:00:00 +0000 https://status.vespa.ai/maintenance/cmiyl2l2d07k9c8n9oaf29fu3 https://status.vespa.ai/maintenance/cmiyl2l2d07k9c8n9oaf29fu3 AWS experiences issues in us-east-1 Type: Incident Duration: 23 hours and 36 minutes Affected Components: AWS, dev.aws-us-east-1c, test.aws-us-east-1c, staging.aws-us-east-1c, perf.aws-us-east-1c, Infrastructure, prod.aws-us-east-1c Oct 20, 07:11:00 GMT+0 - Identified - Track status on <https://health.aws.amazon.com/health/status> Existing applications are not affected by outage. Only maintenance operations are degraded. Oct 20, 10:26:36 GMT+0 - Monitoring - Infrastructure services restored, we will continue to monitor the situation for any residual issues. Oct 20, 16:50:39 GMT+0 - Monitoring - We are still experiencing the failures with provisioning new hosts on AWS us-east region. Therefore, we recommend to avoid applying changes to the applications on this region until the issue is resolved on AWS side. Oct 20, 20:58:27 GMT+0 - Monitoring - Infrastructure services are now opertional. We continue to monitor our system performance to detect residual issues. Oct 21, 06:47:23 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 hours and 36 minutes

Affected Components: , , , , , ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>07:11:00</var> GMT+0</small><br><strong>Identified</strong> - Track status on <https://health.aws.amazon.com/health/status> Existing applications are not affected by outage. Only maintenance operations are degraded..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>10:26:36</var> GMT+0</small><br><strong>Monitoring</strong> - Infrastructure services restored, we will continue to monitor the situation for any residual issues..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:50:39</var> GMT+0</small><br><strong>Monitoring</strong> - We are still experiencing the failures with provisioning new hosts on AWS us-east region. Therefore, we recommend to avoid applying changes to the applications on this region until the issue is resolved on AWS side. .</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:58:27</var> GMT+0</small><br><strong>Monitoring</strong> - Infrastructure services are now opertional. We continue to monitor our system performance to detect residual issues..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>06:47:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 20 Oct 2025 07:11:00 +0000 https://status.vespa.ai/incident/cmgytgo3p00mlmx24ihc87kdx https://status.vespa.ai/incident/cmgytgo3p00mlmx24ihc87kdx Issues with metric dashboards in Vespa Console Type: Incident Duration: 3 hours and 13 minutes Affected Components: Console Aug 22, 15:08:28 GMT+0 - Resolved - This incident on Grafana is still open, but we don't observe any effect on our side. Aug 22, 11:55:00 GMT+0 - Monitoring - We have identified an issue in our vespa Console, when clicking on "Metrics" for an application we you might experience "Failed to load dashboard - Internal Server Error" This is caused by an outage in Grafana, for more details please refer to \[the Grafana Status Page\](https://status.grafana.com/incidents/z42xrjqydny8) updates. Type: Incident

Duration: 3 hours and 13 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>15:08:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident on Grafana is still open, but we don't observe any effect on our side..</p> <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>11:55:00</var> GMT+0</small><br><strong>Monitoring</strong> - We have identified an issue in our vespa Console, when clicking on "Metrics" for an application we you might experience "Failed to load dashboard - Internal Server Error" This is caused by an outage in Grafana, for more details please refer to \[the Grafana Status Page\](https://status.grafana.com/incidents/z42xrjqydny8) updates..</p> ]]> Fri, 22 Aug 2025 11:55:00 +0000 https://status.vespa.ai/incident/cmems9mnk0001107un22ahtkn https://status.vespa.ai/incident/cmems9mnk0001107un22ahtkn Provisioning new nodes might fail Type: Incident Duration: 1 hour and 12 minutes Affected Components: perf.aws-us-east-1c, test.gcp-us-central1-f, prod.aws-us-east-1c, prod.gcp-europe-west3-b, prod.gcp-us-central1-f, staging.gcp-us-central1-f, test.aws-us-east-1c, staging.aws-us-east-1c, dev.aws-us-east-1c, , prod.aws-eu-west-1a, prod.aws-us-west-2a, dev.gcp-us-central1-f, Zones → Jul 2, 06:31:58 GMT+0 - Investigating - We are currently investigating this incident. Jul 2, 06:47:51 GMT+0 - Identified - We have identified the root cause and we are applying a mitigation to allow nodes to be provisioned. Jul 2, 07:00:57 GMT+0 - Monitoring - Workaround is in place, so it should be possible to provision new nodes. If you encounter issues don't hesitate to contact support. Jul 2, 07:43:51 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 12 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>06:31:58</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>06:47:51</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause and we are applying a mitigation to allow nodes to be provisioned..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:00:57</var> GMT+0</small><br><strong>Monitoring</strong> - Workaround is in place, so it should be possible to provision new nodes. If you encounter issues don't hesitate to contact support..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:43:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 2 Jul 2025 06:31:58 +0000 https://status.vespa.ai/incident/cmclkwzow01fxt1chtevzvasm https://status.vespa.ai/incident/cmclkwzow01fxt1chtevzvasm Metrics dashboard not working for GCP and enclave applications Type: Incident Duration: 1 hour and 1 minute Affected Components: Console Jun 26, 12:17:20 GMT+0 - Investigating - New data will not be populated in the dashboard, while historical data is still visible. We are currently investigating this incident. Jun 26, 13:18:09 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 1 minute

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:17:20</var> GMT+0</small><br><strong>Investigating</strong> - New data will not be populated in the dashboard, while historical data is still visible. We are currently investigating this incident. .</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>13:18:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 26 Jun 2025 12:17:20 +0000 https://status.vespa.ai/incident/cmcdcm03p002f7gde7sg7nl6g https://status.vespa.ai/incident/cmcdcm03p002f7gde7sg7nl6g The vespa release rolled out today, vespa-8.534.59, introduced an issue affecting applications with containers running embedders Type: Incident Duration: 14 hours and 10 minutes Affected Components: Infrastructure Jun 16, 08:30:00 GMT+0 - Identified - Impact: \* Any application changes will fail to be successfully deployed \* Autoscaling: New nodes added to such container clusters will fail to start We have implemented a fix that we currently are testing \[Embedding Reference\](https://docs.vespa.ai/en/reference/embedding-reference.html) Jun 16, 14:54:51 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 16, 21:29:16 GMT+0 - Monitoring - We have implemented a fix and created a new release, which is now being rolled out across our infrastructure. Once the deployment is complete, the issue reported in this incident will be considered resolved. Jun 16, 22:40:06 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 14 hours and 10 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> - Impact: \* Any application changes will fail to be successfully deployed \* Autoscaling: New nodes added to such container clusters will fail to start We have implemented a fix that we currently are testing \[Embedding Reference\](https://docs.vespa.ai/en/reference/embedding-reference.html).</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>14:54:51</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>21:29:16</var> GMT+0</small><br><strong>Monitoring</strong> - We have implemented a fix and created a new release, which is now being rolled out across our infrastructure. Once the deployment is complete, the issue reported in this incident will be considered resolved..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>22:40:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 16 Jun 2025 08:30:00 +0000 https://status.vespa.ai/incident/cmbz7ph1i000gq87zjzk79lst https://status.vespa.ai/incident/cmbz7ph1i000gq87zjzk79lst Performance regression on release 8.528.12 Type: Incident Duration: 3 hours and 23 minutes Affected Components: perf.aws-us-east-1c, test.gcp-us-central1-f, prod.aws-us-east-1c, prod.gcp-europe-west3-b, prod.gcp-us-central1-f, staging.gcp-us-central1-f, test.aws-us-east-1c, staging.aws-us-east-1c, dev.aws-us-east-1c, , prod.aws-eu-west-1a, prod.aws-us-west-2a, dev.gcp-us-central1-f, Zones → Jun 3, 11:36:20 GMT+0 - Investigating - We are have identified a regression on the vespa release 8.528.12. Jun 3, 11:47:59 GMT+0 - Identified - All the upgrades in Vespa Cloud are being stopped and any application already upgraded will be automatically downgraded. Jun 3, 12:17:43 GMT+0 - Monitoring - All production applications have been rolled back the the previous version, there should not be any impact at the current moment. We will be monitoring the situation for a while. Jun 3, 14:59:40 GMT+0 - Resolved - We don't see any further impact. Please don't hesitate to contact our support through the Vespa Cloud panel if you still experience any disruption. Type: Incident

Duration: 3 hours and 23 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:36:20</var> GMT+0</small><br><strong>Investigating</strong> - We are have identified a regression on the vespa release 8.528.12..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:47:59</var> GMT+0</small><br><strong>Identified</strong> - All the upgrades in Vespa Cloud are being stopped and any application already upgraded will be automatically downgraded..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>12:17:43</var> GMT+0</small><br><strong>Monitoring</strong> - All production applications have been rolled back the the previous version, there should not be any impact at the current moment. We will be monitoring the situation for a while..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>14:59:40</var> GMT+0</small><br><strong>Resolved</strong> - We don't see any further impact. Please don't hesitate to contact our support through the Vespa Cloud panel if you still experience any disruption..</p> ]]> Tue, 3 Jun 2025 11:36:20 +0000 https://status.vespa.ai/incident/cmbgg0p79000equffv437p932 https://status.vespa.ai/incident/cmbgg0p79000equffv437p932 Issues new deployments in Dev zones Type: Incident Duration: 12 hours and 47 minutes Affected Components: dev.aws-us-east-1c, dev.gcp-us-central1-f May 22, 22:17:00 GMT+0 - Resolved - This incident has been resolved. May 22, 20:30:00 GMT+0 - Investigating - We are currently investigating an incident affecting new deployments in Dev. May 22, 20:58:04 GMT+0 - Identified - We identified the root of the problem and it is affecting only a subset of hosts. We are working on a fix. May 22, 22:10:22 GMT+0 - Monitoring - We have resolved the issue that caused some deployments to fail Type: Incident

Duration: 12 hours and 47 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>22:17:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>20:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident affecting new deployments in Dev..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>20:58:04</var> GMT+0</small><br><strong>Identified</strong> - We identified the root of the problem and it is affecting only a subset of hosts. We are working on a fix..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>22:10:22</var> GMT+0</small><br><strong>Monitoring</strong> - We have resolved the issue that caused some deployments to fail.</p> ]]> Thu, 22 May 2025 20:30:00 +0000 https://status.vespa.ai/incident/cmazula79001311nk2jb9tsn7 https://status.vespa.ai/incident/cmazula79001311nk2jb9tsn7 Provisioning failures in dev.aws-us-east-1c Type: Incident Duration: 23 hours and 29 minutes Affected Components: dev.aws-us-east-1c Apr 21, 11:57:00 GMT+0 - Investigating - Due to increased demand, we are seeing failures in launching instances for new tenants. We are currently investigating this incident. Apr 22, 08:52:23 GMT+0 - Monitoring - We have identified the issue and increased the limits so new tenants should start working. We are now monitoring to confirm that this resolves the issue. Apr 22, 11:25:49 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 hours and 29 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>11:57:00</var> GMT+0</small><br><strong>Investigating</strong> - Due to increased demand, we are seeing failures in launching instances for new tenants. We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>08:52:23</var> GMT+0</small><br><strong>Monitoring</strong> - We have identified the issue and increased the limits so new tenants should start working. We are now monitoring to confirm that this resolves the issue..</p> <p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>11:25:49</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 21 Apr 2025 11:57:00 +0000 https://status.vespa.ai/incident/cm9s8b72e004lh2rii8i6frg5 https://status.vespa.ai/incident/cm9s8b72e004lh2rii8i6frg5 Missing metrics from on GCP and Enclave Type: Incident Duration: 4 hours and 20 minutes Affected Components: staging.gcp-us-central1-f, dev.gcp-us-central1-f, test.gcp-us-central1-f, prod.gcp-europe-west3-b, prod.gcp-us-central1-f, AWS, GCP Apr 8, 08:16:44 GMT+0 - Identified - We have identified one problem with our telemetry gateway and are working on a fix. Apr 8, 07:36:26 GMT+0 - Investigating - We are currently investigating this incident. Apr 8, 09:19:15 GMT+0 - Monitoring - We have applied a workaround and we see the data metrics flowing back in our systems. We are now monitoring the situation. Apr 8, 11:56:01 GMT+0 - Resolved - We can confirm that all the systems have been successfully working since our workaround is applied and the final fix has been applied. Type: Incident

Duration: 4 hours and 20 minutes

Affected Components: , , , , , ,

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>08:16:44</var> GMT+0</small><br><strong>Identified</strong> - We have identified one problem with our telemetry gateway and are working on a fix..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>07:36:26</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>09:19:15</var> GMT+0</small><br><strong>Monitoring</strong> - We have applied a workaround and we see the data metrics flowing back in our systems. We are now monitoring the situation..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>11:56:01</var> GMT+0</small><br><strong>Resolved</strong> - We can confirm that all the systems have been successfully working since our workaround is applied and the final fix has been applied..</p> ]]> Tue, 8 Apr 2025 07:36:26 +0000 https://status.vespa.ai/incident/cm986shm0008qsp4flqbc6ms6 https://status.vespa.ai/incident/cm986shm0008qsp4flqbc6ms6 Metrics view in application console unavailable due to Grafana incident with AWS Type: Incident Duration: 3 hours and 39 minutes Affected Components: Console Feb 18, 08:43:00 GMT+0 - Identified - We are monitoring the progress via <https://status.grafana.com/> Feb 18, 12:21:43 GMT+0 - Resolved - The part of the Grafana incident that had an impact on the rendring of the metrics in the Vespa Cloud console has been resolved Type: Incident

Duration: 3 hours and 39 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>08:43:00</var> GMT+0</small><br><strong>Identified</strong> - We are monitoring the progress via <https://status.grafana.com/>.</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>12:21:43</var> GMT+0</small><br><strong>Resolved</strong> - The part of the Grafana incident that had an impact on the rendring of the metrics in the Vespa Cloud console has been resolved.</p> ]]> Tue, 18 Feb 2025 08:43:00 +0000 https://status.vespa.ai/incident/cm7act6cx002om2eggsyn4fwt https://status.vespa.ai/incident/cm7act6cx002om2eggsyn4fwt New deployments, node increase, and replacements might fail in prod.gcp-europe-west3-b Type: Incident Duration: 5 hours and 48 minutes Affected Components: prod.gcp-europe-west3-b Oct 7, 08:00:00 GMT+0 - Investigating - We have identified that some deployments are fail in the `prod.gcp-europe-west3-b` zone, we are investigating the issue. Oct 7, 09:00:00 GMT+0 - Identified - We have identified the source of the issue being one of the Quota limits in GCP. The team has been working with Google Cloud Platform (GCP) to increase quotas. Oct 7, 12:40:44 GMT+0 - Identified - We are still waiting from Google Cloud Platform to update our quota for the affected Zone. **Note:** This incident has **no impact on application performances**. Only _new applications and deployments_ with large local storage _might_ be affected. Oct 7, 13:47:34 GMT+0 - Resolved - We have received confirmation from the Google Compute Platform (GCP) that quotas on our account have been updated, this issue has now been be resolved. Type: Incident

Duration: 5 hours and 48 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We have identified that some deployments are fail in the `prod.gcp-europe-west3-b` zone, we are investigating the issue..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the source of the issue being one of the Quota limits in GCP. The team has been working with Google Cloud Platform (GCP) to increase quotas..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>12:40:44</var> GMT+0</small><br><strong>Identified</strong> - We are still waiting from Google Cloud Platform to update our quota for the affected Zone. **Note:** This incident has **no impact on application performances**. Only _new applications and deployments_ with large local storage _might_ be affected..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>13:47:34</var> GMT+0</small><br><strong>Resolved</strong> - We have received confirmation from the Google Compute Platform (GCP) that quotas on our account have been updated, this issue has now been be resolved..</p> ]]> Mon, 7 Oct 2024 08:00:00 +0000 https://status.vespa.ai/incident/cm1yxjree003n11ysqtggmk5c https://status.vespa.ai/incident/cm1yxjree003n11ysqtggmk5c Vespa Cloud console maintenance Type: Maintenance Duration: 5 minutes Affected Components: Console Sep 4, 07:15:01 GMT+0 - Identified - Maintenance is now in progress Sep 4, 07:20:00 GMT+0 - Completed - Maintenance has completed successfully Sep 4, 07:15:00 GMT+0 - Identified - We are planning a Vespa Cloud console maintenance. The console will be unavailable for a few minutes Type: Maintenance

Duration: 5 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>07:15:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>07:20:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning a Vespa Cloud console maintenance. The console will be unavailable for a few minutes.</p> ]]> Wed, 4 Sep 2024 07:15:00 +0000 https://status.vespa.ai/maintenance/cm0niqq02004vl3c8tq3x35xq https://status.vespa.ai/maintenance/cm0niqq02004vl3c8tq3x35xq