Skip to content

Outage tracker / Honeycomb

Is Honeycomb down?

I'm having a problem

Partially downchecked 12 minutes ago

Part of Honeycomb is not answering our probes: its web surface from South America. Its sign-in surface, the surface we treat as the service's own, answered from every region we check.

As of Sep 21, 2026, 11:32 AM UTC, Honeycomb answered RealUptime's probes in all 10 regions that returned a reading. Our South America probe reached some of its surfaces and not others.

Functional endpoints verified

We have an outage open for Honeycomb, 5h 32m so far.

Last outage: 3h 15m on Sep 13, 2026 (web surface, from South America and Australia, intermittent).

our independent probeslive · checked Sep 21, 2026, 11:32 AM UTC
US-East168 msOperational
US-West738 msOperational
Europe438 msOperational
Asia-Pacific1024 msOperational
US-Central420 msOperational
Canada657 msOperational
UK399 msOperational
Southeast Asia2031 msOperational
Australia1338 msOperational
South America999 msPartially down
their status pagetheir claim, not our reading

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

from Honeycomb's own status page, checked Sep 21, 2026, 11:14 AM UTC
Our probes are seeing errors from Honeycomb right now. Honeycomb's own status page currently reports All Systems Operational. We are not able to explain the difference. It's possible the issue is limited to the specific request path we check, or that their status page has not updated yet.

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
530msp95 · 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-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 492ms2026-09-06 UTC: p95 436ms2026-09-07 UTC: p95 386ms2026-09-08 UTC: p95 459ms2026-09-09 UTC: p95 462ms2026-09-10 UTC: p95 463ms2026-09-11 UTC: p95 476ms2026-09-12 UTC: p95 479ms2026-09-13 UTC: p95 425ms2026-09-14 UTC: p95 707ms2026-09-15 UTC: p95 492ms2026-09-16 UTC: p95 515ms2026-09-17 UTC: p95 531ms2026-09-18 UTC: p95 572ms2026-09-19 UTC: p95 456ms2026-09-20 UTC: p95 498ms2026-09-21 UTC: p95 530ms
Aug 23Sep 6Sep 21
US-West
830msp95 · 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-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 624ms2026-09-06 UTC: p95 692ms2026-09-07 UTC: p95 637ms2026-09-08 UTC: p95 575ms2026-09-09 UTC: p95 525ms2026-09-10 UTC: p95 562ms2026-09-11 UTC: p95 637ms2026-09-12 UTC: p95 630ms2026-09-13 UTC: p95 609ms2026-09-14 UTC: p95 701ms2026-09-15 UTC: p95 893ms2026-09-16 UTC: p95 813ms2026-09-17 UTC: p95 812ms2026-09-18 UTC: p95 870ms2026-09-19 UTC: p95 866ms2026-09-20 UTC: p95 938ms2026-09-21 UTC: p95 830ms
Aug 23Sep 6Sep 21
Europe
459msp95 · 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-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 592ms2026-09-06 UTC: p95 590ms2026-09-07 UTC: p95 627ms2026-09-08 UTC: p95 750ms2026-09-09 UTC: p95 767ms2026-09-10 UTC: p95 797ms2026-09-11 UTC: p95 755ms2026-09-12 UTC: p95 710ms2026-09-13 UTC: p95 713ms2026-09-14 UTC: p95 975ms2026-09-15 UTC: p95 930ms2026-09-16 UTC: p95 795ms2026-09-17 UTC: p95 677ms2026-09-18 UTC: p95 669ms2026-09-19 UTC: p95 446ms2026-09-20 UTC: p95 563ms2026-09-21 UTC: p95 459ms
Aug 23Sep 6Sep 21
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-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.5s2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s
Aug 23Sep 6Sep 21
US-Central
518msp95 · 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 603ms2026-09-06 UTC: p95 604ms2026-09-07 UTC: p95 540ms2026-09-08 UTC: p95 530ms2026-09-09 UTC: p95 691ms2026-09-10 UTC: p95 526ms2026-09-11 UTC: p95 738ms2026-09-12 UTC: p95 727ms2026-09-13 UTC: p95 695ms2026-09-14 UTC: p95 654ms2026-09-15 UTC: p95 628ms2026-09-16 UTC: p95 672ms2026-09-17 UTC: p95 630ms2026-09-18 UTC: p95 644ms2026-09-19 UTC: p95 658ms2026-09-20 UTC: p95 755ms2026-09-21 UTC: p95 518ms
Aug 23Sep 6Sep 21
Canada
639msp95 · 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 593ms2026-09-06 UTC: p95 595ms2026-09-07 UTC: p95 658ms2026-09-08 UTC: p95 570ms2026-09-09 UTC: p95 595ms2026-09-10 UTC: p95 761ms2026-09-11 UTC: p95 638ms2026-09-12 UTC: p95 660ms2026-09-13 UTC: p95 591ms2026-09-14 UTC: p95 601ms2026-09-15 UTC: p95 720ms2026-09-16 UTC: p95 606ms2026-09-17 UTC: p95 582ms2026-09-18 UTC: p95 608ms2026-09-19 UTC: p95 542ms2026-09-20 UTC: p95 626ms2026-09-21 UTC: p95 639ms
Aug 23Sep 6Sep 21
UK
460msp95 · 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 546ms2026-09-06 UTC: p95 552ms2026-09-07 UTC: p95 515ms2026-09-08 UTC: p95 505ms2026-09-09 UTC: p95 513ms2026-09-10 UTC: p95 496ms2026-09-11 UTC: p95 473ms2026-09-12 UTC: p95 467ms2026-09-13 UTC: p95 480ms2026-09-14 UTC: p95 498ms2026-09-15 UTC: p95 542ms2026-09-16 UTC: p95 529ms2026-09-17 UTC: p95 495ms2026-09-18 UTC: p95 508ms2026-09-19 UTC: p95 525ms2026-09-20 UTC: p95 520ms2026-09-21 UTC: p95 460ms
Aug 23Sep 6Sep 21
Southeast Asia
3.3sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. 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.9s2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 2.1s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 2.2s2026-09-14 UTC: p95 1.9s2026-09-15 UTC: p95 2.1s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 3.3s
Aug 23Sep 6Sep 21
Australia
1.8sp95 · 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.8s2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.9s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.8s
Aug 23Sep 6Sep 21
South America
1.4sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. 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 970ms2026-09-06 UTC: p95 939ms2026-09-07 UTC: p95 937ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.4s
Aug 23Sep 6Sep 21

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: Down
  • 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.

