Company Logo

Is there an InfluxDB outage?

InfluxDB status: Systems Active

Last checked: 6 minutes ago

Get notified about any outages, downtime or incidents for InfluxDB and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

InfluxDB outages and incidents

Outage and incident data over the last 30 days for InfluxDB.

There have been 1 outages or incidents for InfluxDB in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for InfluxDB

Outlogger tracks the status of these components for Xero:

API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Reads Active
API Writes Active
Management API Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Auth0 User Authentication Active
Marketplace integrations Active
Web UI Authentication (Auth0) Active
Component Status
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Reads Active
API Writes Active
Management API Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
API Queries Active
API Writes Active
Compute Active
Other Active
Persistent Storage Active
Tasks Active
Web UI Active
Active
Auth0 User Authentication Active
Marketplace integrations Active
Web UI Authentication (Auth0) Active

Latest InfluxDB outages and incidents.

View the latest incidents for InfluxDB and check for official updates:

Updates:

  • Time: Jan. 25, 2023, 11:49 a.m.
    Status: Resolved
    Update: Incident has been resolved for any more info please check out https://status.azure.com/en-gb/status
  • Time: Jan. 25, 2023, 10:50 a.m.
    Status: Monitoring
    Update: We have identified a recent change to WAN as the underlying cause, and have taken steps to roll back this change. Our telemetry shows consistent signs of recovery from 09:45 UTC onwards across multiple regions and services. Most customers should now see full recovery as WAN networking has recovered fully. We are working to monitor and ensure full recovery for services that were impacted. The next update will be in 30 minutes or as soon as we have further information. This message was last updated at 10:28 UTC on 25 January 2023 https://status.azure.com/en-gb/status
  • Time: Jan. 25, 2023, 9:31 a.m.
    Status: Investigating
    Update: Azure has advised there are networking issues in multiple regions and this might affect customers. This impacts connectivity between clients on the internet to Azure, as well as connectivity between services in datacenters, as well as ExpressRoute connections. The issue is causing impact in waves, peaking approximately every 30 minutes. You can find more details on https://status.azure.com/en-gb/status

Updates:

  • Time: Jan. 25, 2023, 11:49 a.m.
    Status: Resolved
    Update: Incident has been resolved for any more info please check out https://status.azure.com/en-gb/status
  • Time: Jan. 25, 2023, 10:50 a.m.
    Status: Monitoring
    Update: We have identified a recent change to WAN as the underlying cause, and have taken steps to roll back this change. Our telemetry shows consistent signs of recovery from 09:45 UTC onwards across multiple regions and services. Most customers should now see full recovery as WAN networking has recovered fully. We are working to monitor and ensure full recovery for services that were impacted. The next update will be in 30 minutes or as soon as we have further information. This message was last updated at 10:28 UTC on 25 January 2023 https://status.azure.com/en-gb/status
  • Time: Jan. 25, 2023, 9:31 a.m.
    Status: Investigating
    Update: Azure has advised there are networking issues in multiple regions and this might affect customers. This impacts connectivity between clients on the internet to Azure, as well as connectivity between services in datacenters, as well as ExpressRoute connections. The issue is causing impact in waves, peaking approximately every 30 minutes. You can find more details on https://status.azure.com/en-gb/status

