Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 28, 2026

  1. PostHogLog ingestion: processing delays

    We temporarily experienced some ingestion delays for logs in the EU cloud region, caused by updates we were applying to our ingestion pipeline. We paused these updates and log ingestion has resumed to normal latencies.

    Resolved

  2. ElevenLabsAgents - EU Residency

    We can confirm that the issue has been fixed and that the service is fully operational. Resolution time was 14:18 UTC We will post the RCA to the status page after the investigation.

    Resolved

  3. SnykSnyk CLI Scans Degraded

    No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

    Resolved

  4. Box[Medium] Issues with Box Notes

    After further monitoring, this incident is now considered resolved. The Box Note service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    Resolved

  5. Trigger.devRun logs are being dropped

    Logs are being fully ingested again. The issue was with the internal workers in our shared OpenTelemetry service. They became unhealthy but weren't rolled. We're looking into why and how to prevent this from happening again.

    Resolved

  6. Vonage APIVoice API degradation in EU region

    Vonage services have been fully restored following today's service interruption, where you may have experienced call failures in the EU region, which began at 2026-09-28 06:05:00 UTC. Full resolution has been confirmed effective 2026-09-28 06:54:00 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com OR https://www.vonage.com/support/

    Resolved

  7. BuildKiteIssues with webhook ingestion, GraphQL queries

    ## Service Impact On September 22, 2026, between 19:09 and 19:32 UTC, customers experienced failures ingesting webhooks and executing GraphQL queries. Some web application requests also failed or timed out. During this period, 2.0% of requests to our webhook ingestion endpoints and 20.3% of requests to our external GraphQL endpoint returned HTTP 500 errors. Webhook ingestion errors ceased by 19:30 UTC, and external GraphQL errors returned to background levels by 19:32 UTC. ## Incident Summary While investigating a separate API performance issue, we made a manual configuration change intended to rollback a routing change for one database proxy. The command instead changed the routing configuration for another database proxy, disrupting access to a database shard used internally by Buildkite. Some customer-facing operations search across all database shards to locate their shard, where routing information isn't available in the request. Those requests round robin through available shards, and could encounter the unavailable shard and wait for a database connection to time out. This extended the impact beyond our internal workloads. We reverted the incorrect configuration and verified that the database proxy had healthy endpoints and load-balancer targets. Two contributing factors allowed the change to cause an outage: the command was not independently checked before execution, and our infrastructure accepted a Service configuration that selected the wrong database proxy workload. The cross-shard lookup behaviour then allowed the disruption to affect requests for other customers. This configuration-change outage was separate from the API performance issue we were originally investigating. ## Changes we're making * Safer operational procedures: We have updated our runbook and introduced an explicit second person review requirement for manual production commands. * Automated safeguards: We’ve added validation to prevent database proxy routing changes from selecting the wrong workload. * Improved failure isolation: We’ve been working on an ongoing initiative to make database shard discovery more resilient, eliminating the remaining cases where an unavailable shard may impact requests for other customers.

    Resolved

Sep 27, 2026

  1. Confluent CloudMissing Metrics on Confluent Cloud

    Confluent Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27. Queries for recent metrics during this time duration may return incomplete or no data. This incident has been resolved as of 02:15 UTC.

    Resolved

Older incidents