Mar <var data-var='date'>18</var>, <var data-var='time'>11:18</var> PDT Resolved - The issue has been identified and we have shipped a fix.Mar <var data-var='date'>18</var>, <var data-var='time'>11:10</var> PDT Identified - We have identified the issue and are working on a fix.Mar <var data-var='date'>18</var>, <var data-var='time'>11:07</var> PDT Investigating - We are currently investigating this issue.

Honeycomb UI displaying an error

Mar <var data-var='date'>12</var>, <var data-var='time'>06:39</var> PDT Resolved - This incident has been resolved.Mar <var data-var='date'>12</var>, <var data-var='time'>06:17</var> PDT Update - We have rolled back a code change to our query engine, but our triggers service has not recovered. We are investigating.Mar <var data-var='date'>12</var>, <var data-var='time'>04:55</var> PDT Identified - We are investigating elevated error rates affecting queries in our US1 region. Our team is actively working on a resolution. We will provide updates as we learn more.

Elevated Querying Errors

Mar <var data-var='date'>10</var>, <var data-var='time'>07:14</var> PDT Resolved - This incident is now resolved. We are also noting that some other parts of honeycomb (the query UI) may have seen spurious failures as well during the impacted period (13:22—13:44 UTC).Mar <var data-var='date'>10</var>, <var data-var='time'>06:56</var> PDT Monitoring - We have stabilized the cluster and are monitoring the state while investigating to understand what triggered the degradation. Overall, 0.04% traffic was rejected with an error due to this degradation during the 20 minute window we were impaired.Mar <var data-var='date'>10</var>, <var data-var='time'>06:50</var> PDT Investigating - We are currently seeing elevated errors in connecting to some of our databases, which results in low amounts of Ingest traffic being rejected. We are looking into correcting the situation.

Degraded Ingest due to database connectivity issues

Feb <var data-var='date'>18</var>, <var data-var='time'>15:07</var> PST Resolved - Between 22:10 and 22:40 UTC on Feb18, 2026 Honeycomb experienced a partial query outage in our EU environment. The incident has been resolved, and we are continuing to investigate the contributing factors.

Partial query outage in EU1

Feb <var data-var='date'>10</var>, <var data-var='time'>12:30</var> PST Resolved - This incident has been resolved.Feb <var data-var='date'>10</var>, <var data-var='time'>12:18</var> PST Investigating - We are aware of elevated errors in trigger evaluations and queries, and are working to resolve it

Query Errors

Jan <var data-var='date'>22</var>, <var data-var='time'>15:42</var> PST Resolved - This appears to have been a minor transient network issue; we do not expect this to recurJan <var data-var='date'>22</var>, <var data-var='time'>15:27</var> PST Investigating - We are currently investigating what appears to be a transient issue related to querying and triggers

Transient querying and trigger failures

Jan <var data-var='date'>15</var>, <var data-var='time'>07:46</var> PST Resolved - We observed a period of increased latency accompanied by a higher-than-normal error rate in some event ingest requests in the US. The service has since stabilized and is operating normally. We are continuing to monitor the system and are evaluating improvements to reduce the impact of similar conditions in the future. We apologize for the disruption and appreciate your patience.

Increased Latency and Errors for Events Ingest

Jan <var data-var='date'> 7</var>, <var data-var='time'>11:54</var> PST Resolved - This incident has been resolved.Jan <var data-var='date'> 7</var>, <var data-var='time'>11:53</var> PST Update - We have stabilized activity log. We have confirmed activity log entries lost from 4:54pm-7:04pm ET in the US and 9:43pm-11:55pm GMT in the EU. Event ingest was unimpacted. All systems are currently operating normallyJan <var data-var='date'> 6</var>, <var data-var='time'>17:17</var> PST Update - We have restored basic activity log functionality, though some delays remain, and we will analyze further tomorrow during business hours.Jan <var data-var='date'> 6</var>, <var data-var='time'>15:05</var> PST Update - We are currently expecting to lose the last three hours of data for the beta activity log feature as part of remediation of this issue.Jan <var data-var='date'> 6</var>, <var data-var='time'>14:37</var> PST Update - We have resolved the issue which impacted querying but are still working to get Activity Log up to dateJan <var data-var='date'> 6</var>, <var data-var='time'>14:14</var> PST Identified - We are seeing a spike in querying errors and the Activity Log has delayed ingest of new activity. We have identified the issue and are working to resolve

