Degraded / minor incident Fivetran status
fivetran.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Fivetran's status page shows “Degraded / minor incident” in Shopify and Stripe; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Degraded / minor incident · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Shopify, Stripe, Stripe test mode
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 23 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 1 h 12 min |
Evidence
- Official page: Degraded / minor incident (“Minor Service Outage”). evidence confidence: high
- Vendor stage: resolved on “Fivetran: Shopify Quickstart Transformations are failing to run with status as 'unavailable'”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Fivetran's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Fivetran. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Fivetran, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Fivetran. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Fivetran: Shopify Quickstart Transformations are failing to run with status as 'unavailable'
minor resolved · started · resolved
12 updates
- identified
The issue has been identified and we are working to resolve it.
- identified
We have identified a configuration issue that unexpectedly switched Shopify connections from the legacy schema to the GraphQL schema, also affecting associated Quickstart transformations. This impacts legacy-schema connections created after October 16, 2025, that synced while the configuration change was active. We have reverted the configuration change and are currently working on identifying affected connections that require additional corrections to restore their expected schema settings. This will also help to fix the transformations issue. We will provide another update as more information becomes available. Next Expected Update: 1 hour
- identified
We have created a hotfix to restore the legacy-schema. Once deployed, we will roll out the fix gradually and monitor the affected connections. Following the schema corrections, we will assess the data synced during the affected period to determine whether any additional recovery steps are required. We will provide another update as more information becomes available. Next Expected Update: 1 hour
- identified
Hotfix to restore the legacy-schema via feature flag has been deployed and we are currently testing the changes. We will roll out the feature flag gradually and monitor the affected connections. Next Expected Update: 1 hour
- identified
Team is continuing to test the changes and working on feature flag rollout as well. We will provide another update as more information becomes available. Next Expected Update: 1 hour
- identified
We are continuing to validate the fix to ensure the legacy schema is restored as expected before expanding the rollout. We will share another update as more information becomes available. Next Expected Update: 1 hour
- identified
Testing of the hotfix remains in progress as we validate that the legacy schema and associated Quickstart transformations are restored as expected. We are also continuing preparations for the gradual rollout and will share further updates as they become available. **Next Expected Update:** 1 hour
- identified
We started rolling out the fix to affected connections in batches. We will continue monitoring the affected connections and provide another update once the rollout is complete. **Next Expected Update:** 1 hour
- identified
The rollout is complete, and the fix is enabled for all affected connections; their schemas will be corrected during their next sync. We are preparing a targeted backfill with an additional buffer around the affected timeframe to ensure the relevant data is reprocessed. We will provide another update as this work progresses. **Next Expected Update:** 1 hour
- identified
The fix remains enabled for all affected connections, and we are monitoring their subsequent syncs. Preparation for the targeted cursor resets covering the affected timeframe is still in progress. **Next Expected Update:** 1 hour
- monitoring
We have deployed a fix for this issue. The schemas for all affected connections will start being corrected during the next sync, after which the transformations will run normally for all objects. We will continue to monitor all affected connectors until they resume normal sync functionality. Next expected update: In 3 hours.
- resolved
This incident has been resolved, and the transformation jobs are now running smoothly. We confirmed that all affected connections have returned to the legacy schema. <b>Incident Summary</b> Description: A configuration issue unexpectedly switched Shopify connections from the legacy schema to the GraphQL schema, affecting associated Quickstart transformations. The issue affected legacy-schema connections created after October 16, 2025, that synced while the configuration change was active. This caused data integrity issues, including additional tables and columns syncing to destinations and some data appearing as NULL. Timeline: The issue began on October 28 at 7:59 AM UTC and was resolved on October 29 at 02:11 PM UTC. Cause: A recent change on our end unintentionally switched the affected connections to the GraphQL schema. Resolution: We reverted the change and released a hotfix to retu
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.