Is Fivetran Down?

No — Fivetran is up

Fivetran's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 248 ms

Right now

We could not read Fivetran's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

fivetran.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 248 ms
Checked: 3 hours ago

By region

Ashburn reachable, 184 ms
Chicago reachable, 187 ms
Johannesburg reachable, 549 ms
London reachable, 110 ms
Los Angeles reachable, 170 ms
Singapore reachable, 309 ms
São Paulo reachable, 233 ms
Tokyo reachable, 249 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	121 ms	1 ms	21 ms	181 ms
Chicago	92 ms	1 ms	11 ms	185 ms
Johannesburg	248 ms	1 ms	7 ms	547 ms
London	50 ms	2 ms	9 ms	105 ms
Los Angeles	78 ms	2 ms	9 ms	167 ms
Singapore	223 ms	1 ms	32 ms	307 ms
São Paulo	174 ms	2 ms	12 ms	231 ms
Tokyo	132 ms	1 ms	9 ms	245 ms

We check that fivetran.com loads, not every feature behind it. Test it yourself

History

Fivetran website availability

Measured by FlareWarden · fivetran.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 220ms

Last 30 days

67-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of fivetran.com from multiple regions every 6 hours. Fivetran's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 67 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Fivetran itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Fivetran goes down

We check Fivetran every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required