May <var data-var='date'>22</var>, <var data-var='time'>09:42</var> PDT Resolved - This is an administrative update, marking the incident as Resolved. There has been no further impact since 23:20UTC on May 21 2026. May <var data-var='date'>21</var>, <var data-var='time'>17:49</var> PDT Update - Impact from this issue has concluded. For a period of time (different between US and EU instances, noted below), queries spanning data older than the most recent 2 hours with certain GROUP / WHERE clauses returned inconsistent results. Data was never lost, and reruns of the same queries will show the previously missing data. US impact times: 21:50 UTC - 23:20 UTC EU impact times: 20:50 UTC - 23:20 UTC May <var data-var='date'>21</var>, <var data-var='time'>16:22</var> PDT Investigating - We have identified and are working to resolve an issue that is causing query results to return inconsistent results.

Investigating querying issues

May <var data-var='date'>11</var>, <var data-var='time'>09:37</var> PDT Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>13:46</var> PDT Update - Activity Log recovered at 07:00 UTC-07:00 today (about 6.5h ago).  All streams are caught up. May <var data-var='date'> 8</var>, <var data-var='time'>03:40</var> PDT Update - All activity log streams are now caught up, except for the query runs table, which should have all data since the start of the incident backfilled by 1600 PDT. May <var data-var='date'> 8</var>, <var data-var='time'>03:22</var> PDT Update - We are continuing to monitor for any further issues. May <var data-var='date'> 8</var>, <var data-var='time'>03:21</var> PDT Update - We believe that the activity log should now be caught up. May <var data-var='date'> 8</var>, <var data-var='time'>03:13</var> PDT Monitoring - Backfilling of the past 2h30m of data is now in progress and should complete shortly. May <var data-var='date'> 8</var>, <var data-var='time'>01:00</var> PDT Identified - Activity log delay is rising, and is more than an hour behind due to a MySQL replica failover. Estimated recovery by 04:00 PDT.

activity log for US instance is delayed

May <var data-var='date'> 7</var>, <var data-var='time'>15:44</var> PDT Completed - Scheduled maintenance is complete. All services are healthy and stable. Ingest, querying SLO processing, anomaly detection, Service Maps, and Activity Log are all confirmed operating normally. Backfill and SLO repair are complete. Thank you for your patience. May <var data-var='date'> 7</var>, <var data-var='time'>15:27</var> PDT Update - We are now in our final verification stage. Query results should begin returning fresh data now. May <var data-var='date'> 7</var>, <var data-var='time'>15:13</var> PDT Verifying - All consumer services have been successfully cut over. SLO backfill is currently running. Anomaly detection, Service Maps, and Activity Log processing are all on the new cluster and catching up. All data will be fully present within approximately 2 hours of the maintenance window closing. May <var data-var='date'> 7</var>, <var data-var='time'>13:53</var> PDT Update - Scheduled maintenance is still in progress. We will provide updates as necessary. May <var data-var='date'> 7</var>, <var data-var='time'>13:10</var> PDT In progress - We have begun scheduled maintenance on our Kafka infrastructure in Production US. During this window, event ingestion and query results may experience delays. Apr <var data-var='date'>28</var>, <var data-var='time'>11:49</var> PDT Scheduled - We will be performing scheduled maintenance on our Kafka infrastructure in the US region. This maintenance will only impact the US cluster. During this window, you may experience the following: Ingest will remain uninterrupted - events will continue to be accepted, although their processing will be delayed. You may notice a gap in your data during the migration window; this data will be backfilled after the migration completes. Expect all data to be present within approximately 3 hours of the maintenance window closing. Query results will reflect a delay in fresh data during the cutover window, in line with the ingestion delays. Triggers and alerts: Triggers watching for missing events (e.g. heartbeats) will fire during this window. Triggers watching for values above a threshold are not expected to fire. Other alerting sources will process delayed events late, up to approximately 3 hours. SLO burn alerts will also fire late during this window. Activity Log and Service Maps will experience delays in processing events. We appreciate your patience and will provide updates as the maintenance progresses

Scheduled Maintenance - US Region