Degraded querying and delayed records sent to Activity Log

Dec <var data-var='date'>17</var>, <var data-var='time'>07:47</var> PST Resolved - As of 23:23UTC on December 16, the Activity Log has fully caught up and has remained up to date. All systems are now operational.Dec <var data-var='date'>16</var>, <var data-var='time'>12:17</var> PST Monitoring - We successfully created and migrated over to a new kafka cluster in the EU. We have resumed consuming events for our SLO and Service Maps features. No further data loss is expected for service maps. SLOs are caught up and are fully synchronized. Activity logs are still delayed and expect to be caught up in about 5 hours. We consider this incident to be mitigated, but will continue to monitor until Activity logs are caught up.Dec <var data-var='date'>15</var>, <var data-var='time'>17:52</var> PST Update - As of today, our old EU cluster is still functional, yet in a bad state. We do not consider this outage over. However, after running a full evacuation in a pre-production cluster, we are now ready to run a production version of it. This will only be in the impacted EU cluster. We are planning to do it on 6pm UTC December 16th. We expect no ingestion downtime, although we will expect delays on processing events and alerts, will suffer minor data loss in our Service Maps feature, and lose 11 days worth of Activity log events starting the night of December 5th. We will provide updates throughout the migration.Dec <var data-var='date'>12</var>, <var data-var='time'>15:20</var> PST Update - We continue to work toward restoring the Activity Log. We’ve made meaningful progress on the underlying issues, but have had to pivot on our remediation plan due to previously unknown hard retention limits. Our engineering team is working through the next steps required to restore Activity Log processing. Next updates to come during Monday US business hoursDec <var data-var='date'>11</var>, <var data-var='time'>16:09</var> PST Update - We continue to work toward restoring the Activity Log. We’ve made meaningful progress on the underlying issues, but have had to pivot on our remediation plan due to previously unknown hard retention limits. Our engineering team is actively working through the next steps required to restore Activity Log processing.Dec <var data-var='date'>11</var>, <var data-var='time'>10:02</var> PST Update - We continue to work toward fully restoring the Activity Log. We’ve made meaningful progress on the underlying issues and continue to work through our remediation plan. Our engineering team is actively working through the next steps required to restore Activity Log processing.Dec <var data-var='date'>10</var>, <var data-var='time'>17:08</var> PST Update - We continue to work toward fully restoring the Activity Log. While functionality has not yet improved, we’ve made progress on the underlying issue and have begun the next phase of remediation. Our engineering team is pausing for the evening and will resume working through the remaining steps required to resume Activity Log processing during US business hours tomorrow. We will provide another update tomorrow morning.Dec <var data-var='date'>10</var>, <var data-var='time'>09:34</var> PST Update - We continue to work toward fully restoring the Activity Log. While functionality has not yet improved, we’ve made progress on the underlying issue and have begun the next phase of remediation. Our engineering team is actively working through the remaining steps required to resume Activity Log processing.Dec <var data-var='date'> 9</var>, <var data-var='time'>14:40</var> PST Update - We continue to work toward fully restoring the Activity Log. While functionality has not yet improved, we have a clear path to recovery, and remediation work is underway. Our next steps involve coordinated infrastructure changes that will allow us to resume Activity Log processing. We’ll provide another update during US business hours Wednesday.Dec <var data-var='date'> 8</var>, <var data-var='time'>18:05</var> PST Update - We are continuing to work on a fix for this issue.Dec <var data-var='date'> 8</var>, <var data-var='time'>18:01</var> PST Update - We fixed the issue that was causing subsets of temporarily missing data in queries against certain partitions. We continue to work on restoring full functionality to Activity Log. We'll provide another update during US business hours Tuesday.Dec <var data-var='date'> 8</var>, <var data-var='time'>17:02</var> PST Update - We continue to work on restoring full functionality to Activity Log and repair the partition causing certain customers to have subsets of unqueryable data. We will next provide an update during US business hours Tuesday.Dec <var data-var='date'> 8</var>, <var data-var='time'>13:52</var> PST Update - The Activity Log is operational but is experiencing ingestion delays, which means recent activity may not be reflected immediately. We are working to restore full functionality. Currently, a small subset of data for certain customers may not be queryable due to a partition needing repair. We are working to return the data to queryability. After investigation of the impact starting on Friday to SLO and Trigger functionality, we're providing the update below with the details. Overview SLOs and Triggers were affected by Kafka and ingest outages beginning Friday, December 5 at 8:40 PM UTC. Trigger evaluations are now behaving normally except for some baseline triggers. SLOs with evaluation periods that include missing ingest or are on the affected partition will reflect that currently unqueryable data in their ongoing calculations. SLOs - No burn alerts were fired between December 5, 2025 at 8:40 PM UTC and December 6, 2025 at 7:15 PM UTC due to a processing delay. - Now that ingest is restored, burn alerts should behave normally again minus a subset that are also impacted by the small amount of currently unqueryable data. Triggers - When ingest was down on December 6, no events were received, so all EU Trigger evaluations were impacted. - Baseline Triggers with lookback windows that query data in the affected partition returning will also be affected by the small amount of currently unqueryable data. - Non-baseline triggers (which can only look back 24 hours) should behave normally going forward. We will provide an update at the end of the workday (5PM PT) or as the situation changes.Dec <var data-var='date'> 7</var>, <var data-var='time'>12:23</var> PST Update - Our Kafka cluster is still operational and we are continuing to work towards restoring full reliability. We will resume work during business hours to restore full Activity Log functionality. We will continue to update as work progresses.Dec <var data-var='date'> 6</var>, <var data-var='time'>18:18</var> PST Update - The Kafka cluster is still operational, but is not back to full capacity and resiliency. Work will continue tomorrow to ensure sufficient capacity, as well as during business hours to resume full Activity Log functionality. We will provide more updates tomorrow and as-needed if there are any changes to availability.Dec <var data-var='date'> 6</var>, <var data-var='time'>16:10</var> PST Update - We have gotten the Kafka cluster to a stable-enough state, however it will still require remediation before the Activity Log is fully functional and it is back to a level of service sustainable until business hours. We will provide another update in 2 hours or as the situation changes.Dec <var data-var='date'> 6</var>, <var data-var='time'>14:08</var> PST Update - Ingest has been fully re-enabled, and SLOs and Triggers are now up-to-date.Dec <var data-var='date'> 6</var>, <var data-var='time'>13:51</var> PST Identified - We have resumed ingest to api.eu1.honeycomb.io as we were able to restore partial service to the Kafka cluster.Dec <var data-var='date'> 6</var>, <var data-var='time'>13:23</var> PST Update - We are continuing to investigate issues with the Kafka cluster. We will continue providing updates every 2 hours unless there are significant changes.Dec <var data-var='date'> 6</var>, <var data-var='time'>11:20</var> PST Update - We are continuing to investigate issues with the Kafka cluster.Dec <var data-var='date'> 6</var>, <var data-var='time'>08:15</var> PST Update - External API access is restored, event ingestion is still impactedDec <var data-var='date'> 6</var>, <var data-var='time'>07:19</var> PST Update - We have temporarily disabled event ingestion for the EU Region, in service of restoring full functionality to our EU Kafka fleet. External API access will also be disabled. Additionally, during the ongoing outage, our Service Level Objectives feature has been impacted and down since 12:30 PM Pacific time on Friday, December 5th. SLO data will not be correct until our systems catch up and we rebuild the cacheDec <var data-var='date'> 5</var>, <var data-var='time'>23:30</var> PST Update - Automated systems are still working to catch up and Activity Log will remain offline until that that completes. We will post another update Saturday whether or not the Activity Log outage has been remediated.Dec <var data-var='date'> 5</var>, <var data-var='time'>16:04</var> PST Update - Ingest, querying, SLOs, and Trigger alerting is back to normal. Activity Log is still impacted, we have identified the cause and are working to resolve. We are still evaluating the scope of the outage for ingest and expect to have a full answer for that posted during US business hours on Monday. We will post at least one more update this evening.Dec <var data-var='date'> 5</var>, <var data-var='time'>15:46</var> PST Update - We are continuing the investigation after business hours to stabilize ingest and determine what work will be needed to fully recover. Known impact will be updated here as the situation changes. We will post at least one more update this evening.Dec <var data-var='date'> 5</var>, <var data-var='time'>14:33</var> PST Update - We have identified that 0.23% of datasets are fully affected, and a larger percentage are seeing intermittent ingestion and query failures (500s at the API level). We are also investigating a replication error in our ingestion pipeline.Dec <var data-var='date'> 5</var>, <var data-var='time'>13:19</var> PST Update - A subset of customer environments may see higher than usual error rates when sending events to api.eu1.honeycomb.io, and notifications for SLOs and Triggers may be delayed for that subset. We are continuing to investigate the issue.Dec <var data-var='date'> 5</var>, <var data-var='time'>12:49</var> PST Investigating - We are currently investigating this issue.

