Fivetran uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
100%free of major or critical incidents, last 30 days*
100%free of major or critical incidents, last 90 days*
88.00%free of any incident, last 90 days
17incidents started, last 90 days
* Our archive of Fivetran’s status page starts , so the window is shorter.
Last 90 days, by UTC day
Aug 7 (UTC day): before our archive of this status page startsAug 8 (UTC day): before our archive of this status page startsAug 9 (UTC day): before our archive of this status page startsAug 10 (UTC day): before our archive of this status page startsAug 11 (UTC day): before our archive of this status page startsAug 12 (UTC day): before our archive of this status page startsAug 13 (UTC day): before our archive of this status page startsAug 14 (UTC day): before our archive of this status page startsAug 15 (UTC day): before our archive of this status page startsAug 16 (UTC day): before our archive of this status page startsAug 17 (UTC day): before our archive of this status page startsAug 18 (UTC day): before our archive of this status page startsAug 19 (UTC day): before our archive of this status page startsAug 20 (UTC day): before our archive of this status page startsAug 21 (UTC day): before our archive of this status page startsAug 22 (UTC day): before our archive of this status page startsAug 23 (UTC day): before our archive of this status page startsAug 24 (UTC day): before our archive of this status page startsAug 25 (UTC day): before our archive of this status page startsAug 26 (UTC day): before our archive of this status page startsAug 27 (UTC day): before our archive of this status page startsAug 28 (UTC day): before our archive of this status page startsAug 29 (UTC day): before our archive of this status page startsAug 30 (UTC day): before our archive of this status page startsAug 31 (UTC day): before our archive of this status page startsSep 1 (UTC day): before our archive of this status page startsSep 2 (UTC day): before our archive of this status page startsSep 3 (UTC day): before our archive of this status page startsSep 4 (UTC day): before our archive of this status page startsSep 5 (UTC day): before our archive of this status page startsSep 6 (UTC day): before our archive of this status page startsSep 7 (UTC day): before our archive of this status page startsSep 8 (UTC day): before our archive of this status page startsSep 9 (UTC day): before our archive of this status page startsSep 10 (UTC day): before our archive of this status page startsSep 11 (UTC day): before our archive of this status page startsSep 12 (UTC day): before our archive of this status page startsSep 13 (UTC day): before our archive of this status page startsSep 14 (UTC day): before our archive of this status page startsSep 15 (UTC day): before our archive of this status page startsSep 16 (UTC day): before our archive of this status page startsSep 17 (UTC day): before our archive of this status page startsSep 18 (UTC day): before our archive of this status page startsSep 19 (UTC day): before our archive of this status page startsSep 20 (UTC day): before our archive of this status page startsSep 21 (UTC day): before our archive of this status page startsSep 22 (UTC day): before our archive of this status page startsSep 23 (UTC day): before our archive of this status page startsSep 24 (UTC day): before our archive of this status page startsSep 25 (UTC day): before our archive of this status page startsSep 26 (UTC day): before our archive of this status page startsSep 27 (UTC day): before our archive of this status page startsSep 28 (UTC day): before our archive of this status page startsSep 29 (UTC day): before our archive of this status page startsSep 30 (UTC day): before our archive of this status page startsOct 1 (UTC day): before our archive of this status page startsOct 2 (UTC day): before our archive of this status page startsOct 3 (UTC day): before our archive of this status page startsOct 4 (UTC day): before our archive of this status page startsOct 5 (UTC day): before our archive of this status page startsOct 6 (UTC day): before our archive of this status page startsOct 7 (UTC day): before our archive of this status page startsOct 8 (UTC day): 0 min with a major or critical incident open, 3 h 30 min with any incident open, 1 incident startedOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): 0 min with a major or critical incident open, 1 h 3 min with any incident open, 2 incidents startedOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): 0 min with a major or critical incident open, 4 h 51 min with any incident open, 2 incidents startedOct 16 (UTC day): 0 min with a major or critical incident open, 6 h 39 min with any incident open, 1 incident startedOct 17 (UTC day): 0 min with a major or critical incident open, 7 h 30 min with any incident openOct 18 (UTC day): 0 min with a major or critical incident open, 20 min with any incident open, 1 incident startedOct 19 (UTC day): 0 min with a major or critical incident open, 3 h 59 min with any incident open, 1 incident startedOct 20 (UTC day): 0 min with a major or critical incident open, 40 min with any incident open, 1 incident startedOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): no vendor-reported incident openOct 23 (UTC day): 0 min with a major or critical incident open, 3 h 46 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): 0 min with a major or critical incident open, 21 h 9 min with any incident open, 2 incidents startedOct 30 (UTC day): 0 min with a major or critical incident open, 18 h 50 min with any incident open, 3 incidents startedOct 31 (UTC day): 0 min with a major or critical incident open, 2 h 4 min with any incident open, 1 incident startedNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 0 min with a major or critical incident open, 2 h 40 min with any incident open, 1 incident startedNov 3 (UTC day): 0 min with a major or critical incident open, 6 min with any incident openNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days* | 100% | 88.00% | 0 min | 3.2 days | 17 |
| Last 90 days* | 100% | 88.00% | 0 min | 3.2 days | 17 |
This is what Fivetran itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: Fivetran status history · last 90 days · Fivetran status page (opens in new tab) · Markdown