Vendor Status Watch

← all vendors

Hevo status history

Current state: operational — “All Systems Operational” per https://status.hevodata.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
4incidents, last 90 days
29incidents on record
Incidents per week, last 12 weeks:

How long do Hevo incidents last?

3.8 hmedian incident duration29 measured
22.7 h90th percentile1 in 10 ran longer
12.6 hmedian, major/critical only5 incidents

From 29 incidents with a vendor-posted start and resolve time. Longest on record: Ingestion Lag Issue — 5.7 days (2026-05-09 18:48 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (29)

StartedIncidentStatusImpactDuration
2026-08-02 16:20 UTCDegraded performance in US clusterresolvedminor10 h 24 min
2026-07-30 06:37 UTCGoogle Ads Pipeline Failures Affecting Ad Group and Campaign Objectsresolvedmajor22 h 43 min
2026-07-19 09:43 UTCMeta Ads API Degraded Performanceresolvednone16 min
2026-07-16 08:38 UTCUI Services Down due to AWS outageresolvedminor3 h 13 min
2026-06-17 14:30 UTCConnection Failures for Redshift > Sources/Destinations configured with SSH tunnelresolvedmajor16 h 07 min
2026-06-12 14:31 UTCFacebook Ads Source Connectors Failureresolvedmajor1 h 37 min
2026-06-04 13:15 UTCEvent Processing Delays of Up to 30 Minutes.resolvednone0 min
2026-05-11 12:09 UTCDegraded performance in Asia regionresolvedminor1 h 37 min
2026-05-09 18:48 UTCIngestion Lag Issueresolvednone5 d 17 h
2026-04-23 00:52 UTCDegraded Performance in the US-GCP Regionresolvedminor2 h 00 min
2026-04-16 14:23 UTCSome Redshift destinations are failing, impacting data loads.resolvedminor2 h 59 min
2026-04-15 03:42 UTCDegraded Performance in the US-GCP Regionresolvedminor4 h 40 min
2026-03-05 07:29 UTCDegraded Performance in the US Regionresolvedminor3 min
2026-02-11 09:40 UTCDegraded Job Monitoring Performance in the US Regionresolvedminor8 h 13 min
2026-02-04 16:44 UTCDegraded performance in US2 [AWS, Oregon (us-west-2)] clusterresolvedminor52 min
2026-01-28 07:56 UTCStripe Source - Issue Ingesting Charge/Refund Objects Dataresolvedminor9 h 27 min
2026-01-21 11:57 UTCSnowflake destination failure for EU and US regionresolvedmajor8 h 54 min
2025-12-22 13:45 UTCDegraded performance for data pipelinesresolvedminor3 h 49 min
2025-12-16 07:31 UTCSnowflake Outage Impacting Hevo's Loading Jobsresolvedminor9 h 27 min
2025-12-11 04:23 UTCDegraded performance in US Clusterresolvedminor46 min
2025-12-03 21:05 UTCDegraded performance in USGCPresolvedminor1 h 04 min
2025-12-02 09:52 UTCDegraded pipeline performance in US clusterresolvedmajor12 h 37 min
2025-11-19 07:45 UTCDegraded UI issue: Quick alerts (🔔) are inaccessibleresolvedminor6 h 22 min
2025-11-16 16:20 UTCBigQuery Destination Setup Buttons Unresponsiveresolvedminor22 h 56 min
2025-10-24 06:59 UTCGoogle Ads source: Issue while fetching "campaign" reportsresolvedminor2 d 0 h
2025-10-21 15:59 UTCService Disruption Due to AWS Outageresolvednone0 min
2025-10-03 16:09 UTCObservability Degradation – Job Monitoringresolvedminor2 h 31 min
2025-08-20 05:38 UTCUI Metrics Disruption – Ingestion, Loading, and Billing UI metrics in US, US2, US-GCP Regionsresolvedminor2 h 41 min
2025-08-13 08:20 UTCDegraded performance with US cluster.resolvedminor4 h 07 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Hevo with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "hevo"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}