Querying and Ingest issues in EU

Dec <var data-var='date'>16</var>, <var data-var='time'>12:00</var> PST Completed - The scheduled maintenance has been completed.Dec <var data-var='date'>16</var>, <var data-var='time'>11:53</var> PST Update - We have completed part of our migration. Querying should now be back to normal. Triggers are firing as expected again. SLOs, service maps, and activity log are still delayed and will return to normal gradually.Dec <var data-var='date'>16</var>, <var data-var='time'>11:43</var> PST Update - Querying should now be back to normal with all historical data. Triggers are firing as expected again. SLOs and service maps are still delayed.Dec <var data-var='date'>16</var>, <var data-var='time'>11:22</var> PST Update - We are in the middle of the migration, it is expected that new data is unavailable for querying and alerts are slightly delayed.Dec <var data-var='date'>16</var>, <var data-var='time'>10:43</var> PST Update - As announced earlier, we are now beginning an emergency maintenance procedure. We expect no ingestion downtime, although we will expect delays on processing events and alerts, will suffer minor data loss in our Service Maps feature, and lose roughly 4 days worth of Activity log events (from December 5 to December 9).Dec <var data-var='date'>16</var>, <var data-var='time'>10:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'>15</var>, <var data-var='time'>23:54</var> PST Update - We will be undergoing scheduled maintenance during this time.Dec <var data-var='date'>15</var>, <var data-var='time'>23:53</var> PST Scheduled - As we posted earlier in a previous update, we are going to perform a full evacuation of our old Kafka cluster in the EU region in order to repair the functionality of the Activity Log, among many other internals that are in limp mode currently. This will only impact the EU cluster - we expect no ingestion downtime, although we will expect delays on processing events and alerts, will suffer minor data loss in our Service Maps feature, and lose 11 days worth of Activity log events starting the night of December 5th. This maintenance will occur at on 6pm UTC December 16th.

