Skip to content
PulseWatchOUTAGE.INTEL
Fivetran logo

Other

Is Fivetran down right now?

NormalOfficial status last polled Sep 28, 2026 09:28 UTCwww.fivetran.comOfficial status page

Are you on the Fivetran team and see something inaccurate? Report it to us. We respond within one business day.

Is Fivetran down right now?

No. Fivetran has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 10:19 UTC

Normal

Fivetran is operating normally

As of Sep 28, 2026 10:19 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 27, 2026 04:51 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Fivetran.

11

Incident days

19

No recorded incident

40h 34m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Fivetran. Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

11

Days with incidents

2 incidents

Busiest day

40h 34m

Recorded duration

Report volume

0 reports in last 24H

10:15 AM01:45 PM05:15 PM08:45 PM12:15 AM03:45 AM07:15 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Fivetran outage on September 27 — 1h 29m disruption

Sep 27, 03:21 AM → Sep 27, 04:51 AM · 1h 29m · medium

Fivetran experienced a service disruption. The incident was detected by automated monitoring systems. Service was fully restored on September 27, 2026, at 04:51 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
1h 29m
until recovery

Impact

During the 1 hour and 29 minute disruption, Fivetran experienced a medium-severity service outage. This incident was identified through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-facing features or regions were identified as impacted through user reports.

Outage timeline

  1. Sep 27, 03:21 AM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Sep 27, 03:21 AM

    Status updated: possible issue

  3. Sep 27, 04:51 AM

    Signals cleared — incident resolved

Official updates

  1. Sep 27, 03:21 AM

    Fivetran status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

94.4%

90-day uptime

98.1%

Calculated from Fivetran's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/27/2026, 3:21:13 AM · 1h 29m

03:21 AM04:51 AM
Detection9/27/2026, 3:21:13 AM · 1d ago

Detected — medium severity

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/25/2026, 1:51:05 PM · 13h 30m

01:51 PM03:21 AM
Detection9/25/2026, 1:51:05 PM · 2d ago

Detected — medium severity

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/24/2026, 10:50:47 PM · 1h 30m

10:50 PM12:21 AM
Detection9/24/2026, 10:50:47 PM · 3d ago

Detected — medium severity

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/23/2026, 4:50:37 AM · 2h 55m

04:50 AM07:46 AM
Detection9/23/2026, 4:50:37 AM · 5d ago

Detected — medium severity

Fivetran: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Fivetran: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/18/2026, 10:45:28 AM · 4h 25m

10:45 AM03:10 PM
Detection9/18/2026, 10:45:28 AM · 9d ago

Detected — medium severity

Fivetran: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Fivetran enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Official status page polled; no gradeable history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.fivetran.com