Skip to content

Incident detail

Degraded query performance in GCP us-central1

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time InfluxDB Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating increased query errors within the region

  2. Investigating

    We are continuing to investigate this issue.

  3. Monitoring

    A fix has been implemented and we are monitoring the results.

  4. Resolved

    This incident has been resolved.

  5. Resolved

    RCA for Cloud 2 prod01-us-central-1 query outage on Nov 10, 2025

    # Summary

    The SRE team has been working on a long-term project to review and rebalance the storage workloads, to provide better separation of workloads within nodepools, which will improve performance, reliability and ease of maintenance.

    The Cloud 2 service is designed with a set of primary and secondary storage pods. During normal deployments, whenever a primary pod is restarted, the secondary pod takes over, so that the service is not interrupted. The change that was made in this cluster was a change to the primary and the secondary pods. When the configuration change was made in prod01-us-central-1, it caused some of the primary storage pods and their corresponding secondary pods to be restarted at the same time. While the pods were unavailable, queries failed. Once the pods restarted, the query error rate went back to normal levels and the cluster recovered.

    # Timeline

    Time (UTC) What happened

    8:45pm The engineer-on-call was paged due to a high rate of query errors in the cluster. Upon investigation, the primary and secondary pods for the same storage slice are unavailable.

    8:50pm Engineer-on-call identified that the problem was due to a misconfiguration that caused the primary and secondary pods to be restarted at the same time.

    9:00pm The system will recover by itself when the pods restart with the new configuration, so no intervention is required.

    9:20pm Queriers start recovering, and error rate is returning to pre-incident level. Some lingering errors in nginx.

    10:00pm Query backlog is fully cleared. The cluster has fully recovered.

    # Future Mitigations

    1. Reviewing procedures relating to storage pod reconfigurations

    Going forward we will ensure that configuration changes for primary pods and secondary pods are never applied at the same time.

Keep exploring

More from InfluxDB Cloud

Neighboring incidents on InfluxDB Cloud's timeline and the rest of their record on OutageDeck.