Skip to content

Incident detail

Elevated Query Error Rate

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 have observed an elevated query error rate and are investigating.

  2. Identified

    The issue has been identified and a fix is being put into place.

  3. Monitoring

    A fix has been implemented and deployed. We are monitoring at this time.

  4. Monitoring

    We are continuing to closely monitor the health of the query API

  5. Monitoring

    We are continuing to monitor this region for any further degradation

  6. Resolved

    This incident has been resolved.

  7. Resolved

    In a multi-tenant environment, such as Cloud 2, there can be unpredictable changes in workload, as different customers on the shared platform may increase or decrease their activity on the cluster with no advance notice. While we try to shelter customers from one another, via rate limits and some partitioning, there is no way to fully protect customers from the impact of a "noisy neighbor". We maintain excess capacity in the cluster to provide some amount of headroom for increased workloads, and we also have rate limits to ensure that one customer does not overwhelm the cluster (via writes, deletes or queries), but the rate limits are not very fine-grained, and at times, a single customer can stress the cluster. When that occurs, the team is automatically notified, and we add additional resources to accommodate the extra workload. It can sometimes take time for the extra capacity to be fully deployed, leading to temporary performance problems. This is what occurred in the Azure eu-west cluster on June 13th. We were notified that query performance was degraded and the team increased the storage pods to provide extra capacity. Once the storage pods limits were fully applied, the query TTBR recovered.

    We apologize for the inconvenience.

Keep exploring

More from InfluxDB Cloud

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