Skip to main content
Vendor reliability

Vendor record

Honeycomb

Vendor reports Operational

Checked

Front door check counts and Honeycomb’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Honeycomb endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.honeycomb.io
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Honeycomb product, region or your app worked.

How we count front door checks

Honeycomb says

Incident posts from Honeycomb’s status page, with its titles, impact levels and times. They say what Honeycomb chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

20

incidents Honeycomb posted, last 1 year

Median recorded duration: 1h 37m. From 20 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Canvas not loading

    Minor

    Started, per Honeycomb

    Closed in our record(43m)

    Honeycomb’s post
  • US1 cold query outage

    Minor

    Started, per Honeycomb

    Closed in our record(7h 38m)

    Honeycomb’s post
  • Triggers intermittently failing in EU region

    Minor

    Started, per Honeycomb

    Closed in our record(1d 5h)

    Honeycomb’s post
  • honeycomb.io marketing website not working

    Major

    Started, per Honeycomb

    Closed in our record(6h 24m)

    Honeycomb’s post
  • Activity Log delayed in US

    Minor

    Started, per Honeycomb

    Closed in our record(2h 43m)

    Honeycomb’s post
15 older records
  • Ingest outage in EU

    Minor

    Started, per Honeycomb

    Closed in our record(2h 40m)

    Honeycomb’s post
  • Delayed ingest in US and EU

    Major

    Started, per Honeycomb

    Closed in our record(56m)

    Honeycomb’s post
  • MCP tool access degraded

    Minor

    Started, per Honeycomb

    Closed in our record(45m)

    Honeycomb’s post
  • Querying Issues

    Minor

    Started, per Honeycomb

    Closed in our record(7h 19m)

    Honeycomb’s post
  • Querying Issues in EU

    Minor

    Started, per Honeycomb

    Closed in our record(38m)

    Honeycomb’s post
  • Delayed ingest in EU

    Minor

    Started, per Honeycomb

    Closed in our record(1h 11m)

    Honeycomb’s post
  • Canvas UI issues

    Minor

    Started, per Honeycomb

    Closed in our record(1h 12m)

    Honeycomb’s post
  • Investigating querying issues

    Minor

    Started, per Honeycomb

    Closed in our record(17h 27m)

    Honeycomb’s post
  • activity log for US instance is delayed

    Minor

    Started, per Honeycomb

    Closed in our record(3d 7h)

    Honeycomb’s post
  • Links in Slack triggers not working

    Not specified

    Started, per Honeycomb

    Closed in our record(1h 37m)

    Honeycomb’s post
  • Activity Log events interrupted for EU

    Major

    Started, per Honeycomb

    Closed in our record(14m)

    Honeycomb’s post
  • Activity Log ingest is delayed

    Minor

    Started, per Honeycomb

    Closed in our record(25m)

    Honeycomb’s post
  • Activity Log delayed ingest in EU

    Minor

    Started, per Honeycomb

    Closed in our record(1h 8m)

    Honeycomb’s post
  • Ingest issues for some customers

    Major

    Started, per Honeycomb

    Closed in our record(3h 43m)

    Honeycomb’s post
  • Activity log outage in production US

    Minor

    Started, per Honeycomb

    Closed in our record(1d 7h)

    Honeycomb’s post

Your code, your dependencies

See which of your code paths call Honeycomb

Connect GitHub or GitLab to find where your public or private repository uses Honeycomb. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Honeycomb status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · HoneycombStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/honeycomb?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Honeycomb status badge"></iframe>

Frequently Asked Questions

Is Honeycomb currently down?

Honeycomb's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Honeycomb last have an outage?

The most recent closed incident record began 56 days ago and spans 43 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Honeycomb?

No. CheckUpstream checks Honeycomb’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Honeycomb in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Honeycomb?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.