Fivetran Outage History
Uptime record, past incidents, and downtime history for Fivetran.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| July 2026 | 77.8% | 9 | 2 |
| June 2026 | 13.3% | 30 | 26 |
| May 2026 | 12.9% | 31 | 27 |
| April 2026 | 42.9% | 21 | 12 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
3rd Party: QuickBooks connections failing with “Failed to sync 1 endpoint” error
Started: Jul 7, 5:20 PM
monitoring
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.
<b>Next Expected Update: 1 Hour </b>
Jul 7, 7:07 PM
identified
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.
<b>Next Expected Update:</b> 1 hour
Jul 7, 5:40 PM
identified
The issue has been identified and we are working to resolve it.
Jul 7, 5:20 PM
3rd Party: Some AppLovin connectors are failing
Started: Jul 6, 11:12 PM
monitoring
We have applied a fix. Affected connectors should resume syncing normally. We are monitoring recovery across all affected accounts.
Jul 7, 12:01 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 6, 11:45 PM
identified
We have identified an issue with the AppLovin connector in which syncs are failing with HTTP 500 Internal Server Error responses. 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.
Jul 6, 11:12 PM
identified
The issue has been identified and we are working to resolve it.
Jul 6, 11:05 PM
June 2026
Fivetran: Apple Search Ads connections are failing with error "HTTP 400 Bad Request"
Started: Jun 19, 6:15 AM
monitoring
A hotfix has been deployed, and the syncs are recovering. We will continue monitoring the syncs
<b>Next Expected Update: 3 hours</b>
Jun 19, 8:30 AM
identified
We have identified that this issue was caused by a recent change, and we are currently working on reverting the changes via a hotfix.
<b>Next Expected Update: 2 hours</b>
Jun 19, 6:45 AM
identified
The issue has been identified and we are working to resolve it.
Jun 19, 6:15 AM
Fivetran: Multiple Hybrid Deployment Connections are failing
Started: Jun 17, 12:40 PM
monitoring
We have deployed a fix for this issue.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
<b>Next Expected Update: 3 hours</b>
Jun 17, 3:56 PM
identified
We are continuing to work on a fix for this issue.
<b>Next Expected Update: 1 hour</b>
Jun 17, 3:00 PM
identified
We have identified that this issue was caused by a recent change, and we are currently working on a HotFix.
<b>Next Expected Update: 1 hour</b>
Jun 17, 1:33 PM
identified
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.
<b>Next Expected Update: 1 hour</b>
Jun 17, 12:40 PM
3rd Party: Multiple Customer.io connections are failing with 5xx error
Started: Jun 14, 1:10 AM
monitoring
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 th...
Jun 14, 3:18 PM
monitoring
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.
<b>Next Expected Update:</b> < 3 hours >
Jun 14, 10:36 AM
monitoring
We are continuing to monitor all affected connectors after the recent fix deployment.
<b>Next Expected Update:3 hours </b> <3 hours = P2, 2 hours = P1>
Jun 14, 7:00 AM
monitoring
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.
<b>Next Expected Update: 3 hours</b> <3 hours = P2, 2 hours = P1>
Jun 14, 4:14 AM
identified
We are preparing a fix to skip the failing endpoints until the source resolves the issue.
<b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>
Jun 14, 3:11 AM
identified
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.
<b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>
Jun 14, 1:55 AM
identified
The issue has been identified and we are working to resolve it.
Jun 14, 1:10 AM
3rd Party: Some Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" error
Started: Jun 7, 10:53 AM
monitoring
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.
<b>Next Expected Update:</b> < 3 hours >
Jun 7, 1:30 PM
identified
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
<b>Next Expected Update:</b> < 1 hour >
Jun 7, 10:53 AM
identified
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.
<b>Next Expected Update:</b> < 1 hour >
Jun 7, 8:50 AM
3rd Party: Some Impact Brand connections are failing with "HTTP 500 Internal server" error
Started: Jun 7, 6:20 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 7, 7:25 AM
identified
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.
<b>Next Expected Update: 1 hour</b>
Jun 7, 6:48 AM
identified
The issue has been identified and we are working to resolve it.
Jun 7, 6:20 AM
3rd Party: Shopify connections are failing with a "HTTP 404 Not Found" error
Started: Jun 3, 2:16 PM
monitoring
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.
<b>Next Expected Update: 3 hours</b>
Jun 3, 3:16 PM
identified
We are preparing a fix to skip the failing endpoints until Shopify resolves the issue.
<b>Next Expected Update: 1 hour</b>
Jun 3, 2:13 PM
identified
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/
<b>Next Expected Update: 1 hour</b>
Jun 3, 2:10 PM
identified
The issue has been identified and we are working to resolve it.
Jun 3, 1:55 PM
May 2026
Fivetran: Hybrid Deployment Agent jobs failing to start with error "Connection pool shut down"
Started: May 29, 4:40 PM
monitoring
We are monitoring the results of the fix. Customers are advised to restart their HD agents.
May 29, 9:44 PM
identified
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
May 29, 9:30 PM
identified
We have identified the root cause and have deployed a hot fix.
May 29, 9:23 PM
identified
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. HD agent logs show the following error
"Return CreateJobResponse/Failure, Caused By User: false - CREATE_JOB_ERROR/Connection pool shut down {process_id=XXX}"
This issue only affects HD deployments in Docker/Podman environments.
May 29, 9:20 PM
3rd Party: Google Display & Video 360 connections are failing with "HTTP 502 Bad Gateway" error
Started: May 26, 3:15 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 26, 7:50 AM
identified
The issue has been identified and we are working to resolve it.
May 26, 3:15 AM
Multiple connection syncs are failing with an "Internal: Failed to read token" error.
Started: May 22, 5:05 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 22, 5:05 AM
identified
The issue has been identified and we are working to resolve it.
May 22, 5:05 AM
Fivetran: Delay in User facing logs and External logs delivery
Started: May 22, 2:20 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 22, 2:45 AM
identified
The issue has been identified and we are working to resolve it.
May 22, 2:20 AM
3rd Party: Multiple Salesforce connections are failing with HTTP 503 Service Unavailable
Started: May 22, 1:20 AM
monitoring
The issue from source side is resolved and we noticed that syncs are succeeding now. We are continuing to monitor the syncs.
May 22, 4:17 AM
identified
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
May 22, 1:35 AM
identified
The issue has been identified and we are working to resolve it.
May 22, 1:20 AM
3rd Party: Qualtrics connection syncs are failing with "HTTP 400 Bad Request" for the "TransactionBatches" endpoint
Started: May 21, 6:25 AM
monitoring
A fix has been implemented from our end and we are monitoring the results.
May 21, 11:42 AM
identified
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 third-party support for more details on these failures.
We are also exploring possible workarounds to mitigate the issue in the meantime.
May 21, 7:53 AM
identified
The issue has been identified and we are working to resolve it.
May 21, 6:25 AM
3rd Party: Twitter Ads connections are failing with BadRequestException due to changes on the source side.
Started: May 20, 6:50 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 20, 8:40 PM
identified
We are continuing to work on a fix for this issue.
May 20, 6:53 PM
identified
The issue has been identified and we are working to resolve it.
May 20, 6:50 PM
Fivetran: Multiple connection syncs are failing with a "Token not found" error
Started: May 19, 10:15 AM
identified
The issue has been identified and we are working to resolve it.
May 19, 10:15 AM
3rd Party: X Ads and X Organic Performance Degradation
Started: May 18, 4:41 PM
identified
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.
Jun 24, 7:04 PM
identified
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.
Jun 23, 7:02 PM
identified
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
Jun 19, 10:29 PM
identified
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
Jun 17, 4:02 PM
identified
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
Jun 15, 10:25 PM
identified
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
Jun 12, 6:26 PM
identified
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
Jun 10, 10:42 PM
identified
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
Jun 9, 12:26 AM
identified
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
Jun 5, 9:01 PM
identified
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 availab...
Jun 3, 10:35 PM
identified
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
May 30, 7:00 PM
identified
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.
May 28, 10:52 PM
identified
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
May 26, 11:14 PM
identified
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
May 24, 3:43 AM
identified
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...
May 21, 4:48 PM
identified
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 21th
May 18, 4:41 PM
identified
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
May 14, 10:20 PM
identified
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...
May 14, 3:37 PM
identified
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.
May 13, 6:41 PM
Fivetran: Mutliple Amazon Ads connection syncs are faling with NullPointerException
Started: May 18, 7:05 AM
identified
We are continuing to work on a fix for this issue.
May 18, 7:45 AM
identified
The issue has been identified and we are working to resolve it.
May 18, 7:05 AM
3rd Party: Facebook Pages connectors failing with MonetizationMetricUnavailableException
Started: May 16, 2:25 PM
monitoring
We disabled monetization metrics processing for Facebook Pages and have not noticed any new failures.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
May 16, 4:21 PM
identified
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.
May 16, 2:32 PM
identified
The issue has been identified and we are working to resolve it.
May 16, 2:25 PM
3rd Party: Facebook Pages connectors failing with MonetizationMetricUnavailableException
Started: May 16, 2:19 PM
identified
We have identified an issue where Facebook Pages connectors are failing with a MonetizationMetricUnavailableException exception. We are currently investigating in more detail.
May 16, 2:19 PM
3rd Party: Multiple Apple App Store Connections are failing with `Reporter is currently unavailable`
Started: May 13, 12:59 AM
monitoring
Connection syncs are succeeding, and we continue to monitor the connections closely.
May 13, 3:23 AM
investigating
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.
May 13, 12:59 AM
identified
The issue has been identified and we are working to resolve it.
May 13, 12:45 AM
Fivetran: Delay in notifications/alerts on the Fivetran dashboard
Started: May 12, 6:25 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 12, 6:35 AM
identified
The issue has been identified and we are working to resolve it.
May 12, 6:25 AM
3rd Party: Typeform connections are failing with an error due to changes on the source side in the response for FORM_INSIGHT data.
Started: May 11, 7:35 PM
monitoring
We have implemented a fix and are currently monitoring the results.
May 11, 9:18 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 11, 9:05 PM
identified
The issue has been identified and we are working to resolve it.
May 11, 7:35 PM
Fivetran: Marketo Connections Experiencing Sync Failures
Started: May 10, 10:10 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 10, 12:30 PM
identified
The Marketo connections are failing with “PROGRAM_MEMBERSHIP: fields not specified” Error. The issue has been identified and we are working to resolve it.
May 10, 10:10 AM
3rd Party: Talkdesk connections are failing with "HTTP 404: Report file not found" Error
Started: May 10, 1:45 AM
monitoring
We have coordinated with Talkdesk, and mitigation measures have been implemented on their end. Their team is actively monitoring systems as they recover.
On our end, we are observing that connector syncs are recovering from prior failures and are now completing successfully.
We will continue to closely monitor the connector syncs and provide further updates as needed.
May 10, 6:21 AM
identified
Multiple report endpoints in the US region are returning HTTP 404 errors. Initial investigation indicates this may be linked to warning statuses for Talkdesk Explore™ Reporting and Talkdesk Workforce Management™ in the US region, as shown on the Talkdesk status page. We have reached out to Talkdesk support for more details on these failures.
Talkdesk status page:
https://status.talkdesk.com/
May 10, 2:46 AM
identified
The issue has been identified and we are working to resolve it.
May 10, 1:45 AM
3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"
Started: May 8, 3:35 AM
monitoring
Syncs were failing with "504 Gateway Timeout Error" for the call endpoint due to degraded performance on the Twilio side, as indicated on their status page.
The syncs have been recovered automatically without any intervention from the Fivetran end, and we are monitoring the connections.
Twilio Status Page: https://status.twilio.com/incidents/rqlltbpn6m1z
May 8, 4:05 AM
identified
The issue has been identified and we are working to resolve it.
May 8, 3:35 AM
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
Started: May 8, 2:35 AM
monitoring
Connection syncs are succeeding, and we continue to monitor the connections closely.
May 8, 7:31 AM
identified
Syncs continue to fail due to the issue on ASP’s side. We are continuing to monitor the connections.
May 8, 5:37 AM
identified
Syncs are failing with 500 Internal Server Error 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
May 8, 2:40 AM
identified
The issue has been identified and we are working to resolve it.
May 8, 2:35 AM
3rd Party: Hubspot connection syncs are failing with "HTTP 500 Internal Server Error" and message: "Your HubSpot source is not available at this time. We'll retry the sync later."
Started: May 8, 1:15 AM
monitoring
Syncs are recovering, and we are monitoring the results.
May 8, 2:15 AM
identified
HubSpot has updated their status page, confirming the regional degradation due to the AWS outage. We are also observing that sync failure rates are decreasing. We are monitoring the situation closely.
https://status.hubspot.com/incidents/f0s8vh3hsftw ("HubSpot is experiencing a regional degradation causing issues with loading related to an AWS outage")
May 8, 2:13 AM
identified
Syncs are failing due to an issue on the third-party side, due to "HTTP 500 Internal Server Error" for the events endpoint.
At this time, there are no reported incidents or updates on the HubSpot status page related to this behaviour. We have reached out to HubSpot support for more details on these failures.
HubSpot status page link: https://status.hubspot.com/
May 8, 1:27 AM
identified
The issue has been identified and we are working to resolve it.
May 8, 1:15 AM
3rd Party: Klaviyo connection syncs are failing with Reconnect Error
Started: May 7, 7:25 AM
monitoring
We have deployed a fix for this issue, and a few of the connectors have recovered since then.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
May 7, 10:46 AM
identified
Syncs are failing due to an issue on the third-party side with "HTTP 401 Unauthorized error" and the reconnect task: "We could not connect to Klaviyo due to an invalid API key. Please update the credentials."
We have reached out to Klaviyo support for more details on these failures. We are also exploring possible workarounds to mitigate the issue in the meantime.
May 7, 8:36 AM
identified
The issue has been identified and we are working to resolve it.
May 7, 7:25 AM
Many Connector SDK connections failed syncs with error "Failed to pull image after max retries"
Started: May 4, 11:40 PM
monitoring
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
<b>Incident Summary</b>
Description:
We identified an issue for Connector SDK connections, which resulted in syncs failing with a "Failed to pull image after max retries" error.
Timeline:
Incident Start Time: 2026-05-04 21:51 UTC
Incident End Time: 2026-05-04 23:49 UTC
Cause:
An automated cleanup process removed a required image used for C...
May 4, 11:56 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 4, 11:40 PM
identified
The issue has been identified and we are working to resolve it.
May 4, 11:40 PM
Fivetran: Hybrid connections are delayed
Started: May 4, 2:15 PM
monitoring
A workaround has been applied. We've rolled back the image affecting Hybrid Deployment connectors, and syncs have resumed. Our team is working on a permanent fix.
May 4, 3:30 PM
identified
The issue has been identified and we are working to resolve it.
May 4, 2:15 PM
The Connector SDK Connection state not advancing
Started: May 4, 9:35 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 4, 12:59 PM
identified
We are continuing to work on a fix for this issue.
May 4, 11:21 AM
identified
We have identified the root cause and are working on the fix.
May 4, 9:55 AM
identified
We identified an issue where the connector SDK connection state is not advancing, resulting in the same data sync for the last few days.
May 4, 9:35 AM
3rd Party: Hubspot connection syncs are failing with error "Your HubSpot source is not responding at this time. We'll retry the sync later"
Started: May 1, 1:10 AM
identified
The issue has been identified and we are working to resolve it.
May 1, 1:10 AM
April 2026
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
Started: Apr 28, 6:15 PM
monitoring
The connections are recovering and we are currently monitoring the syncs.
Apr 28, 6:54 PM
identified
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
Apr 28, 6:35 PM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 6:15 PM
3rd Party: Qualtrics connector syncs failing with error "Ticket export failed."
Started: Apr 28, 3:05 PM
monitoring
The issue on Qualtrics’ side has been resolved, and connector syncs are now recovering. We are continuing to monitor the results closely.
Apr 28, 4:25 PM
identified
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
Apr 28, 3:41 PM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 3:05 PM
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
Started: Apr 28, 10:00 AM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 10:00 AM
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
Started: Apr 28, 1:10 AM
monitoring
We have updated all the regions with the new secret keys and will continue to monitor the connections.
Apr 28, 10:26 AM
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
Apr 28, 9:52 AM
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
Apr 28, 9:51 AM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 9:50 AM
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
Started: Apr 28, 1:10 AM
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
Apr 28, 3:21 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 28, 3:20 AM
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
Apr 28, 1:45 AM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 1:10 AM
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
Started: Apr 28, 12:45 AM
monitoring
The connections are recovering and we are currently monitoring the syncs.
Apr 28, 2:15 AM
identified
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
Apr 28, 12:55 AM
identified
The issue has been identified and we are working to resolve it.
Apr 28, 12:45 AM
3rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changes
Started: Apr 27, 8:38 AM
monitoring
We have implemented a mitigation on our end to temporarily skip the SALES_AND_TRAFFIC_BUSINESS_* tables while we await further updates from the third-party. We will continue to monitor the connections.
Apr 27, 12:15 PM
identified
We have observed that all the Amazon Selling Partner connections across Fivetran app, custom app and customer_oauth app are re-scheduling due to the change in rate limits from 3rd party.
Apr 27, 8:38 AM
identified
The issue has been identified and we are working to resolve it.
Apr 27, 8:35 AM
3rd Party: Multiple Quickbooks connections sync failed
Started: Apr 26, 7:00 AM
identified
The issue has been identified and we are working to resolve it.
Apr 26, 7:00 AM
3rd Party: Multiple Twitter Ads connections failing due to 500 errors
Started: Apr 25, 10:55 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 26, 12:26 PM
identified
We are continuing to work on a fix for this issue.
Apr 26, 5:48 AM
identified
We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.
Apr 26, 12:09 AM
identified
The issue has been identified and we are working to resolve it.
Apr 25, 10:55 PM
Sync start delays caused by Azure outage in East-US-2 region
Started: Apr 24, 6:35 PM
identified
Azure is continuing to rollout a fix in the East US region. We have observed our backlog of syncs are caught up, but pod scaling is still affected. Once Azure confirms they have competed their fix, we will test pod scaling to ensure it works as expected.
Apr 24, 9:49 PM
identified
Azure has identified the issue and they expect recovery within the next hour. Fivetran engineering will continue to monitor as Azure works through this incident.
Apr 24, 8:47 PM
identified
The issue was caused by an outage on Azure. You can find more details at the following link:
https://azure.status.microsoft/en-us/status
Apr 24, 6:58 PM
identified
The issue has been identified and we are working to resolve it.
Apr 24, 6:35 PM
Some syncs are failing starting at 8AM Pacific time.
Started: Apr 23, 5:20 PM
monitoring
In the last hour, we have observed sync failure rates drop to normal rates. We are continuing to monitor.
Apr 23, 7:00 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 23, 5:20 PM
identified
The issue has been identified and we are working to resolve it.
Apr 23, 5:20 PM
3rd Party: Multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453)
Started: Apr 21, 10:00 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 22, 12:25 AM
identified
The issue has been identified and we are working to resolve it.
Apr 21, 10:00 PM
3rd Party: Multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453)
Started: Apr 21, 9:49 PM
identified
The issue has been identified and we are working to resolve it.
Apr 21, 9:49 PM
Apple App Store Connectors are failing with `Reporter is currently unavailable`
Started: Apr 21, 4:30 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 21, 4:30 AM
identified
The issue has been identified and we are working to resolve it.
Apr 21, 4:30 AM
Some Twitter Ads connections are failing due to a null primary key exception
Started: Apr 14, 4:40 PM
monitoring
Twitter has identified an outage and services have now returned to normal:
https://devcommunity.x.com/t/x-api-service-outage/262778
A hotfix has also been deployed to prevent further failures due to null primary keys. We have observed connections begin to recover and will continue monitoring.
Apr 14, 10:48 PM
identified
We have identified an issue where the source API is returning null values in a primary key field (segment) for some reports, resulting in sync failures.
We are actively working on a fix to skip these rows so that syncs can continue without interruption. We will provide another update as more information becomes available.
Apr 14, 7:21 PM
identified
The issue has been identified and we are working to resolve it.
Apr 14, 4:40 PM
3rd Party: Sync failures due to Bad Authentication data (code 215) error
Started: Apr 11, 10:45 PM
monitoring
A fix has been implemented, and we are monitoring the results.
Apr 12, 12:07 AM
identified
Connectors are failing with a “Bad Authentication data” error (code 215) while fetching successful async job results.
Apr 11, 11:18 PM
identified
The issue has been identified and we are working to resolve it.
Apr 11, 10:45 PM
3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to URI is not absolute error with HTTP 500 Response
Started: Apr 11, 11:55 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 11, 1:14 PM
identified
The failure, "URI is not absolute" is a cause of failing Twitter APIs while trying to fetch reports with code 500 and message "internal server error"
Apr 11, 1:08 PM
identified
The issue has been identified and we are working to resolve it.
Apr 11, 11:55 AM
3rd Party: Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable" error
Started: Apr 10, 9:59 AM
monitoring
A hotfix has been implemented, and affected connections are recovering. We are continuing to monitor results.
Apr 10, 7:58 PM
identified
We're rolling out fixes to handle 429 and 503 errors more effectively. Endpoints that continue to fail after retries will now be skipped to ensure smoother syncs.
Apr 10, 6:51 PM
identified
We are continuing to work on a fix for this issue.
Apr 10, 12:21 PM
identified
The issue has been identified as originating from the third-party end, where the accounts endpoint is intermittently failing.
We are implementing a fix to address this, ensuring the exception is now properly detected and managed. We are continuing to monitor the situation closely.
Apr 10, 9:59 AM
identified
There are no updates from Twitter on their status page: https://docs.x.com/status
We are looking into potential workarounds to address these failures and will provide further updates as soon as more information is available.
Apr 10, 6:09 AM
identified
The issue has been identified and we are working to resolve it.
Apr 10, 4:15 AM
Transformation jobs are failing with "UnsatisfiedDependencyException" error
Started: Apr 10, 12:34 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 12:45 AM
identified
We are actively working on a fix for this issue. This issue is currently impacting dbt core and Quickstart transformations
Apr 10, 12:34 AM
identified
The issue has been identified and we are working to resolve it.
Apr 10, 12:20 AM
Fivetran : Few Amazon Selling partner connections are failing for the all_listings_report
Started: Apr 8, 12:50 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 8, 2:07 PM
identified
We have identified that the connections are failing with the below error
all_listings_report endpoint sync failed with error: Cannot invoke "com.fivetran.platform.interfaces.connector.SharedContext.safeFileBufferFactory()" because "this.sharedContext" is null
Apr 8, 12:50 PM
3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) error
Started: Apr 7, 5:18 PM
monitoring
The hotfix to handle 503 errors and attempt retries on failed endpoints has been deployed. We have confirmed a significant drop in sync failures as a result and will continue monitoring for any further failures.
Apr 7, 10:47 PM
identified
A hotfix will be deployed to handle 503 errors from the Twitter API and to skip failing endpoints after several retries.
We are still waiting for an update from X regarding the issue:
https://devcommunity.x.com/t/503-error-while-requesting-12-stats-jobs-accounts-accountid/262061
Apr 7, 9:50 PM
identified
We’ve logged an issue with the Twitter support team and will share updates shortly.
Link: https://devcommunity.x.com/t/503-error-while-requesting-12-stats-jobs-accounts-accountid/262061
Apr 7, 5:23 PM
identified
We have identified that the '/stats/jobs/accounts/' endpoint is returning HTTP 503 (Service Unavailable), impacting syncs.
Apr 7, 5:18 PM
identified
The issue has been identified and we are working to resolve it.
Apr 7, 4:30 PM
Awin connection syncs are failing with 500 internal server error for transaction endpoint
Started: Apr 4, 8:05 AM
monitoring
We have successfully implemented a workaround by skipping the Transaction endpoint sync for now. We will continue monitoring all affected connections and have also reached out to the awin source team.
Apr 4, 10:52 AM
identified
As a temporary workaround, our development team is skipping the Transaction endpoint. We will contact the source to investigate the issue and work on a fix.
Apr 4, 8:44 AM
identified
The issue has been identified as originating from the source side and we are working to resolve it.
Apr 4, 8:05 AM
Fivetran: SQL Server TELEPORT and Epic CSA Connector POTENTIAL Failures Due to Unsupported Type in VIEW tables
Started: Apr 2, 5:45 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 2, 9:03 PM
identified
We are continuing to work on a fix for this issue.
Apr 2, 6:37 PM
identified
We identified a potential issue affecting the SQL Server (Teleport) and Epic CSA connectors, where syncs are failing with the following error.
The action failed after 1 attempt(s), the failures were:1) java.lang.IllegalArgumentException: No enum constant com.fivetran.integrations.sql_server.connector.schema.SqlServerType.SYSNAME
Apr 2, 5:45 PM
3rd Party: Multiple Twitter Ads connections are failing with an HTTP 500 Internal Server Error
Started: Apr 2, 10:29 AM
monitoring
A fix has been implemented and the connections are recovering from the failure.
We'll continue to monitor the results.
Apr 2, 2:51 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 2, 2:40 PM
identified
We have identified that this issue was caused by the 'campaigns' endpoint, which is returning a '500 Internal Server' error.
We are looking into potential workarounds to address these failures and will provide further updates as soon as more information is available.
Apr 2, 10:29 AM
identified
The issue has been identified and we are working to resolve it.
Apr 2, 10:20 AM
Some Reddit Ads connections are failing with an HTTP 500 Internal Server error
Started: Apr 1, 7:30 PM
identified
We are seeing HTTP 500 (Internal Server Error) responses from Reddit’s Ads API when attempting to create reporting jobs. This occurs on the report creation endpoint and is affecting multiple connectors.
Apr 1, 7:50 PM
identified
The issue has been identified and we are working to resolve it.
Apr 1, 7:30 PM
Delay in log delivery in customer's external log due to an issue with our external logging services
Started: Apr 1, 1:40 AM
monitoring
There is an outage in the external logging API “Splunk Log,” causing delays. Splunk has also reported this incident on their status page: https://status.splunkcloud.com/
This resulted in a buildup of Splunk log messages in our internal queue, impacting log delivery across other logging services. The team has deployed a fix to prevent delays to other logging services. The Splunk issue also appears to be resolved, and we are actively monitoring the system.
Apr 1, 1:50 AM
identified
The issue has been identified and we are working to resolve it.
Apr 1, 1:40 AM
March 2026
Fivetran: Few Pipedrive connections are failing with the Null exception.
Started: Mar 31, 3:40 PM
identified
The issue has been identified and we are working to resolve it.
Mar 31, 3:40 PM
Multiple Twitter Ads and Twitter Organic Connections Failing with error "HTTP 503 Service Unavailable"
Started: Mar 30, 10:00 PM
monitoring
The issue appears to have been resolved from the source side. Rate limit errors have subsided, and affected connectors have returned to normal sync operations
Mar 31, 3:54 PM
identified
We are continuing to monitor the status page, as there are no latest updates from X.
In the meantime, we are exploring potential workarounds to help mitigate the issue until it is fully resolved on the source side.
Mar 31, 11:56 AM
identified
We are still seeing the issue at the source end and are continuing to monitor their status page. We have reached out to X support, and X has acknowledged degraded performance on their status page: https://docs.x.com/status.
Mar 31, 3:56 AM
identified
The issue appears to be related to missing rate limit headers in the response. As a result, requests are repeatedly hitting HTTP 429 (rate limit) and, in some cases, resulting in HTTP 503 errors. We have reached out to X support, and X has also acknowledged degraded performance on their status page: https://docs.x.com/status
Mar 30, 6:09 PM
identified
The issue has been identified and we are working to resolve it.
Mar 30, 5:55 PM
Fivetran: OAuth Authentication Issues Affecting Multiple Connections
Started: Mar 26, 4:05 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 26, 5:00 PM
identified
The issue has been identified and we are working to resolve it.
Mar 26, 4:05 PM
Fivetran: PostgreSQL Connections Using RDS Proxy Are Failing with the Error: The source database does not support a provided lock_timeout parameter
Started: Mar 26, 6:20 AM
identified
We are continuing to work on a fix for this issue.
Mar 26, 6:24 AM
identified
The issue has been identified and we are working to resolve it.
Mar 26, 6:20 AM
Fivetran: Fivetran REST API Failing with 404 Errors
Started: Mar 26, 4:35 AM
monitoring
We have deployed a fix for the issue causing 404 errors in the Fivetran REST API.
We will continue to monitor the service to ensure normal operation.
If you continue to experience any issues, please reach out to our Support Team.
Mar 26, 7:05 AM
identified
We have identified the root cause of the issue causing 404 errors in the Fivetran REST API and are actively working on a fix. We will continue to share updates as we make progress.
Mar 26, 6:47 AM
identified
We are continuing to investigate the root cause of the issue. Our Engineering team is actively working to identify the underlying problem and will share further updates as more information becomes available.
The team is also reviewing recent changes to determine if they may have contributed to the issue.
Mar 26, 5:47 AM
identified
The issue has been identified and we are working to resolve it.
Mar 26, 4:35 AM
3rd Party: Multiple Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable"
Started: Mar 26, 3:30 AM
monitoring
Many Twitter and Twitter Ads connections have recovered, and the rate of severe errors has dropped significantly over the past 2 hours.
We are still seeing intermittent 500 and 503 errors for a small subset of connections.
X (Twitter) has not yet marked the incident as resolved on their status page, and we will continue to monitor for full recovery.
https://docs.x.com/status
Mar 26, 11:41 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 26, 10:40 AM
identified
We have reached out to the third-party to obtain the latest status on this issue and are currently awaiting their response.
Additionally, we have started observing "HTTP 500 – Internal Server Error" for a few connections.
At this time, there are no further updates available on their status page. We are continuing to closely monitor the situation and will share updates as soon as we receive more information.
Mar 26, 8:35 AM
identified
The third-party is still working on this incident, and there have been no further updates on their status page at this time.
We are continuing to closely monitor the situation and will keep you informed as soon as we receive any new information.
Mar 26, 5:56 AM
identified
The issue has been identified as being caused by a problem on the third-party side. They have also acknowledged and posted an update on their page (link below).
https://docs.x.com/status
We are closely monitoring the situation and will provide further updates as soon as more information becomes available.
Mar 26, 4:09 AM
identified
The issue has been identified and we are working to resolve it.
Mar 26, 3:30 AM
Multiple connectors under the BigQuery destination are failing with a "GCS_BG_STORAGE" error.
Started: Mar 25, 1:20 AM
monitoring
Connections syncing to BigQuery destinations are impacted due to an internal configuration error. The issue has now been resolved, and we are monitoring sync.
Mar 25, 1:37 AM
identified
The issue has been identified and we are working to resolve it.
Mar 25, 1:20 AM
Some Box Connections are failing with HTTP "429 Too Many Requests" errors
Started: Mar 23, 8:10 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 23, 8:40 PM
identified
The issue has been identified and we are working to resolve it.
Mar 23, 8:10 PM
Some itunes_connect Connections Failing Due to Intermittent Apple App Store Connect Reporter Unavailability
Started: Mar 22, 7:40 AM
identified
We identified an issue with the itunes_connect Connections where sync is failing with the "Unknown failure" error.
Mar 22, 7:40 AM
3rd Party: Snowflake Downtime Causing Sync Failures Across Multiple Connections Using Snowflake as Destination
Started: Mar 21, 9:37 AM
monitoring
We are continuing to monitor to ensure all syncs return to normal.
More details: https://status.snowflake.com/
Mar 21, 9:38 AM
monitoring
Snowflake has reported recovery for US regions, and we are monitoring to ensure all syncs return to normal.
More details: https://status.snowflake.com/
Mar 21, 7:30 AM
identified
Sync failures were caused by an ongoing Snowflake issue impacting Snowflake destinations. Snowflake has reported recovery for US regions, and we are monitoring to ensure all syncs return to normal.
More details: https://status.snowflake.com/
Mar 21, 7:07 AM
identified
The issue has been identified and we are working to resolve it.
Mar 21, 7:05 AM
3rd Party: Sync delays in GCP Australia Southeast1 region
Started: Mar 20, 7:30 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 20, 7:40 PM
identified
The issue has been identified and we are working to resolve it.
Mar 20, 7:30 PM
3rd Party: Some Amazon S3 Connections Intermittently Failing with HTTP Connection Timeout Error
Started: Mar 20, 1:05 AM
monitoring
Sync failures were due to AWS-side timeouts, and the connectors have now recovered.
Mar 20, 1:05 AM
identified
The issue has been identified and we are working to resolve it.
Mar 20, 1:05 AM
3rd Party: Snapchat Ads connections are failing with error "500 Internal Server Error"
Started: Mar 18, 5:50 AM
monitoring
We experienced an intermittent issue with a third-party API service that resulted in 500 errors. Connections are now recovering, and we are continuing to closely monitor sync performance.
Mar 18, 6:13 AM
identified
The issue has been identified and we are working to resolve it.
Mar 18, 5:50 AM
Fivetran: Multiple connection syncs and transformations are delayed
Started: Mar 15, 7:35 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 15, 9:56 AM
identified
We are continuing to work on a fix for this issue.
Mar 15, 9:00 AM
identified
We have identified an issue where multiple connection syncs and transformations are delayed.
Mar 15, 7:35 AM
3rd Party: Few Qualtrics connections were failing with HTTP Error Code 429
Started: Mar 14, 10:55 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 14, 11:22 PM
identified
We identified an issue where the Distribution Contact endpoint was retrying requests too frequently, which caused some syncs to fail with rate limit errors (429).
A hotfix has been raised to adjust the retry behavior so that retries are spaced out more effectively. We will continue to monitor the syncs after deployment.
Mar 14, 11:12 PM
identified
The issue has been identified and we are working to resolve it.
Mar 14, 10:55 PM
3rd Party: Some HubSpot connection syncs are failing with an HTTP 477 RefreshCredentials error.
Started: Mar 14, 9:00 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 14, 10:45 AM
identified
Recent migration of the Fivetran public app by HubSpot has caused the issue. A hotfix is being deployed to resolve the issue.
Mar 14, 10:15 AM
identified
We identified an issue with the HubSpot Connections where the syncs are failing with an HTTP 477 RefreshCredentials error.
Mar 14, 9:00 AM
Some of connections may experience dashboard sync bar delay in showing data
Started: Mar 12, 7:35 PM
monitoring
We have deployed a fix for this issue: We created a hotfix to handle malformed messages which were preventing normal messages from processing
We will continue to monitor all affected sync events until we are caught up and the Connection Status page is back to normal.
Mar 12, 9:10 PM
identified
The issue has been identified and we are working to resolve it.
Mar 12, 7:35 PM