Updates:

  • Time: Feb. 8, 2023, 3:27 a.m.
    Status: Postmortem
    Update: # Incident RCA 2023-01-23: Delayed writes and reads in eu-central-1 # **Summary** Beginning in early January, a new customer workload began periodically causing high TTBR in eu-central-1. This workload was characterized by a few \(< 10/day\) large spikes of writes, sometimes upwards of 50-60MiB/s. Under normal circumstances, this would have posed little issue for a cluster of this size, however, these spikes consisted primarily of “upserts”--modifications to existing points. The process of merging the existing point values and those newly written during a spike of write traffic was highly CPU intensive, resulting in all replicas of the most impacted storage partitions falling behind on the stream of new writes, sometimes by over an hour. After each spike of write traffic, the most severely impacted partitions would take several hours to recover. Frequently, spikes during UTC business hours were separated by as little as one hour, further adding to the needed time to recover. The engineering team identified the customer in question and attempted to mitigate the impact of these spikes of write traffic by significantly increasing the provisioned resources for each storage partition in this cluster. After these efforts proved to be unsuccessful, we worked with this customer to pause this workload. Going forward, we will be working with this customer to tune their workload.
  • Time: Feb. 8, 2023, 3:27 a.m.
    Status: Postmortem
    Update: # Incident RCA 2023-01-23: Delayed writes and reads in eu-central-1 # **Summary** Beginning in early January, a new customer workload began periodically causing high TTBR in eu-central-1. This workload was characterized by a few \(< 10/day\) large spikes of writes, sometimes upwards of 50-60MiB/s. Under normal circumstances, this would have posed little issue for a cluster of this size, however, these spikes consisted primarily of “upserts”--modifications to existing points. The process of merging the existing point values and those newly written during a spike of write traffic was highly CPU intensive, resulting in all replicas of the most impacted storage partitions falling behind on the stream of new writes, sometimes by over an hour. After each spike of write traffic, the most severely impacted partitions would take several hours to recover. Frequently, spikes during UTC business hours were separated by as little as one hour, further adding to the needed time to recover. The engineering team identified the customer in question and attempted to mitigate the impact of these spikes of write traffic by significantly increasing the provisioned resources for each storage partition in this cluster. After these efforts proved to be unsuccessful, we worked with this customer to pause this workload. Going forward, we will be working with this customer to tune their workload.
  • Time: Feb. 1, 2023, 6:38 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 1, 2023, 6:38 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 27, 2023, 7:45 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Jan. 27, 2023, 7:45 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Jan. 26, 2023, 10:33 p.m.
    Status: Monitoring
    Update: The amount of time taken for writes to become readable has returned to the normal operating level. We will continue to monitor and update.
  • Time: Jan. 26, 2023, 10:33 p.m.
    Status: Monitoring
    Update: The amount of time taken for writes to become readable has returned to the normal operating level. We will continue to monitor and update.
  • Time: Jan. 26, 2023, 7:53 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Jan. 26, 2023, 7:53 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Jan. 26, 2023, 6:38 p.m.
    Status: Monitoring
    Update: The region is currently experiencing elevated times for written information to become queryable along with elevated query run times. All written information is still being safely queued. We are working to minimize disruptions and we will continue to update as the situation evolves.
  • Time: Jan. 26, 2023, 6:38 p.m.
    Status: Monitoring
    Update: The region is currently experiencing elevated times for written information to become queryable along with elevated query run times. All written information is still being safely queued. We are working to minimize disruptions and we will continue to update as the situation evolves.
  • Time: Jan. 26, 2023, 3:06 a.m.
    Status: Monitoring
    Update: The storage engine has completed processing the bursted traffic. Writes are now queryable within the normal time ranges. Our team will continue to monitor.
  • Time: Jan. 26, 2023, 3:06 a.m.
    Status: Monitoring
    Update: The storage engine has completed processing the bursted traffic. Writes are now queryable within the normal time ranges. Our team will continue to monitor.
  • Time: Jan. 26, 2023, 2:29 a.m.
    Status: Identified
    Update: The region received another burst of write traffic causing backup into the queueing system. Heavily bursting traffic has now been limited on a per organization basis. All organizations impacted by this limitation have been notified. The storage system is currently processing the bursted traffic. We will update here as the storage engine completes this processing.
  • Time: Jan. 26, 2023, 2:29 a.m.
    Status: Identified
    Update: The region received another burst of write traffic causing backup into the queueing system. Heavily bursting traffic has now been limited on a per organization basis. All organizations impacted by this limitation have been notified. The storage system is currently processing the bursted traffic. We will update here as the storage engine completes this processing.
  • Time: Jan. 26, 2023, 1:21 a.m.
    Status: Investigating
    Update: We are seeing a return of the delayed reads and writes issue from a few hours ago. Our team is actively investigating.
  • Time: Jan. 25, 2023, 7:53 p.m.
    Status: Monitoring
    Update: We have identified the primary contributing factor for performance degradation (delayed writes and subsequent temporary read discrepancies). The impacted region has been receiving a large burst of writes twice daily which has saturated the storage layer. All writes to this region have been successfully recorded within our queuing system but are taking much longer than expected to become queryable. In response to this event, we have increased the resources available to the storage system. In addition, we have paused all tertiary background processes in the region to expedite recovery. We will continue to provide updates as the storage system recovers and will provide a complete root cause analysis when this incident has been resolved.
  • Time: Jan. 25, 2023, 6:12 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 6:12 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 4:06 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 4:06 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 2:45 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 2:45 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 1:50 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 1:50 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 9:29 a.m.
    Status: Identified
    Update: We have deployed some minor updates to the cluster but still continue to investigate the issue
  • Time: Jan. 25, 2023, 9:29 a.m.
    Status: Identified
    Update: We have deployed some minor updates to the cluster but still continue to investigate the issue
  • Time: Jan. 25, 2023, 7:32 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 7:32 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 5:53 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 5:53 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 3:44 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 1:25 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 25, 2023, 1:25 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 24, 2023, 11:43 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 24, 2023, 11:43 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Jan. 24, 2023, 9 p.m.
    Status: Identified
    Update: We are continuing to work on this issue and a fix is being implemented.
  • Time: Jan. 24, 2023, 9 p.m.
    Status: Identified
    Update: We are continuing to work on this issue and a fix is being implemented.
  • Time: Jan. 24, 2023, 7:50 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is still being implemented.
  • Time: Jan. 24, 2023, 7:50 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is still being implemented.
  • Time: Jan. 24, 2023, 5:41 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Jan. 24, 2023, 5:41 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Jan. 24, 2023, 3:57 p.m.
    Status: Investigating
    Update: The AWS regions specified are experiencing delayed write/query operations and intermittent query failures. We are continuing to investigate the issue.
  • Time: Jan. 24, 2023, 3:57 p.m.
    Status: Investigating
    Update: The AWS regions specified are experiencing delayed write/query operations and intermittent query failures. We are continuing to investigate the issue.
  • Time: Jan. 24, 2023, 1:50 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Jan. 24, 2023, 1:50 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Jan. 24, 2023, 1:11 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: Jan. 24, 2023, 1:11 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Jan. 23, 2023, 6:14 p.m.
    Status: Resolved
    Update: This incident has been resolved, and the delete operations have been re-enabled.
  • Time: Jan. 23, 2023, 4:37 p.m.
    Status: Monitoring
    Update: Delete operations have temporarily been suspended, the delay is decreasing steadily. We will continue to monitor the issue and provide further updates
  • Time: Jan. 23, 2023, 1:57 p.m.
    Status: Identified
    Update: Delete operations have temporarily been suspended whilst the team investigate the root cause, customers will not currently be able to run predicate based deletes in this region.
  • Time: Jan. 23, 2023, 12:32 p.m.
    Status: Identified
    Update: The issue has been identified and the team is working on a fix.
  • Time: Jan. 23, 2023, 11:38 a.m.
    Status: Investigating
    Update: We are seeing the writes and query performance delayed, but there are no loss in writes. The team is investigating the issue and will we will provide further updates soon