EU ONLY - Production EU Kafka migration

Dec <var data-var='date'> 5</var>, <var data-var='time'>12:15</var> PST Completed - The scheduled maintenance has been completed.Dec <var data-var='date'> 5</var>, <var data-var='time'>12:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'> 2</var>, <var data-var='time'>14:07</var> PST Scheduled - We will be performing system maintenance at this time. We expect it to last approximately 15 minutes and no service downtime is expected.

System Maintenance

Nov <var data-var='date'>26</var>, <var data-var='time'>16:14</var> PST Resolved - As of 23:00 UTC, all systems are back to synchronized.Nov <var data-var='date'>26</var>, <var data-var='time'>09:24</var> PST Update - We are continuing to work on catching up late data from yesterday night's replication issues and expect to complete this process in approximately 6 hours.Nov <var data-var='date'>25</var>, <var data-var='time'>21:07</var> PST Monitoring - Due to issues with replication streams, the activity log will have a gap in its data. We estimate that a little over 6 hours of content will be missing, from 20:27 UTC until 2:43 UTC. We do not expect missing data to be backfilled. No other Honeycomb data or feature has been impacted. We are currently working on catching up on late data after this window.Nov <var data-var='date'>25</var>, <var data-var='time'>21:02</var> PST Update - We are continuing to work on a fix for this issue.Nov <var data-var='date'>25</var>, <var data-var='time'>14:51</var> PST Identified - We have identified the cause and are working to resolve the issue.

Activity log outage in production US

