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 |
|---|---|---|---|
| April 2026 | 40% | 10 | 6 |
| March 2026 | 45.2% | 31 | 17 |
| February 2026 | 69.6% | 23 | 7 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 64 Days)
Feb 6
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
3rd Party: Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable" error
Started: Apr 10, 9:59 AM
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