Skip to content

Outage tracker / Honeycomb

Is Honeycomb down?

I'm having a problem

Vendor reports no incidentWhat Honeycomb reports

Honeycomb reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:50 UTC.

Honeycomb's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 18 minutes ago

Our checks of Honeycomb pass from all 10 regions we check.

As of Oct 22, 2026, 9:35 PM UTC, RealUptime's checks of Honeycomb passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:35 PM UTC
US-East331 msChecks passing
US-West418 msChecks passing
Europe423 msChecks passing
Asia-Pacific874 msChecks passing
US-Central328 msChecks passing
Canada326 msChecks passing
UK403 msChecks passing
Southeast Asia1628 msChecks passing
Australia1227 msChecks passing
South America700 msChecks passing
their status pagetheir claim, not our reading

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

from Honeycomb's own status page, checked Oct 22, 2026, 9:33 PM UTC
Honeycomb's own status page shows no incident, and our checks of Honeycomb pass 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
1.2sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 556ms2026-09-24 UTC: p95 528ms2026-09-25 UTC: p95 504ms2026-09-26 UTC: p95 513ms2026-09-27 UTC: p95 528ms2026-09-28 UTC: p95 449ms2026-09-29 UTC: p95 551ms2026-09-30 UTC: p95 530ms2026-10-01 UTC: p95 716ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 444ms2026-10-04 UTC: p95 522ms2026-10-05 UTC: p95 524ms2026-10-06 UTC: p95 525ms2026-10-07 UTC: p95 533ms2026-10-08 UTC: p95 568ms2026-10-09 UTC: p95 594ms2026-10-10 UTC: p95 566ms2026-10-11 UTC: p95 538ms2026-10-12 UTC: p95 551ms2026-10-13 UTC: p95 549ms2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 434ms2026-10-16 UTC: p95 519ms2026-10-17 UTC: p95 848ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
US-West
2.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 884ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 896ms2026-09-27 UTC: p95 818ms2026-09-28 UTC: p95 912ms2026-09-29 UTC: p95 909ms2026-09-30 UTC: p95 872ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 784ms2026-10-03 UTC: p95 903ms2026-10-04 UTC: p95 880ms2026-10-05 UTC: p95 963ms2026-10-06 UTC: p95 858ms2026-10-07 UTC: p95 666ms2026-10-08 UTC: p95 686ms2026-10-09 UTC: p95 854ms2026-10-10 UTC: p95 697ms2026-10-11 UTC: p95 639ms2026-10-12 UTC: p95 739ms2026-10-13 UTC: p95 815ms2026-10-14 UTC: p95 904ms2026-10-15 UTC: p95 910ms2026-10-16 UTC: p95 763ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 950ms2026-10-21 UTC: p95 623ms2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 470ms2026-09-24 UTC: p95 562ms2026-09-25 UTC: p95 462ms2026-09-26 UTC: p95 458ms2026-09-27 UTC: p95 623ms2026-09-28 UTC: p95 476ms2026-09-29 UTC: p95 639ms2026-09-30 UTC: p95 495ms2026-10-01 UTC: p95 804ms2026-10-02 UTC: p95 858ms2026-10-03 UTC: p95 963ms2026-10-04 UTC: p95 780ms2026-10-05 UTC: p95 892ms2026-10-06 UTC: p95 842ms2026-10-07 UTC: p95 729ms2026-10-08 UTC: p95 694ms2026-10-09 UTC: p95 740ms2026-10-10 UTC: p95 641ms2026-10-11 UTC: p95 665ms2026-10-12 UTC: p95 639ms2026-10-13 UTC: p95 632ms2026-10-14 UTC: p95 475ms2026-10-15 UTC: p95 475ms2026-10-16 UTC: p95 591ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Asia-Pacific
2.2sp95 · 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-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.2s
Sep 23Oct 7Oct 22
US-Central
464msp95 · 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-23 UTC: p95 701ms2026-09-24 UTC: p95 668ms2026-09-25 UTC: p95 737ms2026-09-26 UTC: p95 655ms2026-09-27 UTC: p95 528ms2026-09-28 UTC: p95 688ms2026-09-29 UTC: p95 554ms2026-09-30 UTC: p95 635ms2026-10-01 UTC: p95 639ms2026-10-02 UTC: p95 624ms2026-10-03 UTC: p95 625ms2026-10-04 UTC: p95 730ms2026-10-05 UTC: p95 756ms2026-10-06 UTC: p95 718ms2026-10-07 UTC: p95 660ms2026-10-08 UTC: p95 582ms2026-10-09 UTC: p95 658ms2026-10-10 UTC: p95 633ms2026-10-11 UTC: p95 686ms2026-10-12 UTC: p95 667ms2026-10-13 UTC: p95 862ms2026-10-14 UTC: p95 658ms2026-10-15 UTC: p95 697ms2026-10-16 UTC: p95 811ms2026-10-17 UTC: p95 628ms2026-10-18 UTC: p95 767ms2026-10-19 UTC: p95 815ms2026-10-20 UTC: p95 562ms2026-10-21 UTC: p95 344ms2026-10-22 UTC: p95 464ms
Sep 23Oct 7Oct 22
Canada
561msp95 · 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-23 UTC: p95 780ms2026-09-24 UTC: p95 633ms2026-09-25 UTC: p95 787ms2026-09-26 UTC: p95 721ms2026-09-27 UTC: p95 644ms2026-09-28 UTC: p95 621ms2026-09-29 UTC: p95 733ms2026-09-30 UTC: p95 628ms2026-10-01 UTC: p95 654ms2026-10-02 UTC: p95 566ms2026-10-03 UTC: p95 574ms2026-10-04 UTC: p95 683ms2026-10-05 UTC: p95 681ms2026-10-06 UTC: p95 742ms2026-10-07 UTC: p95 639ms2026-10-08 UTC: p95 711ms2026-10-09 UTC: p95 692ms2026-10-10 UTC: p95 685ms2026-10-11 UTC: p95 698ms2026-10-12 UTC: p95 715ms2026-10-13 UTC: p95 769ms2026-10-14 UTC: p95 748ms2026-10-15 UTC: p95 720ms2026-10-16 UTC: p95 721ms2026-10-17 UTC: p95 680ms2026-10-18 UTC: p95 612ms2026-10-19 UTC: p95 680ms2026-10-20 UTC: p95 737ms2026-10-21 UTC: p95 630ms2026-10-22 UTC: p95 561ms
Sep 23Oct 7Oct 22
UK
498msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 525ms2026-09-24 UTC: p95 517ms2026-09-25 UTC: p95 497ms2026-09-26 UTC: p95 614ms2026-09-27 UTC: p95 617ms2026-09-28 UTC: p95 715ms2026-09-29 UTC: p95 523ms2026-09-30 UTC: p95 504ms2026-10-01 UTC: p95 503ms2026-10-02 UTC: p95 490ms2026-10-03 UTC: p95 525ms2026-10-04 UTC: p95 868ms2026-10-05 UTC: p95 514ms2026-10-06 UTC: p95 497ms2026-10-07 UTC: p95 466ms2026-10-08 UTC: p95 472ms2026-10-09 UTC: p95 540ms2026-10-10 UTC: p95 498ms2026-10-11 UTC: p95 491ms2026-10-12 UTC: p95 625ms2026-10-13 UTC: p95 713ms2026-10-14 UTC: p95 434ms2026-10-15 UTC: p95 472ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 902ms2026-10-18 UTC: p95 756ms2026-10-19 UTC: p95 766ms2026-10-20 UTC: p95 798ms2026-10-21 UTC: p95 815ms2026-10-22 UTC: p95 498ms
Sep 23Oct 7Oct 22
Southeast Asia
1.6sp95 · 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-23 UTC: p95 4.1s2026-09-24 UTC: p95 3.8s2026-09-25 UTC: p95 3.6s2026-09-26 UTC: p95 3.8s2026-09-27 UTC: p95 3.1s2026-09-28 UTC: p95 3.5s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
Australia
1.3sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 2.6s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 2.8s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.9s2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 2.5s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
South America
965msp95 · 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-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 928ms2026-10-22 UTC: p95 965ms
Sep 23Oct 7Oct 22

