Looking for an update now? Check the current status, or follow Honeycomb for future changes.
98.3%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We've identified and isolated the impacted service and are seeing recovery in query execution. SLO processing remains degraded.
investigating
We are currently investigating the degradation of various services in our US region.
Legacy Incident Archive
23 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Delayed ingest in EU
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
Queries should no longer be delayed. SLOs and Trigger evaluations remain impacted.
investigating
We are investigating an issue with delayed ingest in the EU region. Received events are still being stored, but there may be a delay in event retrieval in queries. SLOs and Trigger evaluations may also be delayed.
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
investigating
We have identified and are working to resolve an issue that is causing query results to return inconsistent results.
activity log for US instance is delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Activity Log recovered at 07:00 UTC-07:00 today (about 6.5h ago). All streams are caught up.
monitoring
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.
monitoring
We are continuing to monitor for any further issues.
monitoring
We believe that the activity log should now be caught up.
monitoring
Backfilling of the past 2h30m of data is now in progress and should complete shortly.
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.
April 2026
Links in Slack triggers not working
Source not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented and links on Slack triggers are functional again.
identified
We discovered that links in Slack triggers are not working and have identified the cause and are in process of implementing a fix
Activity Log events interrupted for EU
majorSource not attested
Last archived state: resolved
View archived record details
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 ingest is delayed
minorSource not attested
Last archived state: resolved
View archived record details
identified
Activity Log is experiencing a delay in processing events. We are working on remediating the issue.
Activity Log delayed ingest in EU
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring recovery.
identified
Activity Log events may be delayed, starting from around 19:55UTC. We're actively working on remediation.
Ingest issues for some customers
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
The manual fix has been applied to all environments.
monitoring
We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.
identified
We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.
identified
We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.
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.
