Skip to main content

Is Fivetran Down?

No — Fivetran is up

Reachable from all 8 checked regions

Average response time: 55ms

Last checked · checks run every 6 hours

Official status page: https://status.fivetran.com

Fivetran uptime

100%
Last 7 days
Last 30 days
Last 90 days
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 6 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

6-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: 100.00% uptime, 24 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
48ms
DNS 0ms TCP 2ms TLS 9ms TTFB 42ms
arn
118ms
DNS 0ms TCP 1ms TLS 13ms TTFB 112ms
bom
55ms
DNS 0ms TCP 3ms TLS 12ms TTFB 41ms
cdg
45ms
DNS 0ms TCP 1ms TLS 10ms TTFB 39ms
dfw
42ms
DNS 0ms TCP 1ms TLS 7ms TTFB 36ms
ewr
67ms
DNS 1ms TCP 3ms TLS 13ms TTFB 53ms
sjc
44ms
DNS 0ms TCP 3ms TLS 10ms TTFB 38ms
syd
32ms
DNS 0ms TCP 1ms TLS 6ms TTFB 27ms
yyz
36ms
DNS 0ms TCP 1ms TLS 9ms TTFB 31ms

What Fivetran does

Fivetran moves data out of SaaS applications, databases and files into a warehouse or lake, managing the connectors and schema changes itself. Data teams use it to keep Snowflake, BigQuery or Databricks populated without maintaining pipeline code. Dashboards, reverse-ETL syncs and anything modelled downstream in dbt inherit whatever delay a Fivetran incident introduces.

What an outage looks like

Syncs stop advancing and connectors sit in a running state without completing, so warehouse tables hold yesterday's data while queries still succeed. The dashboard is slow or will not load connector history. Setting up or reauthorising a connector fails. The quiet symptom is the dangerous one: reports look fine because they return rows, just stale ones.

What to do about it

Check status.fivetran.com, which renders in the browser rather than in a plain fetch. Tell anyone reading dashboards that the numbers are stale, since nothing in a BI tool signals a paused pipeline. Avoid re-running syncs or rotating credentials mid-incident, which adds load and can complicate the catch-up once the platform recovers.

Is it down for everyone, or just you?

If this page says Fivetran is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Fivetran outage FAQ

How do I tell a Fivetran outage from one broken connector?
Scope tells you. A single connector failing, especially just after a source changed credentials or schema, is usually that connector. Several unrelated connectors stalling at once, across different sources, points at the platform. The status page settles it, and the dashboard's sync history shows whether the pause began at the same moment across pipelines.
Will I lose data if a sync is interrupted?
Loss is unlikely; delay is the real cost. Fivetran syncs run on a schedule, so rows created during an incident generally arrive on a later run rather than never. What does need attention is anything downstream that already ran against incomplete data, such as a dbt model or a report sent on a fixed schedule to people who will act on it.
Why do my dashboards look fine during a Fivetran outage?
Because a BI tool queries the warehouse, not the pipeline. The tables are still there and still answer queries; they just stop gaining new rows. Nothing in the chart signals that the underlying data stopped updating, which is why a stalled pipeline is often noticed a day late. Say so explicitly to the people reading the numbers.
Does a Fivetran incident affect Snowflake or BigQuery?
No. The warehouse keeps running and serving queries; only the loading of new data stops. If Snowflake or BigQuery is itself unavailable, Fivetran will also report failures writing to that destination, so the two can look similar from the dashboard. Check the destination's own status alongside Fivetran's before deciding which one to wait on.

How we measure this

  • We request Fivetran's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Fivetran publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Fivetran goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required