May <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> PDT Completed - Scheduled maintenance is complete. All services are healthy and stable. Ingest, Querying, SLO processing, Anomaly Detection, Service Maps, Triggers and Activity Log are all confirmed operating normally. Backfill and SLA repair are complete. Thank you for your patience. May <var data-var='date'> 4</var>, <var data-var='time'>12:08</var> PDT Verifying - We are in our final verification phase. Query results, SLO calculations, anomaly detection, and Service Maps are all confirmed processing as expected. May <var data-var='date'> 4</var>, <var data-var='time'>11:14</var> PDT Update - Query results should begin returning fresh data shortly. SLO processing and Service Maps migration are still in progress. May <var data-var='date'> 4</var>, <var data-var='time'>10:28</var> PDT Update - We have begun scheduled maintenance on our Kafka infrastructure in Production EU. May <var data-var='date'> 4</var>, <var data-var='time'>10:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>27</var>, <var data-var='time'>13:58</var> PDT Scheduled - We will be performing scheduled maintenance on our Kafka infrastructure in the EU region. This maintenance will only impact the EU cluster. During this window, you may experience the following: * Ingest will remain uninterrupted - events will continue to be accepted, although their processing will be delayed. You may notice a gap in your data during the migration window; this data will be backfilled after the migration completes. Expect all data to be present within approximately 3 hours of the maintenance window closing. * Query results will reflect a delay in fresh data during the cutover window, in line with the ingestion delays. * Triggers and alerts: Triggers watching for missing events (e.g. heartbeats) will fire during this window. Triggers watching for values above a threshold are not expected to fire. Other alerting sources will process delayed events late, up to approximately 3 hours. * SLO burn alerts will also fire late during this window. * Activity Log and Service Maps will experience delays in processing events. We appreciate your patience and will provide updates as the maintenance progresses

Scheduled Maintenance – EU Region

