Skip to content
Back to FivetranIncident Postmortem
Fivetran logo

Fivetran

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Fivetran: vendor-reported incident on September 24 (tracked 1h 30m)

Sep 24, 10:50 PM → Sep 25, 12:21 AM · 1h 30m · medium

Fivetran reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 30m, from Thu, 24 Sep 2026 22:50:47 GMT to Fri, 25 Sep 2026 00:21:08 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 30m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 24, 10:50 PM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Sep 24, 10:50 PM

    Status updated: possible issue

  3. Sep 25, 12:21 AM

    PulseWatch closed the incident

Official updates

  1. Sep 24, 10:50 PM

    Fivetran reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback