Hevo incident

Degraded performance in US2 [AWS, Oregon (us-west-2)] cluster

Minor Resolved View vendor source →
Started
Feb 04, 2026, 04:44 PM UTC
Resolved
Feb 04, 2026, 05:37 PM UTC
Duration
52m
Detected by Pingoru
Feb 04, 2026, 04:44 PM UTC

Affected components

SourcesData Pipelines

Update timeline

  1. 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.

  2. investigating Feb 04, 2026, 04:45 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. identified Feb 04, 2026, 05:02 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Feb 04, 2026, 05:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Feb 04, 2026, 05:37 PM UTC

    This incident has been resolved.

Looking to track Hevo downtime and outages?

Pingoru polls Hevo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Hevo reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Hevo alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Hevo for free

5 free monitors · No credit card required