Provider resolved: . The notice publication date does not establish the outage start.
Amplitude
resolved
The Amplitude team has fixed the issue on their end and marked the incident as resolved.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified by the source team and they are working on resolving it.
Amplitude Status page: https://status.amplitude.com/incidents/nrrkcvqt75zd
Fivetran: Tableau (Lite) connections failing with "Failed to fetch OAuth2 Token" error
Provider resolved: . The notice publication date does not establish the outage start.
Tableau
resolved
This incident has been resolved. We have observed that error rates are returning to normal levels, and affected Tableau connectors are syncing successfully.
Incident Summary
Description:
We identified an issue affecting Tableau connections that caused syncs to fail with the error "Failed to fetch OAuth2 Token".
Timeline:
This issue began on Oct 19th, 2026 at 15:30 UTC and was resolved on Oct 19th, 2026 at 23:00 UTC.
Cause:
This issue was caused by a recent authentication-related change.
Resolution:
We rolled back the change and deployed the fix. Following deployment, affected connections recovered automatically and are now syncing successfully.
monitoring
We have deployed a fix for this issue by rolling back a recent authentication-related change that was causing connection failures.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
identified
We have identified that this issue was caused by a recent authentication-related change. We’ve rolled back the change, and the fix is being deployed now. Once deployment is complete, affected connections should recover automatically.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
3rd Party: Ramp connections failing with a "Reconnect" error
Provider resolved: . The notice publication date does not establish the outage start.
Ramp
resolved
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 Ramp connections that resulted in syncs failing with a "Reconnect" error because the APIs returned 503 Service Unavailable with the message "Scheduled maintenance in progress" on several endpoints.
Timeline:
This issue began on October 18, 2026 at 03:00 UTC and was resolved on October 18, 2026 at 08:00 UTC.
Cause:
We have identified that this issue was caused by a scheduled maintenance on the Ramp source end.
Resolution:
The issue was fixed on the Ramp source end after the scheduled maintenance was completed, and the affected connectors are syncing successfully.
monitoring
We have identified an issue where Ramp connectors started to fail with a Reconnect error. The APIs returned 503 Service Unavailable with the message "Scheduled maintenance in progress" on several endpoints.
We have identified that this issue was caused by scheduled maintenance on the Ramp source end.
This has been fixed by Ramp source, and we're continuing to monitor the results.
Next Expected Update: 3 hours
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working to resolve it.
3rd Party: NetSuite connections failing due to NetSuite-side "TCP/IP error, connection reset by peer" error
Provider resolved: . The notice publication date does not establish the outage start.
NetSuite SuiteAnalytics
resolved
Incident Summary
Description:
We identified an issue affecting the NetSuite SuiteAnalytics connector that caused syncs to fail with the error: TCP/IP error, connection reset by peer.
Timeline:
The issue began on October 16, 2026, at 17:20 UTC and was resolved on October 17, 2026, at 04:25 UTC.
Cause:
The issue was caused by metadata queries timing out on the NetSuite SuiteAnalytics side, resulting in connection resets and subsequent sync failures.
Resolution:
We implemented a fix to skip the affected tables that were causing the failures, allowing syncs to proceed successfully.
monitoring
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: 7:30 AM UTC
identified
The issue has been identified and we are working to resolve it.
Fivetran: Some Asana Connections Failing with “HTTP 400 Bad Request” Errors on the portfolios Endpoint
Provider resolved: . The notice publication date does not establish the outage start.
Asana
resolved
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 Asana which resulted in syncs failing with a “HTTP 400 Bad Request” error on the portfolios endpoint.
Timeline:
This issue began on October 15, 2026 at 17:49 UTC and was resolved on October 15, 2026 at 20:30 UTC.
Cause:
A recent change caused some Asana connections to fail due to a missing required parameter in requests to the /portfolios endpoint.
Resolution:
We reverted the problematic change and deployed a fix. Following the fix, the affected connections began recovering and resumed syncing successfully. No data was lost; any delayed data will be picked up automatically in subsequent syncs, and no customer action is required.
monitoring
A fix has been implemented and we are monitoring the results.
identified
A recent change caused some Asana connections to fail due to a missing required parameter in requests to the /portfolios endpoint. We are working to deploy a fix.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
Fivetran: Databricks Connections Using Private Link Reporting Successful Syncs Without Loading Data
Provider resolved: . The notice publication date does not establish the outage start.
Databricks
resolved
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 have identified an issue affecting Databricks connections using Private Link connectivity, where syncs are completing successfully without loading data. Additionally, tables are being automatically deselected, and connection setup tests are failing with an "Unknown failure" error.
Timeline:
The issue began on October 14, 2026, at 16:30 UTC and was resolved on October 15, 2026, at 13:30 UTC.
Cause:
A recent platform change introduced an issue affecting Databricks source connections using Private Link connectivity, preventing data from being loaded successfully.
Resolution:
We reverted the problematic change and re-enabled the affected tables. Following the fix, the connections began recovering and resumed syncing successfully.
No data was skipped, and no customer action is required.
monitoring
We have deployed a fix for the issue.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
identified
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
We have identified an issue affecting Databricks connections using Private Link connectivity, where syncs are completing successfully without loading data. Additionally, tables are being automatically deselected, and connection setup tests are failing with an "Unknown failure" error.
We are currently investigating in more detail.
Next Expected Update: 1 hour.
3rd Party: HubSpot connections are failing with an HTTP 500: Internal Server Error
Provider resolved: . The notice publication date does not establish the outage start.
HubSpot
resolved
Incident Summary
Description:
We identified an issue for HubSpot which resulted in syncs failing with HTTP 500: Internal Server Error (Your HubSpot source is not available at this time) errors.
Timeline: This issue began on October 10, 2026 at 16:14 UTC and was resolved on October 10, 2026 at 16:30 UTC.
Cause: A temporary source-side issue where multiple HubSpot endpoints returned 500 Internal Server Errors.
Resolution: No action was required on our side; all affected connections recovered automatically once the HubSpot API stopped returning errors.
3rd Party: Salesforce connections are failing with Reauthorize OAuth access error
Provider resolved: . The notice publication date does not establish the outage start.
Salesforce
resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels.
Incident Summary
Description:
We identified an issue with Salesforce connectors, which resulted in syncs failing with a Reauthorize OAuth access error.
Timeline:
This issue began on 2026/10/10 at 04:26 UTC and was resolved on 2026/10/10 at 14:30 UTC.
Cause:
This was caused by a Major Release and Maintenance at the Salesforce source.
During this maintenance, Salesforce appear to have revoked the refresh tokens, resulting in the connection failures.
Resolution:
To resolve the error,
We kindly request that you reauthorize the affected Salesforce connections to refresh their authentication tokens and allow the syncs to resume successfully.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The Salesforce connections are failing with the "Reauthorize OAuth access" error.
We have identified that this issue was caused by an ongoing maintenance on Salesforce, and Salesforce appear to have revoked the refresh tokens. Hence, the connections encountered the "expired access/refresh token" error.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
3rd Party: HubSpot connections are failing with a 504 Gateway Timeout error from the source side.
Provider resolved: . The notice publication date does not establish the outage start.
HubSpot
resolved
We have resolved this incident.
monitoring
The HubSpot team has fixed the issue on their end, and the affected connections have started recovering.
We will continue to monitor the situation.
monitoring
The HubSpot team has fixed the issue on their end, and the affected connections have started recovering.
We will continue to monitor the situation.
identified
The issue is from the HubSpot end, and the same has been posted on their status page. You can find the latest updates here: https://status.hubspot.com/
identified
The issue has been identified and we are working to resolve it.
Fivetran: A few Google Ads connector syncs are unable to ingest complete data for some reports
Provider resolved: . The notice publication date does not establish the outage start.
Google Ads
resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are completing syncs successfully.
Incident Summary
Description:
We identified an issue with the Google Ads connector, which resulted in syncs failing to ingest complete data for some reports due to a RESOURCE_EXHAUSTED (gRPC message exceeds maximum size) error.
Timeline:
This issue began on October 2 at approximately 4:30 PM UTC and was resolved on October 3 at 7:45 PM UTC.
Cause:
A recent update to our system accidentally lowered the limit on the size of data batches we can receive at one time. Because of this, our system began rejecting larger data responses coming from Google Ads.
Resolution:
We released a quick fix to restore the data limit back to its normal, higher capacity. We have closely monitored the affected connections and confirmed that data is now syncing completely and normally. Any previously skipped data has automatically caught up, and no manual action is required on your part.
monitoring
We have deployed a fix for this gRPC message size issue and are seeing the previously skipped reports catch up.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
identified
A fix for the gRPC message size issue affecting Google Ads connectors has been raised and is currently being reviewed by our team. Once approved, we will deploy the fix and monitor sync stability.
Next Expected Update: 1 hour
identified
We have identified that this issue was caused by a recent code change on our end and we are currently working on a fix.
Next Expected Update: 1 hour
identified
We have identified an issue where Google Ads connectors are experiencing an issue, causing the syncs to be unable to ingest complete data for some reports.
Logs show the "RESOURCE_EXHAUSTED, Fault: gRPC message exceeds maximum size 4194304." messages.
We are currently investigating in more detail.
Next Expected Update: 1 hour
identified
The issue has been identified and we are working to resolve it.
Legacy Incident Archive
66 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
The issue on Qualtrics’ side has been resolved, and connector syncs are now recovering. We are continuing to monitor the results closely.
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
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
minorSource not attested
Last archived state: identified
View archived record details
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
majorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have updated all the regions with the new secret keys and will continue to monitor the connections.
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
identified
The issue has been identified and we are working to resolve it.
Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
monitoring
A fix has been implemented and we are monitoring the results.
identified
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
identified
The issue has been identified and we are working to resolve it.
3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
The connections are recovering and we are currently monitoring the syncs.
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
identified
The issue has been identified and we are working to resolve it.
3rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changes
minorSource not attested
Last archived state: monitoring
View archived record details
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.
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.
identified
The issue has been identified and we are working to resolve it.
The issue has been identified and we are working to resolve it.
3rd Party: Multiple Twitter Ads connections failing due to 500 errors
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.
identified
The issue has been identified and we are working to resolve it.
Sync start delays caused by Azure outage in East-US-2 region
minorSource not attested
Last archived state: identified
View archived record details
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.
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.
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
identified
The issue has been identified and we are working to resolve it.
Some syncs are failing starting at 8AM Pacific time.
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
In the last hour, we have observed sync failure rates drop to normal rates. We are continuing to monitor.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working to resolve it.