Oct <var data-var='date'>21</var>, <var data-var='time'>08:41</var> PDT Resolved - This incident has been resolved. At no point did we lose any customer data that hit our load balancers. Querying has been stable for hours, and all features that were degraded are functional.Oct <var data-var='date'>20</var>, <var data-var='time'>17:11</var> PDT Update - Honeycomb core functionality is operational. Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. This is our final update for the night unless the situation degrades. We will continue to monitor the situation.Oct <var data-var='date'>20</var>, <var data-var='time'>16:08</var> PDT Update - Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. We are continuing to monitor the situation.Oct <var data-var='date'>20</var>, <var data-var='time'>13:06</var> PDT Update - AWS is starting to show signs of recovery. Querying remains partially impacted and may take longer to return results. We are continuing to monitor the situation.Oct <var data-var='date'>20</var>, <var data-var='time'>10:39</var> PDT Update - We’re currently observing that querying is seeing signs of recovery. We are continuing to monitor the situationOct <var data-var='date'>20</var>, <var data-var='time'>08:30</var> PDT Update - The networking issues in us-east-1 is affecting our query engine - customers may see errors or delays when running queries as a result.Oct <var data-var='date'>20</var>, <var data-var='time'>08:14</var> PDT Update - SLO processing has recovered. Service Maps continues to be degraded but historical data can be queried.Oct <var data-var='date'>20</var>, <var data-var='time'>07:16</var> PDT Monitoring - Due to constrained EC2 instance capacity in the AWS us-east-1 region, we are choosing to allocate the capacity we have to incoming events and telemetry. As such, customers may see over 5 minute delays in our processing of - SLOs - Service Maps We do not expect a degradation of our core ingest -> query flow, and we do not expect triggers to be impacted

Delays in SLO, Service Maps processing

Oct <var data-var='date'>20</var>, <var data-var='time'>03:04</var> PDT Resolved - All affected systems have fully recovered.Oct <var data-var='date'>20</var>, <var data-var='time'>02:49</var> PDT Monitoring - We are beginning to see recovery across our systems. We will continue to monitor the situation in case of any regressions.Oct <var data-var='date'>20</var>, <var data-var='time'>01:46</var> PDT Update - We are currently experiencing degraded performance. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes trace queries. SLO and Trigger alerts may be missed or delayed. Queries may return results, but those results may not be saved, meaning that loading queries that other people have run may fail. After the problem resolves, queries may need to be rerun. Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>01:14</var> PDT Update - We are currently experiencing degraded performance for queries. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs, Triggers, and Traces. Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>00:24</var> PDT Identified - We are currently experiencing degraded performance for queries that access older data stored in cold storage. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs and Triggers. Queries over recent or “hot” data are not impacted. Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.

Investigating Querying Issues

Oct <var data-var='date'> 8</var>, <var data-var='time'>08:24</var> PDT Resolved - The system has remained stable, we do believe everything to now be in order.Oct <var data-var='date'> 8</var>, <var data-var='time'>08:10</var> PDT Monitoring - We have made changes to our configuration and errors rates seem to have gone back to normal. We are keeping an eye on things to know the features remain stable.Oct <var data-var='date'> 8</var>, <var data-var='time'>07:26</var> PDT Identified - We are currently experiencing issues with our configuration with one of our AI providers. Features such as Query Assistant and our Calculated Field assistant are not functional, and some other parts of Honeycomb Intelligence may be partially degraded at this moment.

Partially Degraded Honeycomb Intelligence Features

Sep <var data-var='date'>24</var>, <var data-var='time'>18:22</var> PDT Resolved - Service Maps functionality has been restored.Sep <var data-var='date'>24</var>, <var data-var='time'>17:07</var> PDT Investigating - An outage with an upstream service provider is currently affecting Honeycomb's infrastructure. Functionality of the ServiceMaps feature is degraded at this time.

ServiceMaps down due to issues with an upstream provider

Aug <var data-var='date'>27</var>, <var data-var='time'>21:30</var> PDT Resolved - A PagerDuty outage prevented some Trigger and SLO notifications from reaching your workspaces. The issue has since been resolved, and notification systems are now operating normally. Impact Window: 21:54 PT – 23:27 PT

PagerDuty outage prevented Trigger and SLO notifications

Aug <var data-var='date'>27</var>, <var data-var='time'>08:36</var> PDT Resolved - We have determined the cause and implemented a fix. Customers should be seeing normal operations again.Aug <var data-var='date'>27</var>, <var data-var='time'>08:19</var> PDT Investigating - We're see a partial degradation of data liveness, which may impact triggers and SLOs in a small percentage of users

Partial degradation of data liveness for a subset of US users

