Honeycomb Incident History

We have identified resource contention that currently leads to degraded query performance, which has slowed down most querying types for the last hour.The situation seems to be improving but we are keeping an eye on it.

Between 18:10 and 18:15 UTC, we saw elevated levels of query failures, including ones made by users and ones made as part of trigger invocations. The system automatically recovered, and begun to serve queries again.After this, from 18:15 UTC to approximately 18:40 UTC, some user queries timed out after 5 minutes. No impact to triggers was seen during this time.

The Query Builder WHERE clause is currently rejecting lower-case selections where there are two columns with the same name that differ only in casing (e.g. if "name" vs "Name" are both present, it would not be possible to select "name"). We have identified the problem and are working on a fix.

Autocomplete in the where clause of Honeycomb UI's query builder was lowercasing all user input, preventing queries from being run correctly.A fix for this has been deployed and users should be able to run queries as expected again.