Is Fivetran down?

Last checked 4m ago
Current status
Fivetran is up

No incidents right now.

Get alerts when Fivetran breaks →

Free · no credit card

Official status page: https://status.fivetran.com · Polled every 5 minutes · 756 components tracked

Real-time Fivetran status, recent outages, and incident history — pulled directly from Fivetran's official status page at https://status.fivetran.com every 5 minutes. Pingoru tracks 756 Fivetran services and has captured 50 incidents in the last 90 days (99.92% uptime). Get email, Slack, Discord, or webhook alerts the moment Fivetran reports a new incident — free for 5 monitors, no credit card.

Users who monitor Fivetran also follow these Analytics services: New Relic Grafana Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 6,000+ providers
Fivetran uptime 99.92% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. 3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
    Resolved 4h 17m
    Started Apr 28, 2026, 06:15 PM UTC · Resolved Apr 28, 2026, 10:32 PM UTC
    Amazon Selling Partner
    4 updates · show timeline
    • identified · Apr 28, 2026, 06:15 PM UTC

      The issue has been identified and we are working to resolve it.

    • identified · Apr 28, 2026, 06:35 PM UTC

      We are currently seeing an increase in 500 Internal Server Error responses due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. This is a third-party issue on ASP's side, and we are continuing to monitor the connections. ASP Status Page: https://sellercentral.amazon.com/sp-api-status

    • monitoring · Apr 28, 2026, 06:54 PM UTC

      The connections are recovering and we are currently monitoring the syncs.

    • resolved · Apr 28, 2026, 10:32 PM UTC

      This incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. Incident Summary Description: We identified an issue with Amazon Selling Partner connections where syncs were failing with 500 Internal Server Error. Timeline: This issue began on 2026-04-28 at 17:39:00 UTC and was resolved on 2026-04-28 at 19:38:00 UTC. Cause: The failures were caused by a source-side outage in the Amazon Selling Partner API, resulting in 500 Internal Server Error responses. Resolution: No action was taken from our end. The issue was resolved on the source side, and syncs recovered automatically.

    Latest: This incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. Incident Summary Description: We identified an issu…

  2. 3rd Party: Qualtrics connector syncs failing with error "Ticket export failed."
    Resolved 2h 48m
    Started Apr 28, 2026, 03:05 PM UTC · Resolved Apr 28, 2026, 05:54 PM UTC
    Qualtrics
    4 updates · show timeline
    • identified · Apr 28, 2026, 03:05 PM UTC

      The issue has been identified and we are working to resolve it.

    • identified · Apr 28, 2026, 03:41 PM UTC

      Sync failures are occurring due to an outage in Qualtrics’ Ticket Export API. We are monitoring the situation. For more details, please visit: https://status.qualtrics.com/incidents/wj65y7rwfx2j

    • monitoring · Apr 28, 2026, 04:25 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 28, 2026, 05:54 PM UTC

      Instance rates have returned to normal levels, and affected connectors are now syncing successfully. Incident Summary Description: We identified an issue with Qualtrics connections where syncs were failing with a "Ticket export failed" error. Timeline: The issue began on April 28, 2026 at 11:30 AM UTC and was resolved at 4:10 PM UTC. Cause: The failures were caused by an issue with the Ticket Export endpoint on the Qualtrics side, leading to sync disruptions. More details: https://status.qualtrics.com/incidents/wj65y7rwfx2j Resolution: The issue was resolved once Qualtrics fixed the problem on their end.

    Latest: Instance rates have returned to normal levels, and affected connectors are now syncing successfully. Incident Summary Description: We identified an issue with Qualtrics connections…

  3. Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
    Resolved 13h 46m
    Started Apr 28, 2026, 01:10 AM UTC · Resolved Apr 28, 2026, 02:57 PM UTC
    Microsoft ListsSharePoint
    5 updates · show timeline
    • identified · Apr 28, 2026, 09:50 AM UTC

      The issue has been identified and we are working to resolve it.

    • identified · Apr 28, 2026, 09:51 AM UTC

      Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.

    • monitoring · Apr 28, 2026, 09:52 AM UTC

      A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.

    • monitoring · Apr 28, 2026, 10:26 AM UTC

      We have updated all the regions with the new secret keys and will continue to monitor the connections.

    • resolved · Apr 28, 2026, 02:57 PM UTC

      This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for SharePoint and Microsoft Lists connections which resulted in syncs failing with a "Authentication failed: The client secret or certificate has expired" error. Timeline: This issue began on 2026-04-27 at 22:20:00 UTC and was resolved on 2026-04-28 at 09:30:00 UTC Cause: The issue occurred due to Microsoft OAuth app credentials expiration.Due to this internal workflows failed to rotate the secret keys. Resolution: A fix has been implemented to update these secrets.

    Latest: This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description:…

  4. Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
    Resolved 5h 9m
    Started Apr 28, 2026, 01:10 AM UTC · Resolved Apr 28, 2026, 06:20 AM UTC
    General Services
    5 updates · show timeline
    • identified · Apr 28, 2026, 01:10 AM UTC

      The issue has been identified and we are working to resolve it.

    • identified · Apr 28, 2026, 01:45 AM UTC

      Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.

    • monitoring · Apr 28, 2026, 03:20 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Apr 28, 2026, 03:21 AM UTC

      A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.

    • resolved · Apr 28, 2026, 06:20 AM UTC

      We have resolved this incident.

    Latest: We have resolved this incident.

  5. 3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
    Resolved 2h 17m
    Started Apr 28, 2026, 12:45 AM UTC · Resolved Apr 28, 2026, 03:03 AM UTC
    Amazon Selling Partner
    4 updates · show timeline
    • identified · Apr 28, 2026, 12:45 AM UTC

      The issue has been identified and we are working to resolve it.

    • identified · Apr 28, 2026, 12:55 AM UTC

      We are currently seeing an increase in 500 Internal Server Error responses due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. This is a third-party issue on ASP's side, and we are continuing to monitor the connections. ASP Status Page: https://sellercentral.amazon.com/sp-api-status

    • monitoring · Apr 28, 2026, 02:15 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 28, 2026, 03:03 AM UTC

      This incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. Incident Summary Description: We identified an issue with Amazon Selling Partner connections where syncs were failing with 500 Internal Server Error. Timeline: This issue began on 2026-04-27 at 23:30:00 UTC and was resolved on 2026-04-28 at 02:15:00 UTC. Cause: The failures were caused by a source-side outage in the Amazon Selling Partner API, resulting in 500 Internal Server Error responses. Resolution: No action was taken from our end. The issue was resolved on the source side, and syncs recovered automatically.

    Latest: This incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. Incident Summary Description: We identified an issu…