Aug <var data-var='date'>13</var>, <var data-var='time'>02:30</var> PDT Resolved - For a period of approximately 1h30, from 9:34 UTC to 11:08 UTC, our ingestion of events in the EU region was delayed. All events were eventually processed, but for that duration, triggers, SLOs, and regular queries could have seen missing data for a brief period of time. As we re-balanced traffic loads and scaled the system, ingestion caught up and data has since then been fully available. We are still actively working on improving the scaling margins and behaviors of the EU instance of Honeycomb to better sustain load variations we are observing at this time.

Delayed ingestion of events in EU region

Aug <var data-var='date'>12</var>, <var data-var='time'>08:37</var> PDT Resolved - Our load-balancing of ingestion traffic is doing its job and everything is back to normal.Aug <var data-var='date'>12</var>, <var data-var='time'>08:30</var> PDT Monitoring - We have load-balanced ingestion traffic to bring back performance under control, and are currently monitoring to make sure it stays that way.Aug <var data-var='date'>12</var>, <var data-var='time'>08:17</var> PDT Identified - Data ingestion is currently being delayed in the EU region. All traffic is being accepted, but it may take some time to show up in queries, and may have an impact on trigger-based alerting as well.

Ingestion delays in EU

Jul <var data-var='date'>21</var>, <var data-var='time'>13:53</var> PDT Resolved - This incident has been resolved.Jul <var data-var='date'>21</var>, <var data-var='time'>12:52</var> PDT Monitoring - A fix has been implemented and customers should see query speed returning to normalJul <var data-var='date'>21</var>, <var data-var='time'>11:01</var> PDT Identified - We are seeing a querying slowdown in the US. We have identified the cause and are working to mitigate

Querying slow down in Production US

Jul <var data-var='date'>21</var>, <var data-var='time'>08:59</var> PDT Resolved - This incident has been resolved.Jul <var data-var='date'>21</var>, <var data-var='time'>08:25</var> PDT Monitoring - An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.

Delay in SLO and errors in Trigger notifications

Jul <var data-var='date'>16</var>, <var data-var='time'>07:47</var> PDT Resolved - This incident has been resolved.Jul <var data-var='date'>15</var>, <var data-var='time'>22:00</var> PDT Monitoring - A fix has been implemented and we are monitoring the resultsJul <var data-var='date'>15</var>, <var data-var='time'>21:38</var> PDT Investigating - Telemetry is being intermittently dropped in the EU and we are currently investigating the cause

Ingestion API is struggling in Prod EU

Jun <var data-var='date'>25</var>, <var data-var='time'>18:00</var> PDT Resolved - The incident is resolved.Jun <var data-var='date'>25</var>, <var data-var='time'>17:20</var> PDT Monitoring - Querying capabilities are now restored.Jun <var data-var='date'>25</var>, <var data-var='time'>17:15</var> PDT Identified - We have identified the cause of the problem and have begun a revert.Jun <var data-var='date'>25</var>, <var data-var='time'>17:08</var> PDT Investigating - A build needs to be reverted as we have ongoing failures when rendering query results.

Queries are failing with errors

Jun <var data-var='date'>13</var>, <var data-var='time'>12:31</var> PDT Resolved - This incident has been resolved.Jun <var data-var='date'>13</var>, <var data-var='time'>11:53</var> PDT Monitoring - A fix has been implemented and we are monitoring the results.Jun <var data-var='date'>13</var>, <var data-var='time'>11:51</var> PDT Identified - We have identified the feature flag that triggered this and are rolling it back.

Is Honeycomb.io down?

Honeycomb.io status is UP

Lastest published events

Honeycomb UI displaying an error

Elevated Querying Errors

Degraded Ingest due to database connectivity issues

Honeycomb.io Services, Components and Regions

Recent Honeycomb.io events

Honeycomb UI displaying an error

Elevated Querying Errors

Degraded Ingest due to database connectivity issues

Partial query outage in EU1

Query Errors

Transient querying and trigger failures

Get your FREE account now,
5 monitors included!

Is Honeycomb.io down?

Honeycomb.io status is UP

Lastest published events

Honeycomb UI displaying an error

Elevated Querying Errors

Degraded Ingest due to database connectivity issues

Honeycomb.io Services, Components and Regions

Recent Honeycomb.io events

Honeycomb UI displaying an error

Elevated Querying Errors

Degraded Ingest due to database connectivity issues

Partial query outage in EU1

Query Errors

Transient querying and trigger failures

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!