Fivetran Outage History
Fivetran is up right nowPingoru has recorded 100 incidents for Fivetran: 100 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 29 | 94 of 720 (13%) |
| May 2026 | 26 | 366 of 744 (49%) |
| June 2026 | 7 | 48 of 720 (7%) |
| July 2026 | 3 | 7 of 744 (1%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 9 (0%) |
Incidents, newest first
Minor July 10, 2026 3rd Party: Some Ramp connections failing with 529 response errors 1h 29m Ramp
Started Jul 10, 2026, 07:10 PM UTC· resolved Jul 10, 2026, 08:39 PM UTC
- identified Jul 10, 2026, 07:10 PM UTC
The issue has been identified and we are working to resolve it.
- identified Jul 10, 2026, 07:38 PM UTC
We have identified that the source API is repeatedly returning HTTP 529 responses, causing sync failures. We are actively working with the third-party source to resolve the issue and will continue to provide updates. Next Expected Update: 1 hour
- monitoring Jul 10, 2026, 08:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 10, 2026, 08:39 PM UTC
This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. Incident Summary Description: We identified an issue affecting Ramp connections that caused sync failures due to repeated HTTP 529 responses from the source API. Timeline: The issue began on 2026-07-10 at 16:50 UTC and was resolved on 2026-07-10 at 19:30 UTC. Cause: The source API was repeatedly returning HTTP 529 responses across multiple endpoints, resulting in sync failures. Resolution: No action was required from our side. The issue was resolved by the source, and affected connections recovered automatically once the source API resumed returning successful responses.
Minor July 7, 2026 3rd Party: QuickBooks connections failing with “Failed to sync 1 endpoint” error 2h 49m QuickBooks
Started Jul 07, 2026, 05:20 PM UTC· resolved Jul 07, 2026, 08:09 PM UTC
- identified Jul 07, 2026, 05:20 PM UTC
The issue has been identified and we are working to resolve it.
- identified Jul 07, 2026, 05:40 PM UTC
We have identified that the issue occurs when querying the CreditCardPaymentTxn entity. The source API is returning the following error: "invalid context declaration: creditcardpaymenttxn" This appears to be happening because the source may have changed the entity name from CreditCardPaymentTxn to CreditCardPayment. Our team is working on accommodating this change. Next Expected Update: 1 hour
- monitoring Jul 07, 2026, 07:07 PM UTC
We have deployed a fix for this issue by switching to the new entity for data retrieval for the table CreditCardPayment We will continue to closely monitor all affected connections until they have fully recovered and returned to normal sync operations. Next Expected Update: 1 Hour
- resolved Jul 07, 2026, 08:09 PM UTC
This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. Incident Summary Description: We identified an issue affecting QuickBooks connections that caused syncs to fail for the CreditCardPaymentTxn entity. Timeline: The issue began on 2026-07-07 at 2:00 PM UTC and was resolved on 2026-07-07 at 7:10 PM UTC. Cause: The QuickBooks query entity was changed from CreditCardPaymentTxn to CreditCardPayment, causing API requests made by the connector to fail with a 400 ValidationFault. Resolution: We made the required changes for the connector to use the new CreditCardPayment query entity. After deploying this change, the affected connectors recovered successfully, and syncs resumed normal operation.
Minor July 6, 2026 3rd Party: Some AppLovin connectors are failing 2h 29m AppLovin
Started Jul 06, 2026, 11:12 PM UTC· resolved Jul 07, 2026, 01:41 AM UTC
- identified Jul 06, 2026, 11:05 PM UTC
The issue has been identified and we are working to resolve it.
- identified Jul 06, 2026, 11:12 PM UTC
We have identified an issue with the AppLovin connector where syncs for the advertiser_report table are failing with HTTP 500 Internal Server Errors. This is caused by a query timeout on AppLovin's backend — the expanded column set being requested exceeds AppLovin's server-side query execution limit. We are actively working on a fix and will provide further updates.
- monitoring Jul 06, 2026, 11:45 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 07, 2026, 12:01 AM UTC
We have applied a fix that resolves the 500 internal server error for the advertiser_report table. Affected connectors should resume syncing normally. We are monitoring recovery across all affected accounts.
- resolved Jul 07, 2026, 01:41 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We have identified an issue with the AppLovin connector where syncs are failing with HTTP 500 Internal Server Error. Timeline: The issue began on July 6, 2026, at 8:30 PM UTC and was resolved on July 6, 2026, at 10:00 PM UTC. Cause: The failures were caused by a backend issue on AppLovin’s side, resulting in API requests timing out or returning HTTP 500 errors. Some syncs were also impacted by increased query complexity due to an expanded set of requested fields, which exceeded AppLovin’s server-side query execution limits. Resolution: AppLovin resolved the backend issue on their end, after which connections using the /skaReport endpoint began syncing successfully again. We rolled back the expanded column set for affected customers. This mitigation reduced query complexity and allowed impacted connections to resume syncing successfully
Minor June 19, 2026 Fivetran: Apple Search Ads connections are failing with error "HTTP 400 Bad Request" 4h 27m Apple Search Ads
Started Jun 19, 2026, 06:15 AM UTC· resolved Jun 19, 2026, 10:43 AM UTC
- identified Jun 19, 2026, 06:15 AM UTC
The issue has been identified and we are working to resolve it.
- identified Jun 19, 2026, 06:45 AM UTC
We have identified that this issue was caused by a recent change, and we are currently working on reverting the changes via a hotfix. Next Expected Update: 2 hours
- monitoring Jun 19, 2026, 08:30 AM UTC
A hotfix has been deployed, and the syncs are recovering. We will continue monitoring the syncs Next Expected Update: 3 hours
- resolved Jun 19, 2026, 10:43 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue in which Apple Search Ads connections were failing with the error "HTTP 400 Bad Request." Timeline: This issue began on June 18, 2026, at 17:47 UTC and was resolved on June 19, 2026, at 11:02 UTC. Cause: The issue was caused by a recent code change that introduced an unexpected error in Apple Search Ads connection processing. Resolution: Identified the problematic change and reverted it Following the change, affected Apple Search Ads connections resumed normal operation and the issue was fully resolved.
Minor June 17, 2026 Fivetran: Multiple Hybrid Deployment Connections are failing 5h 26m General Services
Started Jun 17, 2026, 12:40 PM UTC· resolved Jun 17, 2026, 06:06 PM UTC
- identified Jun 17, 2026, 12:40 PM UTC
We have identified an issue where Hybrid Deployment Connections are failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. We are currently investigating in more detail. Next Expected Update:
- identified Jun 17, 2026, 01:33 PM UTC
We have identified that this issue was caused by a recent change, and we are currently working on a HotFix. Next Expected Update: 1 hour
- identified Jun 17, 2026, 03:00 PM UTC
We are continuing to work on a fix for this issue. Next Expected Update: 1 hour
- monitoring Jun 17, 2026, 03:56 PM UTC
We have deployed a fix for this issue. We will continue to monitor all affected connectors until they resume their normal sync functionality. Next Expected Update: 3 hours
- resolved Jun 17, 2026, 06:06 PM UTC
Incident Summary Description: We identified an issue where Hybrid Deployment connections were failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. Timeline: This issue began on June 17, 2026, at 08:10 UTC and was resolved on June 17, 2026, at 15:50 UTC. Cause: A recent code change introduced an issue affecting Hybrid Deployment connectors, specifically Oracle HVA and SQL Server HVA connectors. As a result, sync jobs for impacted connectors would start and then fail. Resolution: We reverted the problematic change and deployed a hotfix. After the fix was deployed, affected connectors began recovering and syncs started succeeding again.
Minor June 14, 2026 3rd Party: Multiple Customer.io connections are failing with 5xx error 15h 52m General Services
Started Jun 14, 2026, 01:10 AM UTC· resolved Jun 14, 2026, 05:02 PM UTC
- identified Jun 14, 2026, 01:10 AM UTC
The issue has been identified and we are working to resolve it.
- identified Jun 14, 2026, 01:55 AM UTC
We identified that multiple REST API requests are failing with 502 Bad Gateway errors returned by the source API. We have reached out to the source regarding this. Next Expected Update: 1 hour
- identified Jun 14, 2026, 03:11 AM UTC
We are preparing a fix to skip the failing endpoints until the source resolves the issue. Next Expected Update: 1 hour
- monitoring Jun 14, 2026, 04:14 AM UTC
A hotfix has been deployed to skip the failing endpoints until the source resolves the issue. We will continue monitoring the connections while we wait for a response from the source team. Next Expected Update: 3 hours
- monitoring Jun 14, 2026, 07:00 AM UTC
We are continuing to monitor all affected connectors after the recent fix deployment. Next Expected Update:3 hours
- monitoring Jun 14, 2026, 10:36 AM UTC
We noticed that the connections were failing again with "502 Server Error". We've raised a hotfix, and the failures are gradually reducing. We're monitoring the affected connections. Next Expected Update:
- monitoring Jun 14, 2026, 03:18 PM UTC
We observed a shift in the issue behavior around 12:00 UTC for the Customer export api. While initial failures occurred during job creation, the connector is now failing during the report download phase. - We have implemented a skip mechanism to mitigate these 502 errors on the affected endpoints, and are continuing to closely monitor all active syncs. - Additionally, we reported the ongoing behavior to Customer.io, as their initial fix did not resolve the issue. We are currently awaiting their response. Next Expected Update:
- resolved Jun 14, 2026, 05:02 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 Customer.io, which resulted in syncs failing with a 502 HTTP error. Timeline: This issue began on 2026-06-13 20:26 UTC and was resolved on 2026-06-14 14:52 UTC. Cause: The issue was caused by intermittent upstream API failures on the Customer.io side. The root-cause behaviour fluctuated throughout the incident, shifting between generic server errors across multiple endpoints. Resolution: Fivetran implemented a skip-on-failure mechanism to bypass 502 HTTP errors and allow syncs to proceed. A permanent root-cause fix will be deployed by Customer.io.
Notice June 8, 2026 3rd Party: Failures Triggering Connection Syncs via API and Dashboard –
Started Jun 08, 2026, 10:00 PM UTC· resolved Jun 08, 2026, 10:00 PM UTC
- resolved Jun 09, 2026, 12:34 PM UTC
Description: We identified an issue affecting manual and API-triggered connection syncs, causing syncs to fail to start and return API errors. Timeline: This issue began on June 8, 2026, at 22:00 UTC and was resolved on June 8, 2026, at 22:35 UTC. Cause: The elevated API error count was caused by an incident with a third-party service used to orchestrate sync execution. As a result, requests to trigger connection syncs through both the API and the Fivetran dashboard were intermittently unsuccessful. Reference: https://status.temporal.io/incidents/8msytm7vpfbv Resolution: The third-party service provider resolved the underlying issue, restoring normal functionality. Following confirmation that sync triggering was operating as expected, the incident was closed. Customers can now successfully trigger syncs through both the API and the dashboard.
Minor June 7, 2026 3rd Party: Some Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" error 3h 14m Microsoft Advertising
Started Jun 07, 2026, 10:53 AM UTC· resolved Jun 07, 2026, 02:08 PM UTC
- identified Jun 07, 2026, 08:50 AM UTC
We have identified an issue where Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" exception. We are currently investigating in more detail. Next Expected Update:
- identified Jun 07, 2026, 10:53 AM UTC
We have performed an initial analysis and identified that the issue appears to be related to an incident with the Bing Ads Reporting API affecting the "GeographicPerformanceReport" report Next Expected Update:
- monitoring Jun 07, 2026, 01:30 PM UTC
The issue appears to have been resolved on the Microsoft end, and the affected connections are recovering. We will continue to monitor all affected connectors until they resume their normal sync functionality. Next Expected Update:
- resolved Jun 07, 2026, 02:08 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 with the Microsoft Advertising connections, which resulted in syncs failing with a "Report processing failed: (StreamProcessing)" error. Timeline: This issue began on June 7, 2026, at 05:00 UTC and was resolved on June 7, 2026, at 13:00 UTC. Cause: The connectors that were syncing Geographic Performance report tables in Microsoft Ads started failing consistently due to an issue with the Microsoft Ads API on Microsoft's end. Resolution: This has been automatically resolved on the Microsoft Ads API affecting the GeographicPerformanceReport, and the connectors are succeeding now.
Minor June 7, 2026 3rd Party: Some Impact Brand connections are failing with "HTTP 500 Internal server" error 50m General Services
Started Jun 07, 2026, 06:48 AM UTC· resolved Jun 07, 2026, 07:38 AM UTC
- identified Jun 07, 2026, 06:20 AM UTC
The issue has been identified and we are working to resolve it.
- identified Jun 07, 2026, 06:48 AM UTC
We identified that this issue is caused by the source API returning 500 Internal Server Errors, impacting the following tables: performance_by_partner, performance_by_day, adv_performance_by_ad_media_date. We have reached out to the source regarding this issue. We are also observing that affected connectors are recovering without any intervention from Fivetran. Next Expected Update:
- monitoring Jun 07, 2026, 07:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 07, 2026, 07:38 AM 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 with the Impact Brand connections, which resulted in syncs failing with 500 Internal Server Errors on the following reporting endpoints:performance_by_partner, performance_by_day, adv_performance_by_ad_media_date Timeline: This issue began on 2026-06-07 at 05:16:55 UTC and was resolved on 2026-06-07 at 19:00:55 UTC. Cause: The failure was caused by a server-side issue on the Impact source. Resolution: We reached out to the Impact source team to investigate the 500 Internal Server Errors. The issue has now been resolved on the Impact side, and no action was taken from Fivetran.
Minor June 3, 2026 3rd Party: Shopify connections are failing with a "HTTP 404 Not Found" error 1h 27m Shopify
Started Jun 03, 2026, 02:16 PM UTC· resolved Jun 03, 2026, 03:43 PM UTC
- identified Jun 03, 2026, 01:55 PM UTC
The issue has been identified and we are working to resolve it.
- identified Jun 03, 2026, 02:10 PM UTC
Our requests to multiple Shopify API endpoints are failing with 404 errors. There is an outage reported on the Shopify status page - https://my.shopifystatus.com/ Next Expected Update: 1 hour
- identified Jun 03, 2026, 02:13 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jun 03, 2026, 03:16 PM UTC
Update from Shopify: "We've identified the problem and are seeing recovery from our mitigation efforts. We will continue to monitor and update." We are seeing that Shopify connector syncs are now recovering. Next Expected Update: 3 hours
- resolved Jun 03, 2026, 03:43 PM UTC
This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue where Shopify connections were failing with an HTTP 404 Not Found error. Timeline: The issue began on 2026-06-03 at 13:10 UTC and was resolved on 2026-06-03 at 15:00 UTC. Cause: The failures were caused by an issue on Shopify's side, which resulted in unexpected API error responses. For more information, please refer to the Shopify Status Page: https://www.shopifystatus.com/incidents/gbqcx5fk01gz Resolution: No action was required from our side. The issue was resolved by Shopify, and affected syncs recovered automatically once the upstream issue was addressed.
Minor May 29, 2026 Fivetran: Hybrid Deployment Agent jobs failing to start with error "Connection pool shut down" 7h 19m General Services
Started May 29, 2026, 04:40 PM UTC· resolved May 29, 2026, 11:59 PM UTC
- identified May 29, 2026, 09:20 PM UTC
The Fivetran Hybrid Deployment Agent is experiencing an issue that may cause syncs to fail to start or connections to fail during setup tests and syncs. The error in the agent logs is "Return CreateJobResponse/Failure, Caused By User: false - CREATE_JOB_ERROR/Connection pool shut down {process_id=XXX}"
- identified May 29, 2026, 09:23 PM UTC
We have identified the root cause and have deployed a hot fix.
- identified May 29, 2026, 09:30 PM UTC
The hot fix should be reflected in the new HD agent images. For existing HD agents, restarting the controller should resolve the issue. Customers are advised to restart their controller with the following commands: cd ~/fivetran ./hdagent.sh stop ./hdagent.sh start
- monitoring May 29, 2026, 09:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 29, 2026, 11:59 PM UTC
This incident has been resolved.
Minor May 26, 2026 3rd Party: Google Display & Video 360 connections are failing with "HTTP 502 Bad Gateway" error 6h 28m General Services
Started May 26, 2026, 03:15 AM UTC· resolved May 26, 2026, 09:44 AM UTC
- identified May 26, 2026, 03:15 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 26, 2026, 07:50 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 26, 2026, 09:44 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue with Google Display & Video 360 connections, which resulted in syncs failing with an "HTTP 502 Bad Gateway" error. Timeline: This issue began on 2026-05-25 14:56 UTC and was resolved on 2026-05-26 at 04:38 UTC. Cause: The failures were caused by a third-party API side, resulting in HTTP 502 Bad Gateway error responses. There was no Incident reported by Google related to this service on their status page: https://ads.google.com/status/publisher/. Resolution: No action was taken from our end. The issue was resolved on the third-party side, and syncs recovered automatically.
Minor May 22, 2026 3rd Party: Multiple connection syncs are failing with an "Internal: Failed to read token" error. 11m General Services
Started May 22, 2026, 05:05 AM UTC· resolved May 22, 2026, 05:16 AM UTC
- identified May 22, 2026, 05:05 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 22, 2026, 05:05 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 22, 2026, 05:16 AM UTC
This incident has been resolved. Incident Summary Issue: Fivetran: Multiple connection syncs were failing with an Internal: Failed to read token error. Timeline: This issue began on May 22, 2026, at 02:47 UTC and was resolved on May 22, 2026, at 02:55 UTC. Root Cause: Calls to Firestore (a GCP service) failed due to transient network errors. Resolution: The transient issue affecting Firestore services has stabilised, and all affected Fivetran syncs have recovered and are operating normally.
Minor May 22, 2026 3rd Party: Multiple Salesforce and Salesforce Sandbox connections are failing with HTTP 503 Service Unavailable 2h 28m Salesforce
Started May 22, 2026, 02:35 AM UTC· resolved May 22, 2026, 05:04 AM UTC
- identified May 22, 2026, 01:20 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 22, 2026, 01:35 AM UTC
We have identified an issue where Salesforce connections are failing with an HTTP 503 Service Unavailable Exception. This is a third-party issue on the Salesforce side, and we are continuing to monitor the connections. Salesforce Status Page: https://status.salesforce.com/incidents/20004038
- monitoring May 22, 2026, 04:17 AM UTC
The issue from source side is resolved and we noticed that syncs are succeeding now. We are continuing to monitor the syncs.
- resolved May 22, 2026, 05:04 AM 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 Saleforce Connection which resulted in syncs failing with a HTTP 503 Service Unavailable error. Timeline: This issue began on 21 May 2026 at 20:00 UTC and was resolved on 22 May 2026 at 00:30 UTC. Cause: The failures were caused by a source-side outage in the Saleforce 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.
Minor May 22, 2026 3rd Party: Delay in User facing logs and External logs delivery 2h 7m General Services
Started May 22, 2026, 02:20 AM UTC· resolved May 22, 2026, 04:27 AM UTC
- identified May 22, 2026, 02:20 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 22, 2026, 02:45 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 22, 2026, 04:27 AM UTC
This incident has been resolved. Log processing delay is back to normal. Incident Summary Description: We identified an issue causing a delay in User facing logs and External logs delivery. Timeline: This issue began on 22nd May 00:00 UTC and was resolved on 22nd May 2:40 UTC. Cause: Misconfiguration in one of our services has caused the issue. Resolution: We have disabled the problematic part to fix the issue.
Minor May 21, 2026 Fivetran: Qualtrics connection syncs are failing with "HTTP 400 Bad Request" for the "TransactionBatches" endpoint 6h 51m Qualtrics
Started May 21, 2026, 07:53 AM UTC· resolved May 21, 2026, 02:45 PM UTC
- identified May 21, 2026, 06:25 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 21, 2026, 07:53 AM UTC
Syncs are intermittently failing with a "HTTP 400 Bad Request" error for the "TransactionBatches" endpoint due to an issue on the third-party side. We have reached out to Qualtrics support for more details on these failures. We are also exploring possible workarounds to mitigate the issue in the meantime.
- monitoring May 21, 2026, 11:42 AM UTC
A fix has been implemented from our end and we are monitoring the results.
- resolved May 21, 2026, 02:45 PM UTC
We have resolved this incident.
Minor May 20, 2026 3rd Party: Twitter Ads connections are failing with BadRequestException due to changes on the source side. 3h 46m General Services, X Ads
Started May 20, 2026, 06:50 PM UTC· resolved May 20, 2026, 10:36 PM UTC
- identified May 20, 2026, 06:50 PM UTC
The issue has been identified and we are working to resolve it.
- identified May 20, 2026, 06:53 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 20, 2026, 08:40 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 20, 2026, 10:36 PM UTC
This incident has been resolved.
Minor May 19, 2026 Fivetran: Multiple connection syncs are failing with a "Token not found" error 25m General Services
Started May 19, 2026, 08:50 AM UTC· resolved May 19, 2026, 09:15 AM UTC
- identified May 19, 2026, 10:15 AM UTC
The issue has been identified and we are working to resolve it.
- resolved May 19, 2026, 10:41 AM UTC
Description: We identified an issue where connections were intermittently failing with the error message: "UNAUTHENTICATED: Token not found". Timeline: The issue began on 2026-05-19 at 08:48 UTC and was resolved on 2026-05-19 at 09:10 UTC. During this period, customers may have experienced intermittent sync failures, with services recovering shortly afterwards. Root Cause: The issue was caused by failures within the scheduling layer due to an internal network disruption. This resulted in cascading failures across dependent connection services. Resolution: The affected connections recovered once network connectivity was restored. All services are currently operating normally.
Minor May 18, 2026 3rd Party: X Ads and X Organic Performance Degradation 39d 2h X Organic, X Ads
Started May 18, 2026, 04:41 PM UTC· resolved Jun 26, 2026, 07:18 PM UTC
- identified May 13, 2026, 06:41 PM UTC
X's async reporting API has been intermittently returning empty or zero-value data and experiencing a higher rate of Internal Server errors since approximately April 9, 2026. This affects all report tables in the Twitter Ads and Twitter Organic connectors. We have reported this issue to X Corp and are actively working with them toward a resolution.
- identified May 14, 2026, 03:37 PM UTC
We are continuing to observe HTTP 500 Internal Server Errors across both the X Ads and X Organic connectors. As a result, data ingestion for those endpoints is currently being skipped to avoid further processing failures. You will notice an alert on your dashboard for the same. However, we are no longer receiving empty reports for most report types. This issue currently persists only for ORGANIC_TWEET_REPORT. We are actively working with the X support team to resolve the remaining API issues. If you have started seeing the latest data in your reports tables and no longer see the "Stats Report Server Error" alert on your dashboard, you may perform a full resync to backfill any missing historical data.
- identified May 14, 2026, 10:20 PM UTC
Our team continues to work with X to address all known issues. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Monday, May 18, 2026
- identified May 18, 2026, 04:41 PM UTC
We are working to identify possible workarounds. In the meantime, we are continuing to communicate with the X team. We will continue to provide updates as soon as new information becomes available. Next expected update: Thursday, May 20th
- identified May 21, 2026, 04:48 PM UTC
The HTTP 500 Internal Server Errors across both the X Ads and X Organic connectors have been resolved. Reports without segmentation are syncing successfully with cursors advancing as expected. We continue to see data integrity issues with segmented tables. The API returns job results indicating that the `segment` field is null for some entities, causing those records to be dropped during upsert because `segment` is part of the primary key. This has been reported to X Corp along with multiple examples. We are continuing to actively work with X Corp toward a resolution Next Expected Update: Saturday, May 23rd.
- identified May 24, 2026, 03:43 AM UTC
Our team continues to work with X to address all known issues. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Tuesday, May 26, 2026
- identified May 26, 2026, 11:14 PM UTC
Our team continues to work with X to address all known issues. We have recently followed up with them regarding their progress. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Thursday, May 28, 2026
- identified May 28, 2026, 10:52 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Saturday, May 30th.
- identified May 30, 2026, 07:00 PM UTC
We are starting to see some improvements for jobs with null values in the segment field. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Tuesday, June 2, 2026
- identified Jun 03, 2026, 10:35 PM UTC
All reports have recovered, except for ORGANIC_TWEET_REPORT. Following a call with X Corp, we understand that they are working on a fix on their end. X Corp has assured us that Segmentation data after April 5th will soon be fixed for AGE, GENDER, PLATFORM, and METROS(DMA). X Corp has confirmed that they are still investigating the reported 500 and 503 exceptions, but do not have an update for us at this time. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Friday, June 5th, 2026
- identified Jun 05, 2026, 09:01 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 8, 2026
- identified Jun 09, 2026, 12:26 AM UTC
X Corp has assured us that Segmentation data will soon be fixed for AGE, GENDER, PLATFORM, and METROS(DMA). We will continue to provide updates as soon as new information becomes available. Next Expected Update: Wednesday, June 10th, 2026
- identified Jun 10, 2026, 10:42 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Friday, June 12, 2026
- identified Jun 12, 2026, 06:26 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 15, 2026
- identified Jun 15, 2026, 10:25 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Wednesday, June 17, 2026
- identified Jun 17, 2026, 04:02 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Friday, June 19, 2026
- identified Jun 19, 2026, 10:29 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 22, 2026
- identified Jun 23, 2026, 07:02 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. Next update will be on Wednesday, June 24th.
- identified Jun 24, 2026, 07:04 PM UTC
Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. Next update will be by or before June 26th.
- resolved Jun 26, 2026, 07:18 PM UTC
X has confirmed that the root cause originates within their API environment and they are actively working towards complete resolution. While the fix must be implemented on their side, Fivetran continues to actively work with X until all known issues are resolved. Affected Fivetran customers have been contacted. Fivetran will continue to send direct communications to affected customers as we have additional information, including once X reaches full resolution.
Minor May 18, 2026 Fivetran: Mutliple Amazon Ads connection syncs are faling with 'operationTimestamp' NullPointerException 1h 33m Amazon Ads
Started May 18, 2026, 07:05 AM UTC· resolved May 18, 2026, 08:38 AM UTC
- identified May 18, 2026, 07:05 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 18, 2026, 07:45 AM UTC
We are continuing to work on a fix for this issue.
- resolved May 18, 2026, 08:38 AM UTC
This incident has been resolved. We have observed that success rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue with Amazon Ads connections that caused syncs to fail with a 'operationTimestamp' NullPointerException. Timeline: This issue began on 18-05-2026 04:49 AM UTC and was resolved on 18-05-2026 08:08 AM UTC. Cause: A recent change related to Operations Consolidation introduced a regression, causing a null pointer exception and resulting in sync failures for affected Amazon Ads connectors. Resolution: We reverted the change that was causing the issue, after which syncs started succeeding.
Minor May 16, 2026 Fivetran: Facebook Pages connectors failing with MonetizationMetricUnavailableException 4h 19m Facebook Pages
Started May 16, 2026, 02:25 PM UTC· resolved May 16, 2026, 06:44 PM UTC
- identified May 16, 2026, 02:25 PM UTC
The issue has been identified and we are working to resolve it.
- identified May 16, 2026, 02:32 PM UTC
We have identified that this issue was caused by instability in newly introduced Facebook Pages monetization metrics and we are currently working on a fix.
- monitoring May 16, 2026, 04:21 PM UTC
We have deployed a fix for this issue. We will continue to monitor all affected connectors until they resume their normal sync functionality.
- resolved May 16, 2026, 06:44 PM UTC
This incident has been resolved. We have observed that instance rates have returned to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for Facebook Pages which resulted in syncs failing with an An unknown error has occurred error while fetching monetization metrics. Timeline: This issue began on 2026-05-15 at 16:30 UTC and was resolved on 2026-05-16 at 17:55 UTC. Cause: An added monetization metrics path in Facebook Pages was unstable and occasionally failed when Facebook returned a transient error, which caused syncs to fail. Resolution: We disabled monetization metrics processing for Facebook Pages connector, which stopped the failing requests and allowed affected connectors to recover.
Minor May 13, 2026 3rd Party: Multiple Apple App Store Connections are failing with `Reporter is currently unavailable` 2h 59m General Services, Apple App Store
Started May 13, 2026, 12:59 AM UTC· resolved May 13, 2026, 03:58 AM UTC
- identified May 13, 2026, 12:45 AM UTC
The issue has been identified and we are working to resolve it.
- investigating May 13, 2026, 12:59 AM UTC
We are investigating an issue impacting Apple App Store connections, where syncs are failing with the error: "Unknown failure. This request cannot be processed right now. Reporter is currently unavailable." We have reached out to Apple Support and are actively monitoring the syncs.
- monitoring May 13, 2026, 03:23 AM UTC
Connection syncs are succeeding, and we continue to monitor the connections closely.
- resolved May 13, 2026, 03:58 AM UTC
This incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue with the Apple App Store connection, which resulted in syncs failing with `Reporter is currently unavailable` Timeline: This issue began on 2026-05-12T22:32:00Z UTC and was resolved on 2026-05-13T02:45:00Z UTC. Cause: The issue was caused by the third-party, /v1/financeReports endpoint failing with "HTTP 503 SERVICE_UNAVAILABLE_ERROR: Reporter is currently unavailable. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Minor May 12, 2026 Fivetran: Delay in notifications/alerts on the Fivetran dashboard 22m General Services
Started May 12, 2026, 06:25 AM UTC· resolved May 12, 2026, 06:47 AM UTC
- identified May 12, 2026, 06:25 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 12, 2026, 06:35 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 12, 2026, 06:47 AM UTC
This incident has been resolved. Incident Summary Description: We identified an issue causing a delay in notifications/alerts on the Fivetran dashboard. Timeline: This issue began on 12th May 04:40 AM UTC and was resolved on 12th May 06:19 AM UTC. Cause: A recent code change on the Fivetran side has caused this issue. Resolution: The code change has been reverted to fix the issue.
Minor May 11, 2026 3rd Party: Typeform connections are failing with an error due to changes on the source side in the response for FORM_INSIGHT data. 3h 16m Typeform
Started May 11, 2026, 07:35 PM UTC· resolved May 11, 2026, 10:51 PM UTC
- identified May 11, 2026, 07:35 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 11, 2026, 09:05 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 11, 2026, 09:18 PM UTC
We have implemented a fix and are currently monitoring the results.
- resolved May 11, 2026, 10:51 PM UTC
This incident has been resolved, and syncs have recovered.
Minor May 10, 2026 Fivetran: Marketo Connections Experiencing Sync Failures 2h 28m Marketo
Started May 10, 2026, 10:10 AM UTC· resolved May 10, 2026, 12:39 PM UTC
- identified May 10, 2026, 10:10 AM UTC
The Marketo connections are failing with “PROGRAM_MEMBERSHIP: fields not specified” Error. The issue has been identified and we are working to resolve it.
- monitoring May 10, 2026, 12:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 10, 2026, 12:39 PM UTC
This incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: Affected Marketo connections experienced sync failures with error PROGRAM_MEMBERSHIP: fields not specified Timeline: This issue began on 2025-05-08 16:00:00 UTC and was resolved on 2025-05-10 12:30:00 UTC. Cause: A recent connector change unintentionally impacted requests to the affected endpoint, resulting in sync failures. Resolution: The change introducing the issue was reverted, and the fix was successfully deployed.