Is Hevo down?

Last checked just now
Current status
Hevo is up

No incidents right now.

Official status page: https://status.hevodata.com · Polled every 5 minutes · 84 components tracked

Hevo is operational right now. Last checked just now; the most recent incident resolved 42d ago.

Real-time Hevo status, recent outages, and incident history — pulled directly from Hevo's official status page at https://status.hevodata.com every 5 minutes. Pingoru tracks 84 Hevo services and has captured 5 incidents in the last 90 days (99.06% uptime). Get email, Slack, Discord, or webhook alerts the moment Hevo reports a new incident — free for 5 monitors, no credit card.

Users who monitor Hevo also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Hevo uptime 99.06% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 10h 24m
    Started Aug 02, 2026, 04:20 PM UTC · Resolved Aug 03, 2026, 02:45 AM UTC
    Data Pipelines
    Timeline · 3 updates
    • identified · Aug 02, 2026, 05:10 PM UTC

      The issue has been identified and we are working on a fix. Incident start time: 4:00 PM UTC

    • monitoring · Aug 02, 2026, 05:16 PM UTC

      A fix has been implemented, and we are monitoring the results. We identified an issue impacting data pipelines and models in the US region. As services recover, we expect data pipelines to experience up to 1 hour of processing lag. We will continue to monitor the recovery and provide further updates as needed.

    • resolved · Aug 03, 2026, 02:45 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 22h 43m
    Started Jul 30, 2026, 06:37 AM UTC · Resolved Jul 31, 2026, 05:21 AM UTC
    SourcesSourcesSourcesSourcesData PipelinesData PipelinesSourcesSourcesData PipelinesData Pipelines
    Timeline · 3 updates
    • identified · Jul 30, 2026, 06:37 AM UTC

      We are currently seeing failures in the Google Ads connector affecting the Ad Group and Campaign objects following the recent upgrade from version 21 to version 24. Our Engineering team has identified the root cause and is actively working on implementing a fix.

    • monitoring · Jul 31, 2026, 12:12 AM UTC

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

    • resolved · Jul 31, 2026, 05:21 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 16m
    Started Jul 19, 2026, 09:43 AM UTC · Resolved Jul 19, 2026, 10:00 AM UTC
    SourcesSourcesSourcesSourcesSourcesData PipelinesData PipelinesData PipelinesSourcesSources
    Timeline · 2 updates
    • monitoring · Jul 19, 2026, 09:43 AM UTC

      We observed degraded performance affecting the Meta Ads API from 08:42 - 09:30 UTC, which may have resulted in delayed data ingestion for Facebook Ads pipelines. The issue appears to be resolved, and services have returned to normal. We are continuing to monitor the situation closely.

    • resolved · Jul 19, 2026, 10:00 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 3h 13m
    Started Jul 16, 2026, 08:38 AM UTC · Resolved Jul 16, 2026, 11:51 AM UTC
    UI ConsoleUI ConsoleUI ConsoleUI ConsoleUI ConsoleUI Console
    Timeline · 4 updates
    • investigating · Jul 16, 2026, 08:38 AM UTC

      Current logs show that none of the backend processes are impacted. We are currently investigating the issue with UI.

    • identified · Jul 16, 2026, 09:13 AM UTC

      AWS is investigating the issue with Amazon CloudFront. For further details, please refer to the AWS STATUS PAGE: https://health.aws.amazon.com/health/status

    • monitoring · Jul 16, 2026, 11:19 AM UTC

      We are now observing healthy responses for requests routed through CloudFront, and the UI should be accessible across regions. The team is still monitoring this. Latest update from AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

    • resolved · Jul 16, 2026, 11:51 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 16h 7m
    Started Jun 17, 2026, 02:30 PM UTC · Resolved Jun 18, 2026, 06:38 AM UTC
    SourcesSourcesSourcesSourcesDestinationsDestinationsDestinationsDestinationsDestinations
    Timeline · 6 updates
    • investigating · Jun 17, 2026, 02:30 PM UTC

      We are currently observing Redshift destination failures across multiple accounts and regions. We have identified that the issue is currently impacting Redshift destinations connected via SSH. Affected pipelines may experience delays in data loading. Our engineering team is actively investigating the issue, and we will provide further updates.

    • identified · Jun 17, 2026, 05:16 PM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Jun 17, 2026, 06:40 PM UTC

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

    • identified · Jun 17, 2026, 10:37 PM UTC

      The fix is under deployment for the US (us-east-1) region. This should take another 2-3 hours for the pipelines to recover. Thanks for your patience in the meantime.

    • monitoring · Jun 17, 2026, 11:42 PM UTC

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

    • resolved · Jun 18, 2026, 06:38 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →