Hevo incident
Degraded performance in US2 [AWS, Oregon (us-west-2)] cluster
Hevo experienced a minor incident on February 4, 2026 affecting Sources and Data Pipelines, lasting 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 04, 2026, 04:44 PM UTC
We have identified lag buildups across pipelines for some of the teams in the US2 cluster. If you're facing some lag with data delivery, kindly rest assured that we're working on it as our topmost priority. Apologies for any inconvenience. We will share further updates here in some time.
- investigating Feb 04, 2026, 04:45 PM UTC
We are continuing to investigate this issue.
- identified Feb 04, 2026, 05:02 PM UTC
The issue has been identified, and we're working on the fix. We want to ensure all the impacted users that this will be mitigated very soon.
- identified Feb 04, 2026, 05:02 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 04, 2026, 05:19 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 04, 2026, 05:37 PM UTC
This incident has been resolved.