Honeycomb Status: How to Check If Honeycomb Is Down Right Now (2026)
Updated July 2026 · 6 min read · By API Status Check
Quick Answer: Check Honeycomb Status Now
Honeycomb is an observability platform built around high-cardinality event data and distributed tracing, commonly fed via OpenTelemetry (OTel). Engineering teams query Honeycomb to debug production issues by slicing traces on arbitrary fields rather than pre-aggregated metrics. Like Datadog, Honeycomb's ingestion pipeline and query engine are separate systems — one can be healthy while the other is degraded.
How Data Reaches Honeycomb
- • OpenTelemetry SDK/collector exports spans via OTLP
- • Or events sent directly to the Honeycomb Events API
- • Ingested into a dataset scoped by your API key
- • Check status.honeycomb.io for ingestion incidents
- • Query Builder / UI issues BubbleUp and trace queries
- • Query engine scans ingested event data on demand
- • Triggers and SLOs run scheduled background queries
- • Query slowness ≠ data loss — ingestion is separate
Understanding Honeycomb's Status Page (status.honeycomb.io)
Honeycomb operates status.honeycomb.io to track infrastructure components. Because Honeycomb separates the write path (ingestion) from the read path (query engine), degradation in one doesn't necessarily affect the other.
Event Ingestion (OTLP/API)
Accepts spans and events from OpenTelemetry exporters and the direct Events API. This is the most critical component — if degraded, new telemetry from your services may be delayed or dropped depending on your exporter's retry and buffering behavior.
Query Engine
Executes queries against ingested event data, including BubbleUp analysis and trace waterfalls. Query slowness on high-cardinality or wide time-range queries can be normal load behavior rather than an incident.
Web UI
The Honeycomb dashboard used to build queries, view traces, and manage boards. A slow or unavailable UI doesn't mean data isn't being ingested — the API and ingestion pipeline can remain healthy independently.
Triggers & SLOs
Scheduled queries that power alerting (Triggers) and service level objective tracking (SLOs). If this component is degraded, alerts may fire late or SLO burn-rate calculations may lag behind real-time data.
Honeycomb API
The management and query API used for programmatic access, Terraform provider operations, and CI/CD integrations. Separate from the OTLP ingestion endpoint used by exporters.
Refinery (self-managed)
For teams running Honeycomb's Refinery sampling proxy themselves, this component is entirely your responsibility to monitor — Refinery issues won't show on Honeycomb's own status page since it runs on your infrastructure.
Diagnosing Honeycomb Ingestion Issues
Most "missing traces" reports trace back to exporter misconfiguration rather than a real Honeycomb outage. Work through these checks before assuming an incident.
Honeycomb Diagnostic Checklist
# 1. Send a test event directly to the Events API
curl https://api.honeycomb.io/1/events/test-dataset \
-H "X-Honeycomb-Team: $HONEYCOMB_API_KEY" \
-d '{"test": true}'
# Should return 200/202
# 2. Enable OTel SDK debug logging
OTEL_LOG_LEVEL=debug (or SDK-specific equivalent)
# Confirms exporter is attempting and succeeding at export
# 3. Verify the exporter endpoint and headers
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io
OTEL_EXPORTER_OTLP_HEADERS=x-honeycomb-team=$API_KEY
# 4. Check for a collector or Refinery bottleneck
Inspect your OTel Collector or Refinery logs for export errors
# 5. Confirm the dataset name matches your query
Data can be ingesting into a different dataset than you're viewing
Common Honeycomb Failure Causes That Aren't Outages
- 🔴 Wrong or expired API key: An invalid x-honeycomb-team header causes silent 401 rejections in many OTel exporters unless debug logging is enabled — data simply never arrives with no obvious error in your app logs.
- 🔴 Dataset name mismatch: Team-based API keys route data to a dataset name specified in the exporter config. If that name doesn't match what you're querying in the UI, the data is arriving — just in a dataset you're not looking at.
- 🔴 Refinery sampling drops: If you're running Refinery for tail-based sampling, its sampling rules may be dropping more traces than expected. This looks like missing data but is a configuration choice, not an ingestion failure.
- 🔴 Collector export queue backpressure: A local OpenTelemetry Collector with a full export queue will drop or delay spans under high throughput. Check collector metrics for dropped-span counters.
- 🔴 High-cardinality query timeouts: Extremely high-cardinality BubbleUp queries over long time windows can legitimately time out under normal system load — this is a query cost issue, not an outage.
Monitor your OTel Collector and exporters independently
Honeycomb's own status page can't see problems in your local collector or network path. Better Stack can watch your collector's health endpoint and alert before telemetry silently stops flowing. Free plan available.
Try Better Stack Free →What Honeycomb Status Colors Mean
Common Honeycomb Issues and What They Mean
"Traces missing spans or showing broken parent-child links"Usually a context propagation issue in your instrumentation, not an ingestion problem — verify trace context headers (traceparent) are being passed correctly across service boundaries, especially through async queues or message brokers.""401 Unauthorized" from the OTLP exporter"Your Honeycomb API key is invalid, expired, or missing the required x-honeycomb-team header. Regenerate the key in Honeycomb's Environment settings and confirm it's set in your exporter's environment variables, not hardcoded in a stale config."Query returns "no data" for a time range you know has events"Check that you're querying the correct dataset and environment — Honeycomb scopes data by both. Also verify your local clock and the query's timezone settings aren't offsetting the window away from when events actually arrived."SLO burn-rate alerts firing incorrectly"SLO calculations depend on Triggers running on schedule. Check status.honeycomb.io for a Triggers & SLOs incident. If status is green, review whether a recent deploy changed the qualifying event volume feeding the SLO's underlying query."Honeycomb UI extremely slow to load boards"Boards with many complex queries render each query independently. If the Query Engine component shows degraded status, board load times will reflect that even though the underlying data is intact.Frequently Asked Questions
Where is the official Honeycomb status page?
Honeycomb's official status page is status.honeycomb.io. It covers Event Ingestion (OTLP/API), Query Engine, Web UI, Triggers & SLOs, and the management API. Subscribe there for email or RSS notifications on incidents.
If Honeycomb ingestion was down, was my telemetry data lost?
It depends on your exporter and collector configuration. Most OpenTelemetry exporters and collectors have local retry buffers that hold spans temporarily during brief outages and retry once ingestion recovers. Extended outages, or exporters without adequate buffering, can result in permanent data loss for that window.
Why does my query say 'no data' even though status.honeycomb.io shows all green?
This is almost always a query scoping issue rather than an outage — wrong dataset, wrong environment, or a time range/timezone mismatch. Double-check which dataset your API key routes data into versus which dataset you're querying in the UI.
How is Honeycomb different from Datadog for outage purposes?
Datadog bundles metrics, logs, and traces with pre-aggregation, while Honeycomb is built around raw high-cardinality event data queried on demand via OpenTelemetry. Because Honeycomb's query engine computes results at query time rather than pre-aggregating, query-time degradation is more visible to users than in metrics-first platforms.
How do I get alerts when Honeycomb goes down?
Subscribe to updates at status.honeycomb.io for official incident notifications. Since Honeycomb can't monitor your own collectors or exporters, also set up independent external monitoring on any self-hosted OTel Collector health endpoints in your pipeline.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Honeycomb goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Honeycomb + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial