Degraded read performance in Azure US-East 1

This incident has been resolved.

The cluster has been scaled up, and system performance has returned to normal. Writes and queries are now processing as expected, and TTBR has stabilized. We sincerely apologize for the disruption to service over the past 24 hours and will share a detailed root cause analysis (RCA) once it is complete.

We have increased the cluster capacity, and it’s currently recovering. However, due to a large backlog of data, the TTBR remains elevated for now. Our team continues to monitor this issue closely.

We apologize for the length of time that it is taking to bring this cluster back into service. The team is working diligently to restore normal operation

We apologize for the length of time that it is taking to bring this cluster back into service. The team is working diligently to restore normal operation.

Recovery is continuing, with setbacks.

Recovery is continuing to progress.

We have implemented a fix that is resulting in steady system recovery.

We have identified the issue and continuing to work on a fix.

We have identified the issue and continuing to work on a fix.

We have identified the issue and continuing to work on a fix, we are working on applying a fix.

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

We are still working on the resolution.

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

We are still working on the resolution. Access to the InfluxDB Cloud UI and API will result in internal errors.

We are still seeing stability issues. Investigating other approaches.

A fix has been implemented. We are monitoring whether read performance has improved.

Investigating fix.