Skip to content

Outage tracker / Honeycomb

Is Honeycomb down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Honeycomb from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Honeycomb (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:05 AM UTC
US-East455 msOperational
US-West285 msOperational
Europe436 msOperational
Asia-Pacific981 msOperational
US-Central445 msOperational
Canada272 msOperational
UK521 msOperational
Southeast Asia1306 msOperational
Australia1065 msOperational
South America782 msOperational
their status pagetheir claim, not our reading

Honeycomb reports: All systems operational (“All Systems Operational”)

from Honeycomb's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Honeycomb's own status page agree: both show Honeycomb as reachable right now.

Honeycomb's own component breakdown, as they publish it

  • api.honeycomb.io - US1 Event IngestOperational
  • ui.honeycomb.io - US1 QueryingOperational
  • ui.honeycomb.io - US1 App InterfaceOperational
  • ui.honeycomb.io - US1 Trigger & SLO AlertingOperational
  • ui.honeycomb.io - US1 Activity LogOperational
  • ui.honeycomb.io - US1 EnhanceOperational
  • api.eu1.honeycomb.io - EU1 Event IngestOperational
  • ui.eu1.honeycomb.io - EU1 App InterfaceOperational
  • ui.eu1.honeycomb.io - EU1 QueryingOperational
  • ui.eu1.honeycomb.io - EU1 Trigger & SLO AlertingOperational
  • ui.eu1.honeycomb.io - EU1 Activity LogOperational
  • ui.eu1.honeycomb.io - EU1 EnhanceOperational
  • www.honeycomb.ioOperational
  • SandboxOperational

These are Honeycomb's components, named and scored by Honeycomb. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Honeycomb's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Honeycomb response time, by region

US-East
966msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 318ms2026-08-23 UTC: p95 229ms2026-08-24 UTC: p95 250ms2026-08-25 UTC: p95 257ms2026-08-26 UTC: p95 299ms2026-08-27 UTC: p95 603ms2026-08-28 UTC: p95 596ms2026-08-29 UTC: p95 547ms2026-08-30 UTC: p95 504ms2026-08-31 UTC: p95 623ms2026-09-01 UTC: p95 748ms2026-09-02 UTC: p95 565ms2026-09-03 UTC: p95 538ms2026-09-04 UTC: p95 669ms2026-09-05 UTC: p95 966ms
Aug 7Aug 21Sep 5
US-West
290msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 366ms2026-08-23 UTC: p95 499ms2026-08-24 UTC: p95 602ms2026-08-25 UTC: p95 752ms2026-08-26 UTC: p95 922ms2026-08-27 UTC: p95 639ms2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 709ms2026-08-30 UTC: p95 634ms2026-08-31 UTC: p95 704ms2026-09-01 UTC: p95 731ms2026-09-02 UTC: p95 613ms2026-09-03 UTC: p95 810ms2026-09-04 UTC: p95 484ms2026-09-05 UTC: p95 290ms
Aug 7Aug 21Sep 5
Europe
453msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 468ms2026-08-23 UTC: p95 620ms2026-08-24 UTC: p95 999ms2026-08-25 UTC: p95 729ms2026-08-26 UTC: p95 623ms2026-08-27 UTC: p95 754ms2026-08-28 UTC: p95 743ms2026-08-29 UTC: p95 673ms2026-08-30 UTC: p95 551ms2026-08-31 UTC: p95 624ms2026-09-01 UTC: p95 577ms2026-09-02 UTC: p95 688ms2026-09-03 UTC: p95 895ms2026-09-04 UTC: p95 861ms2026-09-05 UTC: p95 453ms
Aug 7Aug 21Sep 5
Asia-Pacific
1.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 978ms2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.3s2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 1.5s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.4s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.5s2026-09-02 UTC: p95 2.1s2026-09-03 UTC: p95 2.2s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
US-Central
491msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 616ms2026-09-04 UTC: p95 649ms2026-09-05 UTC: p95 491ms
Aug 7Aug 21Sep 5
Canada
490msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 633ms2026-09-04 UTC: p95 598ms2026-09-05 UTC: p95 490ms
Aug 7Aug 21Sep 5
UK
529msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 685ms2026-09-04 UTC: p95 585ms2026-09-05 UTC: p95 529ms
Aug 7Aug 21Sep 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 1.6s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
Australia
1.5sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 1.8s2026-09-05 UTC: p95 1.5s
Aug 7Aug 21Sep 5
South America
962msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 962ms
Aug 7Aug 21Sep 5

Is it Honeycomb, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Honeycomb -- it cannot diagnose Honeycomb's own systems.

What we measured, function by function

Honeycomb answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 455msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Honeycomb normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 285msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Honeycomb normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 445msstatus code: 401checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Honeycomb normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 272msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Honeycomb normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 782msstatus code: 401checked: Sep 5, 2026, 1:56 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Honeycomb normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 436msstatus code: 401checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Honeycomb normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 521msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Honeycomb normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 981msstatus code: 401checked: Sep 5, 2026, 1:45 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Honeycomb normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1306msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Honeycomb normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1065msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Honeycomb normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Honeycomb, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Honeycomb yet, which is not evidence that nothing is wrong.

Recent outages

Canvas not loading, 38mdeclared on their status page2026-08-21
US1 cold query outage, 7h 34mdeclared on their status page2026-08-10
Querying issues, 1mdeclared on their status page2026-07-31
Triggers intermittently failing in EU region, 29h 17mdeclared on their status page2026-07-27
honeycomb.io marketing website not working, 6h 21mdeclared on their status page2026-07-02
Activity Log delayed in US, 2h 40mdeclared on their status page2026-06-29
Ingest outage in EU, 2h 32mdeclared on their status page2026-06-25
Ingest Outage in US and EU, 51mdeclared on their status page2026-06-24

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Honeycomb since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Honeycomb covering any window you pick, with our measurements and Honeycomb's own claim at the time, side by side.

Full availability history for Honeycomb: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Honeycomb, and again when they can reach it again. That is our own measurement from ten regions, not Honeycomb's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Honeycomb uptime measured by RealUptimeLive, from this page's own readings.
[![Honeycomb uptime measured by RealUptime](https://realuptime.io/outages/honeycomb/badge.svg?days=30)](https://realuptime.io/outages/honeycomb)
<a href="https://realuptime.io/outages/honeycomb"><img src="https://realuptime.io/outages/honeycomb/badge.svg?days=30" alt="Honeycomb uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Honeycomb's SLA implies, from our measurement

At or above your target

We measured none of downtime for Honeycomb over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Honeycomb's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.honeycomb.io/1/auth
secondary
https://www.honeycomb.io/
secondary
https://status.honeycomb.io/api/v2/status.json
RealUptime is not affiliated with Honeycomb; the name identifies what we measured, and nothing here speaks for Honeycomb's own team. We send a single web request to Honeycomb from 10 regions on our own schedule and time the response. We do not see inside Honeycomb's systems, do not use an account or real transaction, and are not the same signal Honeycomb's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Honeycomb is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.