Is there an InfluxDB outage?
InfluxDB status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for InfluxDB and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for InfluxDB and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for InfluxDB.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| AWS: Sydney (Discontinued) | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Dedicated | Active |
| API Reads | Active |
| API Writes | Active |
| Management API | Active |
| Cloud Serverless: AWS, EU-Central | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: AWS, US-East-1 | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: AWS, US-West-2-1 | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: AWS, US-West-2-2 | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: Azure, East US | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: Azure, W. Europe | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Cloud Serverless: GCP | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Google Cloud: Belgium (Discontinued) | Active |
| API Queries | Active |
| API Writes | Active |
| Compute | Active |
| Other | Active |
| Persistent Storage | Active |
| Tasks | Active |
| Web UI | Active |
| Other Services | Active |
| Auth0 User Authentication | Active |
| Marketplace integrations | Active |
| Web UI Authentication (Auth0) | Active |
View the latest incidents for InfluxDB and check for official updates:
Description: # RCA **Degradable performance on read and write in azure-us-east on April 1, 2024** **Summary** Alerts were received indicating an increase in Time To Be Readable \(TTBR\) followed by an increase in the number of queries failing within the region **Cause** The cluster experienced a significant increase in workload which consumed the available CPU time within the storage tier. This led to the query queue growing deeper, with some queries timing out before being processed. Whenever a multi-tenant cluster experiences performance issues which do not appear to correlate to any changes that we’ve made, we first check the larger customers in the cluster to see whether they’ve exhibited any change in behavior. In this instance, a large customer had increased the number of queries being run throughout the day. The incident coincided with another large customer writing a large number of new series into the cluster, which will have led to indexes being locked more frequently than usual. The combination of the two led to the storage tier answering queries far more slowly than normal, allowing more queries to queue and therefore sustaining pressure on the system. On InfluxDB Cloud2 the performance of writes and queries is inextricably linked with changes in behavior within one path able to affect the other \(note: this is no longer the case in v3 based products such as InfluxDB Cloud Dedicated\). **Future mitigations** Multi-tenant clusters come with an inherent risk that an increase or change in workload can negatively impact other users of the cluster. When we observe significant and persistent changes in workload, we look to adjust the cluster to handle the new workload.
Status: Postmortem
Impact: Major | Started At: April 1, 2024, 8:41 p.m.
Description: # RCA **Degradable performance on read and write in azure-us-east on April 1, 2024** **Summary** Alerts were received indicating an increase in Time To Be Readable \(TTBR\) followed by an increase in the number of queries failing within the region **Cause** The cluster experienced a significant increase in workload which consumed the available CPU time within the storage tier. This led to the query queue growing deeper, with some queries timing out before being processed. Whenever a multi-tenant cluster experiences performance issues which do not appear to correlate to any changes that we’ve made, we first check the larger customers in the cluster to see whether they’ve exhibited any change in behavior. In this instance, a large customer had increased the number of queries being run throughout the day. The incident coincided with another large customer writing a large number of new series into the cluster, which will have led to indexes being locked more frequently than usual. The combination of the two led to the storage tier answering queries far more slowly than normal, allowing more queries to queue and therefore sustaining pressure on the system. On InfluxDB Cloud2 the performance of writes and queries is inextricably linked with changes in behavior within one path able to affect the other \(note: this is no longer the case in v3 based products such as InfluxDB Cloud Dedicated\). **Future mitigations** Multi-tenant clusters come with an inherent risk that an increase or change in workload can negatively impact other users of the cluster. When we observe significant and persistent changes in workload, we look to adjust the cluster to handle the new workload.
Status: Postmortem
Impact: Major | Started At: April 1, 2024, 8:41 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: March 19, 2024, 10:09 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: March 19, 2024, 10:09 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: March 14, 2024, 12:24 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