May <var data-var='date'> 1</var>, <var data-var='time'>06:00</var> PDT Resolved - The database failover that caused query issues earlier in the EU (https://status.honeycomb.io/incidents/n855d8kzp32y) has also had knock-on effects on our Activity Log beta feature. Due to recovery issues on the data replication flow used for this mechanism, activity log events will be missing from 12:45 UTC until 19:45 UTC, representing a 5 hour gap in events. We have identified configuration parameters that will be adjusted to reduce the likelihood of such losses in the future.

Gap in Activity Log data in the EU region.

May <var data-var='date'> 1</var>, <var data-var='time'>05:30</var> PDT Resolved - At 12:50, our main database underwent an automated failover. This failover led to issues with some of our query engine connection pools, and caused queries to fail for roughly 10 minutes before self resolving.

Query interuption due to database failover in the EU region

Apr <var data-var='date'>30</var>, <var data-var='time'>09:37</var> PDT Resolved - We are confident the issue is fully resolved. Apr <var data-var='date'>30</var>, <var data-var='time'>08:07</var> PDT Monitoring - The fix has been implemented and links on Slack triggers are functional again. Apr <var data-var='date'>30</var>, <var data-var='time'>08:03</var> PDT Identified - We discovered that links in Slack triggers are not working and have identified the cause and are in process of implementing a fix

Links in Slack triggers not working

Apr <var data-var='date'>20</var>, <var data-var='time'>10:02</var> PDT Resolved - Activity Log is back to operational, and most events should be recovered. Apr <var data-var='date'>20</var>, <var data-var='time'>09:56</var> PDT Identified - Activity Log events are interrupted, starting from around 15:51UTC. Customers may experience some data lost since the beginning of the incident.

Activity Log events interrupted for EU

Apr <var data-var='date'>15</var>, <var data-var='time'>12:25</var> PDT Resolved - Activity Log is ingesting events again. We had no loss in data. Apr <var data-var='date'>15</var>, <var data-var='time'>12:04</var> PDT Identified - Activity Log is experiencing a delay in processing events. We are working on remediating the issue.

Activity Log ingest is delayed

Apr <var data-var='date'>14</var>, <var data-var='time'>15:37</var> PDT Resolved - All activity log data is now live and up to date. Apr <var data-var='date'>14</var>, <var data-var='time'>15:08</var> PDT Monitoring - A fix has been implemented and we are monitoring recovery. Apr <var data-var='date'>14</var>, <var data-var='time'>14:36</var> PDT Identified - Activity Log events may be delayed, starting from around 19:55UTC. We're actively working on remediation.

Activity Log delayed ingest in EU

Apr <var data-var='date'>10</var>, <var data-var='time'>12:10</var> PDT Resolved - All activity log data is now live and up to date. Apr <var data-var='date'> 9</var>, <var data-var='time'>17:05</var> PDT Update - SLO processing has fully recovered. Apr <var data-var='date'> 9</var>, <var data-var='time'>16:43</var> PDT Update - SLOs experienced a period of additional processing delays. A fix has been deployed and recovery is ongoing. Apr <var data-var='date'> 9</var>, <var data-var='time'>14:03</var> PDT Update - We have identified an issue with triggers and SLOs and have implemented a fix. Customers should no longer see degraded performance for triggers or SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes. Apr <var data-var='date'> 9</var>, <var data-var='time'>13:24</var> PDT Update - We have identified an issue with triggers and SLOs and are actively investigating. Customers may experience delays when creating or updating triggers and SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes. Apr <var data-var='date'> 9</var>, <var data-var='time'>04:52</var> PDT Identified - We have identified the cause and are working to resolve the issue.

Activity log delay in production US

Apr <var data-var='date'>10</var>, <var data-var='time'>10:24</var> PDT Resolved - We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore. Apr <var data-var='date'>10</var>, <var data-var='time'>08:21</var> PDT Update - We are continuing to work on the systemic solution and monitor. We'll leave the incident open until we're able to confirm the issue won't recur. Apr <var data-var='date'>10</var>, <var data-var='time'>07:32</var> PDT Update - The manual fix has been applied to all environments. Apr <var data-var='date'>10</var>, <var data-var='time'>07:19</var> PDT Monitoring - We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress. Apr <var data-var='date'>10</var>, <var data-var='time'>06:55</var> PDT Update - We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution. Apr <var data-var='date'>10</var>, <var data-var='time'>06:46</var> PDT Update - We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment. Apr <var data-var='date'>10</var>, <var data-var='time'>06:41</var> PDT Identified - We have confirmed reports of some teams getting issues ingesting their data. We have identified a probable source behind this behavior and are currently trying to correct it.

Ingest issues for some customers

Apr <var data-var='date'> 9</var>, <var data-var='time'>12:00</var> PDT Resolved - We have detected and remediated an issue around our SLO processing pipeline. From 17:00 to 17:15 UTC, events were being delayed, and alerts may likewise have been a few minutes late. Processing has caught up and is currently within normal operational ranges.

SLO processing delay in US

Apr <var data-var='date'> 9</var>, <var data-var='time'>03:12</var> PDT Resolved - We experienced a partial querying outage from approximately 8:58 - 9:18 UTC. This outage may have resulted in some Trigger and SLO alert failures for the duration of the outage. The cause of the outage has been identified and mitigated.

Partial Querying Outage

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 recur Jan <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 normally Jan <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 date Jan <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 hours Dec <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 impacted Dec <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 cache Dec <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.

Is Honeycomb.io down?

Honeycomb.io status is UP

Lastest published events

Investigating querying issues

activity log for US instance is delayed

Scheduled Maintenance - US Region

Honeycomb.io Services, Components and Regions

Recent Honeycomb.io events

Investigating querying issues

activity log for US instance is delayed

Scheduled Maintenance - US Region

Scheduled Maintenance – EU Region

Gap in Activity Log data in the EU region.

Query interuption due to database failover in the EU region

Get your FREE account now,
5 monitors included!

Is Honeycomb.io down?

Honeycomb.io status is UP

Lastest published events

Investigating querying issues

activity log for US instance is delayed

Scheduled Maintenance - US Region

Honeycomb.io Services, Components and Regions

Recent Honeycomb.io events

Investigating querying issues

activity log for US instance is delayed

Scheduled Maintenance - US Region

Scheduled Maintenance – EU Region

Gap in Activity Log data in the EU region.

Query interuption due to database failover in the EU region

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!