Updates:

  • Time: Jan. 23, 2023, 6:14 p.m.
    Status: Resolved
    Update: This incident has been resolved, and the delete operations have been re-enabled.
  • Time: Jan. 23, 2023, 4:37 p.m.
    Status: Monitoring
    Update: Delete operations have temporarily been suspended, the delay is decreasing steadily. We will continue to monitor the issue and provide further updates
  • Time: Jan. 23, 2023, 1:57 p.m.
    Status: Identified
    Update: Delete operations have temporarily been suspended whilst the team investigate the root cause, customers will not currently be able to run predicate based deletes in this region.
  • Time: Jan. 23, 2023, 12:32 p.m.
    Status: Identified
    Update: The issue has been identified and the team is working on a fix.
  • Time: Jan. 23, 2023, 11:38 a.m.
    Status: Investigating
    Update: We are seeing the writes and query performance delayed, but there are no loss in writes. The team is investigating the issue and will we will provide further updates soon

Check the status of similar companies and alternatives to InfluxDB

Smartsheet
Smartsheet

Systems Active

ESS (Public)
ESS (Public)

Systems Active

ESS (Public)
ESS (Public)

Systems Active

Cloudera
Cloudera

Systems Active

New Relic
New Relic

Systems Active

Boomi
Boomi

Systems Active

AppsFlyer
AppsFlyer

Systems Active

Imperva
Imperva

Systems Active

Bazaarvoice
Bazaarvoice

Issues Detected

Optimizely
Optimizely

Systems Active

Electric
Electric

Systems Active

ABBYY
ABBYY

Issues Detected

Frequently Asked Questions - InfluxDB

Is there a InfluxDB outage?
The current status of InfluxDB is: Systems Active
Where can I find the official status page of InfluxDB?
The official status page for InfluxDB is here
How can I get notified if InfluxDB is down or experiencing an outage?
To get notified of any status changes to InfluxDB, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of InfluxDB every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does InfluxDB do?
Efficiently store and access time series data in a specialized database designed for speed, available in cloud, on-premises, or edge environments.

Start monitoring now!

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.

Get Started for Free