Foxglove - Notice history

On July 29, 2026, Foxglove customers experienced a full API outage for approximately 90 minutes, during which the dashboard, uploads, data browsing, and API access were all unavailable. The cause was a sudden, large spike in traffic to a specific endpoint in one of our backend services, which exhausted database connections and took our API servers offline. No customer data was lost. We’ve shipped fixes to handle traffic spikes like this more gracefully, and identified follow-up work to prevent similar overload in the future.

On May 19–20, 2026, some Foxglove customers using bring-your-own-storage (BYOS) data platforms experienced intermittent disruptions to indexing, querying, and streaming across US and EU regions. The cause was a Kubernetes configuration change that unintentionally deleted resources during a deployment, plus a downstream DNS misconfiguration after restoration. No customer data was lost. We've shipped fixes and identified follow-up work to consolidate our infrastructure-as-code ownership and improve recovery for similar issues in the future.

We've found and shipped a permanent fix for the underlying infrastructure misconfiguration.

The mitigation has succeeded. We are continuing to monitor and working on a permanent fix.

We've identified a mitigation and are implementing it.