Check your own site while you wait on Honeycomb

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Honeycomb reports an incident on its status page, and again when it reports it resolved.

Get an email when Honeycomb reports an incident

Email me when Honeycomb reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Honeycomb's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 331msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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
      Checks passinglatency: 418msstatus code: 401checked: Oct 22, 2026, 9:35 PM 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
      Checks passinglatency: 328msstatus code: 401checked: Oct 22, 2026, 9:35 PM 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
      Checks passinglatency: 326msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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
    Checks passinglatency: 700msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 423msstatus code: 401checked: Oct 22, 2026, 9:35 PM 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
      Checks passinglatency: 403msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 874msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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
      Checks passinglatency: 1628msstatus code: 401checked: Oct 22, 2026, 9:35 PM 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
      Checks passinglatency: 1227msstatus code: 401checked: Oct 22, 2026, 9:34 PM 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 probe events

Email notifications for SLOs, Triggers, and Anomaly Detection not sending, 1h 1mdeclared on their status page2026-10-22
Slowness in US region, 2h 21mdeclared on their status page2026-10-20
Degraded event ingest, 1mdeclared on their status page2026-10-20
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

check 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 check readings and Honeycomb's own claim at the time, side by side.

Full check history for Honeycomb: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Honeycomb uptime by RealUptime's checksLive, from this page's own readings.
[![Honeycomb uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Honeycomb down?", https://realuptime.io/outages/honeycomb. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.honeycomb.io

RealUptime is not affiliated with Honeycomb; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.