{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-10-12T02:54:09.508Z"
  },
  "data": {
    "id": "incident_statuspage_influxdb_mpp8x4qjqgft",
    "slug": "influxdb-query-performance-degradation-in-azure-westeurope-2026-08-25",
    "title": "Query performance degradation in Azure Westeurope",
    "summary": "Query performance degradation in Azure Westeurope",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2026-08-25T13:49:50.092+00:00",
    "updatedAt": "2026-09-28T13:09:25.809+00:00",
    "resolvedAt": "2026-08-25T15:41:54.986+00:00",
    "provider": {
      "slug": "influxdb",
      "name": "InfluxDB Cloud"
    },
    "affectedServices": [
      {
        "slug": "influxdb-api",
        "name": "Serverless writes & queries"
      }
    ],
    "links": {
      "html": "/incidents/influxdb-query-performance-degradation-in-azure-westeurope-2026-08-25",
      "api": "/api/v1/incidents/influxdb-query-performance-degradation-in-azure-westeurope-2026-08-25",
      "providerHtml": "/providers/influxdb",
      "alerts": "https://outagedeck.com/account?stack=influxdb&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "InfluxDB Cloud reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_influxdb_status",
      "kind": "official_api",
      "name": "InfluxDB Cloud Status",
      "checkedAt": "2026-10-12T02:45:04.378+00:00",
      "stale": false,
      "officialUrl": "https://status.influxdata.com",
      "statusPageUrl": "https://status.influxdata.com"
    },
    "updates": [
      {
        "id": "update_statuspage_influxdb_mpp8x4qjqgft_mbngp0wcyv5t",
        "status": "identified",
        "body": "The issue has been identified and a fix is being implemented.",
        "createdAt": "2026-08-25T13:49:50.195+00:00"
      },
      {
        "id": "update_statuspage_influxdb_mpp8x4qjqgft_kt6zhmwl7nhp",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-08-25T14:29:24.1+00:00"
      },
      {
        "id": "update_statuspage_influxdb_mpp8x4qjqgft_mqsbn87xght8",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-08-25T15:41:54.986+00:00"
      },
      {
        "id": "update_statuspage_influxdb_mpp8x4qjqgft_ts2g5zqhss5b",
        "status": "resolved",
        "body": "# **Root Cause Analysis: Query Latency on August 25, 2026**\n\nRegion: Azure West Europe Cluster: prod01-eu-west-1\n\n## **Summary and impact**\n\nOn August 25, 2026, some customers in Azure West Europe experienced increased query latency and query timeouts. Additional query capacity helped reduce the initial queue, but full recovery required a manual restart of a stalled storage partition. Query latency returned to normal at 15:35 UTC.\n\n## **Cause**\n\nA surge in query volume triggered scaling that quickly exhausted available resources. Shortly after the initial trigger, a storage partition did not complete startup successfully.\n\nAlthough additional capacity brought the query queue back to a nominal state, customer latency signals showed that recovery was incomplete. We discovered the stalled partition required manual intervention to complete initialization. One half of the partition remained online to serve queries and writes while its companion half was impaired.\n\nThe underlying reason for the partition startup failure remains under investigation.\n\n## **Recovery actions**\n\nThe team allocated additional query resources, then manually inspected and restarted the impaired partition after identifying the incomplete recovery. The partition fully recovered at 15:32 UTC, and query latency returned to normal at 15:35 UTC.\n\n## **Timeline**\n\nAll times are UTC.\n\nTime            Event\n\n13:13   -      Scaling alerts triggered; incident opened.\n\n13:33  -       Additional resources were added and consumed.\n\n13:35  -       Query queue returned to a nominal state.\n\n14:11   -      Impaired partition attempted a self-repair restart.\n\n14:40    -    Customer latency signals indicated incomplete recovery; investigation resumed.\n\n15:24   -     Impaired partition was manually inspected and restarted.\n\n15:32    -    Impaired partition fully recovered.\n\n15:35    -   Query latency returned to normal.\n\n## **Future Mitigations**\n\nImprovements to the partition management workflow are in progress to strengthen resilience and automate recovery. Investigation into the startup failure continues.\n\nThese improvements are ongoing work, rather than completed preventive fixes. We continue to strive for a healthy platform for all customers on our cloud infrastructure.",
        "createdAt": "2026-09-28T13:00:35.962+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}