https://approjects-vendor-status-watch.static.hf.space/v/influxdata.htmlIncidents from InfluxData's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/p7rlkkfdswnminfluxdata:2026-09-16T10:08:27.330ZWed, 16 Sep 2026 10:08:27 +0000The issue has been identified and a fix is being implemented.https://stspg.io/7dt3n0grpnx2influxdata:2026-09-11T16:32:25.112ZFri, 11 Sep 2026 16:32:25 +0000This incident has been resolved.https://stspg.io/p3644c1wj0zkinfluxdata:2026-09-11T08:45:49.624ZFri, 11 Sep 2026 08:45:49 +0000This incident has been resolved.https://stspg.io/ctrr38xqs81cinfluxdata:2026-09-07T10:11:46.600ZMon, 07 Sep 2026 10:11:46 +0000This incident has been resolved.https://stspg.io/rrn627w0gk7sinfluxdata:2026-08-25T13:49:50.103ZTue, 25 Aug 2026 13:49:50 +0000This incident has been resolved.https://stspg.io/yzpp1z4brvmginfluxdata:2026-05-27T15:51:52.865ZWed, 27 May 2026 15:51:52 +0000This incident has been resolved.https://stspg.io/3f1bp28mtcwwinfluxdata:2026-03-17T19:18:18.200ZTue, 17 Mar 2026 19:18:18 +0000This incident has been resolved.https://stspg.io/zpvfz0jprvkdinfluxdata:2026-03-10T17:26:08.315ZTue, 10 Mar 2026 17:26:08 +0000This incident has been resolved.https://stspg.io/1dkl20dg6156influxdata:2026-03-06T03:05:20.656ZFri, 06 Mar 2026 03:05:20 +0000This incident has been resolved.https://stspg.io/f4pwyg61xljjinfluxdata:2026-02-18T23:23:23.905ZWed, 18 Feb 2026 23:23:23 +0000Cloud Dedicated Management API and Admin UI access issue has been resolved.https://stspg.io/93lxwbqj412cinfluxdata:2026-02-16T16:48:47.149ZMon, 16 Feb 2026 16:48:47 +0000Cloud Dedicated Management API and Admin UI access issue has been resolved.https://stspg.io/fkyjr2hkpgcminfluxdata:2026-02-12T11:26:55.161ZThu, 12 Feb 2026 11:26:55 +0000This incident has been resolved.https://stspg.io/vbrkgjcggffninfluxdata:2026-02-10T17:37:31.884ZTue, 10 Feb 2026 17:37:31 +0000## Summary A software change was introduced that was intended to improve data compaction for very large partitions. The change had a bug that, under certain circumstances, caused some data to be dropped during the compaction process. When compaction completed, the new compacted file \(missing a portion of the source data\) replaced the original files. This made some data unavailable until it was restored from backup. ‌ Because the underlying data remained intact in backups, no permanent data loss occurred. After identifying the issue, we rolled back the software change and initiated a full data restoration from backups. While the restoration process is reliable, restoring data at cluster scale while maintaining normal system operations required an extended recovery period. During the rehttps://stspg.io/vcxzy0jn4pckinfluxdata:2026-01-26T22:45:57.141ZMon, 26 Jan 2026 22:45:57 +0000This incident has been resolved.https://stspg.io/fj8371hb74b2influxdata:2026-01-23T03:19:53.999ZFri, 23 Jan 2026 03:19:53 +0000This incident has been resolved.https://stspg.io/mbhwjk0xtx91influxdata:2026-01-21T16:08:44.548ZWed, 21 Jan 2026 16:08:44 +0000This incident has been resolved.https://stspg.io/xl226v3p2zmginfluxdata:2026-01-20T12:31:12.627ZTue, 20 Jan 2026 12:31:12 +0000This incident has been resolved.https://stspg.io/j9pr53c9h4blinfluxdata:2026-01-15T17:18:55.000ZThu, 15 Jan 2026 17:18:55 +0000**Summary** On January 15, 2026, user login for Cloud 2 was failing intermittently in the eu-central AWS cluster. The impact was that for some users, they could not login via the web UI. For others, they were able to login but then could not see their resources \(buckets, dashboards etc.\) in the web UI. This was an intermittent issue, not affecting all users, and in some cases, recoverable by retrying. It was also isolated to the web UI and did not impact API-based writes and queries. **Cause of the Incident** The incident was caused by the clock on some of the nodes being slightly behind the master clock. When a user logs in, a JWT session token is signed with a nbf \(not-before\) timestamp based on the signing server's clock. When the request hits a gateway pod, the token is chhttps://stspg.io/vz9v69fsxswkinfluxdata:2026-01-15T17:15:15.000ZThu, 15 Jan 2026 17:15:15 +0000This incident has been resolved.https://stspg.io/d48pkz26wmyjinfluxdata:2026-01-12T11:32:18.012ZMon, 12 Jan 2026 11:32:18 +0000This incident has been resolved.https://stspg.io/6k5t1bxlj1ypinfluxdata:2026-01-09T10:41:22.441ZFri, 09 Jan 2026 10:41:22 +0000This incident has been resolved.https://stspg.io/09p9r0bvpjqjinfluxdata:2026-01-08T13:24:32.896ZThu, 08 Jan 2026 13:24:32 +0000This incident has been resolved.https://stspg.io/65nc9x3p5ymkinfluxdata:2026-01-06T21:27:27.928ZTue, 06 Jan 2026 21:27:27 +0000This incident has been resolved.https://stspg.io/8k34w6hhktvbinfluxdata:2025-12-09T16:19:11.476ZTue, 09 Dec 2025 16:19:11 +0000Query error rates have returned to normal levelshttps://stspg.io/w524qf6d0979influxdata:2025-12-09T09:49:41.382ZTue, 09 Dec 2025 09:49:41 +0000This incident has been resolved.https://stspg.io/mn2vzkq36g64influxdata:2025-11-20T21:03:31.844ZThu, 20 Nov 2025 21:03:31 +0000This incident has been resolved.https://stspg.io/zgdnprb90b6kinfluxdata:2025-11-20T08:52:19.082ZThu, 20 Nov 2025 08:52:19 +0000This incident has been resolved.https://stspg.io/1nd18xst2b2vinfluxdata:2025-11-18T19:48:25.748ZTue, 18 Nov 2025 19:48:25 +0000This incident has been resolved.https://stspg.io/kbfvmsfd67gxinfluxdata:2025-11-11T02:46:44.576ZTue, 11 Nov 2025 02:46:44 +0000RCA for Cloud 2 prod01-us-east-1 outage on Nov 11, 2025 # Summary The incident began during a planned migration of storage pods to a newer, more performant node class in Azure. The root cause was insufficient capacity in the new Azure node pool. When additional capacity could not be obtained, the team had to spend significant time rebalancing workloads across existing node pools to find a configuration capable of sustaining the write and query load. ‌ Clear communication was difficult during the incident because multiple mitigation paths were being explored in parallel, and we did not have confidence in any single fix until late in the recovery. A contributing factor to the duration of the outage was the amount of time Azure requires to apply node pool adjustments, which slowed our abihttps://stspg.io/j31d7rqd8h8kinfluxdata:2025-11-10T21:04:34.000ZMon, 10 Nov 2025 21:04:34 +0000RCA 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. Whil