See the full Fivetran outage history

45 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 32 incidents
  • 3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error Resolved
    Started Apr 28, 2026, 06:15 PM UTC · Resolved Apr 28, 2026, 10:32 PM UTC · 4h 17m
  • 3rd Party: Qualtrics connector syncs failing with error "Ticket export failed." Resolved
    Started Apr 28, 2026, 03:05 PM UTC · Resolved Apr 28, 2026, 05:54 PM UTC · 2h 48m
  • Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired" Resolved
    Started Apr 28, 2026, 01:10 AM UTC · Resolved Apr 28, 2026, 02:57 PM UTC · 13h 46m
  • Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired" Resolved
    Started Apr 28, 2026, 01:10 AM UTC · Resolved Apr 28, 2026, 06:20 AM UTC · 5h 9m
  • 3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error Resolved
    Started Apr 28, 2026, 12:45 AM UTC · Resolved Apr 28, 2026, 03:03 AM UTC · 2h 17m
  • 3rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changes Resolved
    Started Apr 27, 2026, 08:38 AM UTC · Resolved Apr 27, 2026, 04:00 PM UTC · 7h 21m
  • 3rd Party: Multiple Quickbooks connections sync failed due to source maintenance Resolved
    Started Apr 26, 2026, 07:00 AM UTC · Resolved Apr 26, 2026, 07:02 AM UTC · 2m
  • 3rd Party: Multiple Twitter Ads connections failing due to 500 errors Resolved
    Started Apr 25, 2026, 10:55 PM UTC · Resolved Apr 26, 2026, 01:30 PM UTC · 14h 35m

See Fivetran in your Pingoru dashboard

Monitor Fivetran alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Fivetran to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Fivetran incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Fivetran or see every provider at once.

Maintenance calendar

Scheduled Fivetran maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Fivetran status change, one inbox

Pingoru watches Fivetran's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Fivetran reports on 756 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Fivetran alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Fivetran maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Fivetran services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Fivetran from the same account, with per-user notification preferences for any monitor.

Get notified on Fivetran status changes

Pingoru watches Fivetran's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Fivetran free

Monitor Fivetran along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Fivetran and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Fivetran uptime & incident history

See 90 days of Fivetran uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Fivetran uptime history

Frequently asked questions

What is Fivetran's uptime?
Over the last 90 days, Fivetran reported 99.92% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.fivetran.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Fivetran's uptime history rolling forward in real time.
Has Fivetran had outages in 2026?
Yes — Fivetran has had 50 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Fivetran outage?
The most recent Fivetran incident was "3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.fivetran.com. See the full incident card above for affected components and the update timeline.
How often does Fivetran have outages?
Based on the last 90 days, Fivetran averages 16.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Fivetran's status page?
Fivetran's official status page is https://status.fivetran.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Fivetran down right now?
Fivetran is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Fivetran reports a change. Current status is based on 756 tracked services.
How does Pingoru know if Fivetran is down?
We read https://status.fivetran.com directly, using Fivetran's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Fivetran has an outage?
Create a free Pingoru account and add Fivetran as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Fivetran's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Fivetran incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Fivetran issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Fivetran status?
We use Fivetran's own status page at https://status.fivetran.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Fivetran components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Fivetran's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Fivetran free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →