Skip to main content
Honeycomb logo

Is Honeycomb Down?

No — Honeycomb is up

Reachable from all 8 checked regions

Average response time: 301ms

Last checked · checks run every 6 hours

Official status page: https://status.honeycomb.io

Honeycomb uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
395ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 57 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

57-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 27 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
278ms
DNS 25ms TCP 2ms TLS 7ms TTFB 264ms
arn
479ms
DNS 34ms TCP 1ms TLS 3ms TTFB 201ms
cdg
211ms
DNS 27ms TCP 1ms TLS 6ms TTFB 204ms
dfw
284ms
DNS 161ms TCP 1ms TLS 3ms TTFB 273ms
ewr
181ms
DNS 92ms TCP 2ms TLS 4ms TTFB 170ms
fra
336ms
DNS 19ms TCP 1ms TLS 4ms TTFB 167ms
gru
446ms
DNS 37ms TCP 1ms TLS 7ms TTFB 216ms
yyz
197ms
DNS 81ms TCP 9ms TLS 13ms TTFB 165ms

What Honeycomb does

Honeycomb is an observability platform built around wide events and distributed traces, used by engineering teams to ask open-ended questions about production rather than watch fixed dashboards. Services send telemetry through OpenTelemetry, and teams rely on it for SLOs, triggers and incident debugging. It runs separate US and EU environments, and an outage removes visibility exactly when it is most wanted.

What an outage looks like

Event ingest at api.honeycomb.io rejects or drops data, so recent time ranges look empty and a healthy service appears to have stopped serving traffic. Queries in the UI time out or return partial results. Triggers and SLO alerting do not fire, which is silent by nature. The EU1 and US1 environments fail independently, so only one may be affected.

What to do about it

status.honeycomb.io reports ingest, querying, the app interface and Trigger and SLO alerting separately for US1 and EU1, so start by confirming which environment and which function is affected. Treat a sudden drop to zero traffic as a Honeycomb ingest problem until proven otherwise, and fall back to another signal, logs or a load balancer's own metrics, before declaring an incident of your own.

Is it down for everyone, or just you?

If this page says Honeycomb is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Honeycomb outage FAQ

My traffic dropped to zero in Honeycomb. Is my service down?
Check ingest first. A sudden flat line across every service at once is far more often an ingest problem at Honeycomb than a simultaneous failure of everything you run. Confirm with a signal that does not pass through Honeycomb, such as a load balancer's own metrics or application logs, before waking anyone or declaring an incident.
Do triggers and SLO alerts still fire during a Honeycomb outage?
Not reliably, and that failure is silent. Trigger and SLO alerting is a separate component from ingest and querying, so alerts can stop while the UI works. Because a missing alert looks exactly like nothing being wrong, treat an alerting incident as a reason to watch systems manually rather than assuming quiet means healthy.
Is telemetry lost while ingest is unavailable?
Expect a gap. Whether telemetry rejected during an ingest incident survives depends on your own collector rather than on Honeycomb: an OpenTelemetry Collector with a persistent queue can hold and resend it, while a direct exporter with a short retry generally cannot. Decide on that buffering before an outage, because the setting cannot be applied retroactively.
Does an EU1 incident affect US1?
They are reported and operated separately. The status page lists ingest, querying, the app interface and alerting individually for US1 and EU1, so an EU environment problem leaves US teams unaffected. Check which environment your organisation sends data to, since the two use different hostnames and a team can easily end up watching the wrong one.

How we measure this

  • We request Honeycomb's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Honeycomb publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Honeycomb goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required