Open incident

Sep 21, 2026, 6:12 AM UTCOngoing
single regionintermittent
open for 5h 32m so farSouth America: failing from Sep 21, 2026, 6:12 AM UTC, still failing

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 168msstatus code: 401checked: Sep 21, 2026, 11:19 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: 738msstatus code: 401checked: Sep 21, 2026, 11:15 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: 420msstatus code: 401checked: Sep 21, 2026, 11:12 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: 657msstatus code: 401checked: Sep 21, 2026, 11:17 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
    Partially downlatency: 999msstatus code: 401checked: Sep 21, 2026, 11:12 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: 438msstatus code: 401checked: Sep 21, 2026, 11:31 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: 399msstatus code: 401checked: Sep 21, 2026, 11:17 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: 1024msstatus code: 401checked: Sep 21, 2026, 11:15 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: 2031msstatus code: 401checked: Sep 21, 2026, 11:13 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: 1338msstatus code: 401checked: Sep 21, 2026, 11:32 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

Outage, 3h 15mmeasured by our probes · South America and Australia2026-09-13
Partial outage, 2h 37mmeasured by our probes · South America2026-09-12
Partial outage, 31mmeasured by our probes · South America2026-09-06
Partial outage, 1hmeasured by our probes · Australia2026-09-06
Partial outage, 7h 59mmeasured by our probes · Australia2026-09-05
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

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

Below your target

We measured 3h 15m of downtime for Honeycomb over the last 30 days, which is 99.5478% uptime by our reading. A 99.9% target allows 43 minutes over that period.

That is 2h 32m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

Separately, we measured 17h 38m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

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.