Vespa Cloud - Notice history

All systems operational

Console - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 99.82%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Infrastructure - Operational

100% - uptime
Mar 2026 · 99.82%Apr · 99.71%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026
100% - uptime

AWS - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 99.71%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

GCP - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 99.71%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026
100% - uptime

Notice history

May 2026

No notices reported this month

Apr 2026

Vespa Cloud Console Maintenance
  • Update
    April 17, 2026 at 09:57
    Update
    April 17, 2026 at 09:57
    Maintenance has completed successfully.
  • Completed
    April 17, 2026 at 09:57
    Completed
    April 17, 2026 at 09:57
    Maintenance has completed successfully.
  • In progress
    April 17, 2026 at 09:00
    In progress
    April 17, 2026 at 09:00
    Maintenance is now in progress
  • Planned
    April 17, 2026 at 09:00
    Planned
    April 17, 2026 at 09:00
    We are planning for a scheduled maintenance during that time.
Vespa Cloud metrics view is unaccessible
  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update
    We are currently investigating this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.
Authentication issues with Vespa Console
  • Resolved
    Resolved

    This incident has been resolved.

  • Identified
    Identified

    We are have identified the issue and proceeding with a fix

  • Investigating
    Investigating

    We are currently investigating issues with authentication in Vespa Console

Metrics pipeline broken — Grafana dashboards reporting no incoming data
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.

Mar 2026

prod - prod.gcp-europe-west3-b isn't accessible at the moment (automated)
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    prod - prod.gcp-europe-west3-b cannot be accessed at the moment. This incident was created by an automated monitoring service.

New nodes can fail to provision -
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    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.

  • Update
    Update

    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.

  • Update
    Update

    Rollout is still in progress, still impacting new nodes on AWS.

    Existing nodes are not impacted.

  • Update
    Update

    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.

  • Update
    Update

    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.

  • Identified
    Identified

    We have identified the root cause and started working on a workaround.

  • Investigating
    Investigating

    We have observed that new nodes are failing to provision.

    Existing nodes are unaffected.

Issues with staging/system test deployments
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We deployed a fix and are currently monitoring the result.

  • Identified
    Identified

    The root cause has been identified

Node provisioning is failing, impacting all test and staging test runs, and node changes in deployments
  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update
    We implemented a fix and are currently monitoring the result.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Update
    Update

    We are continuing to work on a fix for this incident.

    We are currently testing an attempted mitigation

  • Identified
    Identified
    We are investigating
Issues with staging/system test deployments
  • Resolved
    Resolved

    The root cause has been identified and mitigated.

  • Investigating
    Investigating

    There was a period where some staging and system test deployments failed.

Mar 2026 to May 2026

Next