Fivetran Outage History
Fivetran is up right nowPingoru has recorded 102 incidents for Fivetran: 102 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 | 31 | 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 590 (0%) |
Incidents, newest first
Minor May 10, 2026 3rd Party: Talkdesk connections are failing with "HTTP 404: Report file not found" Error 7h 21m Talkdesk
Started May 10, 2026, 01:45 AM UTC· resolved May 10, 2026, 09:06 AM UTC
- identified May 10, 2026, 01:45 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 10, 2026, 02:46 AM UTC
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/
- monitoring May 10, 2026, 06:21 AM UTC
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.
- resolved May 10, 2026, 09:06 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 affecting Talkdesk Reporting endpoints in the US region, which caused connection sync failures with the error: "HTTP 404 Report file not found." Timeline: The issue started on 2026-05-09 14:51:00 UTC and was resolved on 2026-05-10 05:30:00 UTC. Cause: The issue originated from the third-party service, where Reporting endpoints in the US region were returning "HTTP 404 Report file not found" errors during report file downloads. We coordinated with Talkdesk, and mitigation actions were taken on their end. Resolution: The issue was resolved by the third-party provider without requiring any changes or intervention from the Fivetran side.
Notice May 8, 2026 3rd Party: Some 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 08, 2026, 05:00 PM UTC· resolved May 08, 2026, 05:00 PM UTC
- resolved May 08, 2026, 06: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: We identified an issue with the HubSpot connection, which resulted in syncs failing with "HTTP 500 Internal Server Error" Timeline: This issue began on 8th May 2026 at 04:54 PM UTC and was resolved on 8th May 2026 at 05:16 PM UTC. Cause: The issue was caused by the third-party, users endpoint failing with "HTTP 500 Internal Server Error". HubSpot has also updated their status page, confirming the regional degradation due to the AWS outage. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Notice May 8, 2026 3rd Party: Brevo Connections Experiencing Sync Failures –
Started May 08, 2026, 03:30 PM UTC· resolved May 08, 2026, 03:30 PM UTC
- resolved May 12, 2026, 05:22 PM UTC
Description: We identified an issue with the Brevo connector, which resulted in syncs failing with error: "Invalid date-time filter". Timeline: This issue began on 2026-05-08 16:30:00 UTC and was resolved on 2026-05-12 07:00:00 UTC. Cause: A recent update from Brevo resulted in the date format that the connector used being incompatible with the source API requirements. Resolution: The datetime formatter has been updated to ensure timestamps are always sent in explicit UTC format (Z) as expected by the source API. This resolved the connector failures and also handles any potential format variation going forward.
Minor May 8, 2026 3rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR" 1h 19m Twilio
Started May 08, 2026, 03:35 AM UTC· resolved May 08, 2026, 04:54 AM UTC
- identified May 08, 2026, 03:35 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 08, 2026, 04:05 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2026, 04:54 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 the Twilio connection, which resulted in syncs failing with "504 Gateway Timeout Error" Timeline: This issue began on 8th May 2026 at 01:20 AM UTC and was resolved on 8th May 2026 at 02:41 AM UTC. Cause: The issue was caused by the third-party call endpoint failing with "504 Gateway Timeout Error". Twilio has also updated their status page, confirming the degraded performance. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Minor May 8, 2026 3rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server Error 6h 36m Amazon Selling Partner
Started May 08, 2026, 02:35 AM UTC· resolved May 08, 2026, 09:11 AM UTC
- identified May 08, 2026, 02:35 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 08, 2026, 02:40 AM UTC
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
- identified May 08, 2026, 05:37 AM UTC
Syncs continue to fail due to the issue on ASP’s side. In parallel, we’re actively exploring potential workarounds to help mitigate the impact while the underlying issue is being resolved.
- monitoring May 08, 2026, 07:31 AM UTC
Connection syncs are succeeding, and we continue to monitor the connections closely.
- resolved May 08, 2026, 09:11 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 Amazon Selling Partners connection, which resulted in syncs failing with "HTTP 500 Internal Server Error" Timeline: This issue began on 2026-05-08 01:00 UTC and was resolved on 2026-05-08 08:00 UTC. Cause: The issue was caused by the third-party, Orders endpoint failed with "HTTP 500 Internal Server Error" . due to degraded performance in the Amazon Selling Partner API, as indicated on their status page. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Minor May 8, 2026 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." 1h 9m HubSpot
Started May 08, 2026, 02:15 AM UTC· resolved May 08, 2026, 03:25 AM UTC
- identified May 08, 2026, 01:15 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 08, 2026, 01:27 AM UTC
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/
- identified May 08, 2026, 02:13 AM UTC
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")
- monitoring May 08, 2026, 02:15 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2026, 03:25 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 the HubSpot connection, which resulted in syncs failing with "HTTP 500 Internal Server Error" Timeline: This issue began on 8th May 2026 at 12:07 AM UTC and was resolved on 8th May 2026 at 01:32 AM UTC. Cause: The issue was caused by the third-party, event-definitions endpoint failing with "HTTP 500 Internal Server Error". HubSpot has also updated their status page, confirming the regional degradation due to the AWS outage. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Minor May 7, 2026 3rd Party: Klaviyo connection syncs are failing with Reconnect Error 4h 41m Klaviyo
Started May 07, 2026, 07:25 AM UTC· resolved May 07, 2026, 12:06 PM UTC
- identified May 07, 2026, 07:25 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 07, 2026, 08:36 AM UTC
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.
- monitoring May 07, 2026, 10:46 AM UTC
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.
- resolved May 07, 2026, 12:06 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 Klaviyo, which resulted in syncs failing with reconnect tasks thrown on the dashboard. Timeline: This issue began on 7th May 2026 at 8:00 AM UTC and was resolved on 7th May 2026 at 11:50 AM UTC. Cause: Received HTTP 401 failure for the Template endpoint. Resolution: We have added a skip logic for the Template endpoint that disables/does not allow syncing the email_template table when the endpoint is encountering the 401 issue, but allows all other tables to sync normally instead of failing the sync.
Minor May 4, 2026 Fivetran: Many Connector SDK connections failed syncs with error "Failed to pull image after max retries" 2h 38m Connector SDK
Started May 04, 2026, 11:56 PM UTC· resolved May 05, 2026, 02:35 AM UTC
- identified May 04, 2026, 11:40 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 04, 2026, 11:40 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 04, 2026, 11:56 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 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 Connector SDK sync runs. Resolution: Fivetran redeployed the image, which restored the Connector SDK service.
- resolved May 05, 2026, 02:35 AM UTC
We have resolved this incident.
Minor May 4, 2026 Fivetran: Hybrid connections are delayed 4h 6m General Services
Started May 04, 2026, 02:15 PM UTC· resolved May 04, 2026, 06:21 PM UTC
- identified May 04, 2026, 02:15 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 04, 2026, 03:30 PM UTC
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.
- resolved May 04, 2026, 06:21 PM UTC
Description: We identified connection issues affecting dependency retrieval during the build process for Hybrid Connector images. Specifically, requests to external package sources were failing, resulting in build disruptions. Impact: Customers using Hybrid Deployment may have experienced failures when attempting to build or update connector images during this period. Timeline: Start Time: 2026-05-04 13:43 UTC End Time: 2026-05-04 14:57 UTC Root Cause: The issue was caused by an inability to fetch required dependencies from Ubuntu Launchpad and the Ubuntu archive, which prevented successful image builds. Resolution: We mitigated the issue by reverting to stable, previously built images, restoring normal functionality for Hybrid Connector deployments.
Minor May 4, 2026 Fivetran: The Connector SDK Connection state not advancing 3h 31m Connector SDK
Started May 04, 2026, 09:35 AM UTC· resolved May 04, 2026, 01:07 PM UTC
- identified May 04, 2026, 09:35 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 04, 2026, 09:55 AM UTC
We have identified the root cause and are working on the fix.
- identified May 04, 2026, 11:21 AM UTC
We are continuing to work on a fix for this issue.
- monitoring May 04, 2026, 12:59 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 04, 2026, 01:07 PM UTC
This incident has been resolved. Incident Summary Description: We identified an issue where the connector SDK connection state is not advancing, resulting in the same data sync for the last few days. Timeline: This issue began on April 29, 2026, at 02:08 UTC and was resolved on May 4, 2026, at 13:00 UTC Cause: A recent code change caused the issue. Resolution: Reverted the changes to resolve the issue.
Minor May 1, 2026 3rd Party: Hubspot connection syncs are failing with error "Your HubSpot source is not responding at this time. We'll retry the sync later" 2h 53m HubSpot
Started May 01, 2026, 01:10 AM UTC· resolved May 01, 2026, 04:03 AM UTC
- identified May 01, 2026, 01:10 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring May 01, 2026, 03:16 AM UTC
We have identified that the issue is related to the events endpoint and have reached out to HubSpot support for more details on the failure. The failure rate is decreasing without any changes on the Fivetran side, and we are monitoring the syncs.
- resolved May 01, 2026, 04:03 AM UTC
Instance rates have returned to normal levels, and affected connections are now syncing successfully. Incident Summary Description: We identified an issue impacting HubSpot connections, where syncs started failing with the error "Your HubSpot source is not responding at this time. We'll retry the sync later." Timeline: The issue began on May 1, 2026 at 00:10 UTC and was resolved on May 1, 2026 at 03:30 UTC Cause: The failures were caused by intermittent 502/504 errors returned by the HubSpot events API endpoint, which led to sync disruptions. Resolution: The issue resolved automatically without any intervention from the Fivetran side.
Notice April 30, 2026 Fivetran: Syncs Are Intermittently Failing with "UNAUTHENTICATED: Token" Errors –
Started Apr 30, 2026, 05:30 PM UTC· resolved Apr 30, 2026, 05:30 PM UTC
- resolved Apr 30, 2026, 06:40 PM UTC
Incident Summary Description: We identified an issue where services were intermittently failing with the error: "UNAUTHENTICATED: Token", resulting in connector sync failures during specific time windows. Timeline: This issue began on 2026-04-30 at 10:00 UTC and was resolved on 2026-04-30 at 16:30 UTC. Customers might have experienced failures around scheduled deployment times (10:00, 13:00, and 16:00 UTC), with recovery shortly after. Root Cause: A recent internal change led to intermittent timeouts during authentication token validation, which triggered "UNAUTHENTICATED: Token" errors and caused some syncs to fail. Resolution: We implemented a fix to ensure sufficient time for token validation, preventing further sync failures. All services are now operating normally.
Minor April 28, 2026 3rd Party: Qualtrics connector syncs failing with error "Ticket export failed." 2h 48m Qualtrics
Started Apr 28, 2026, 03:05 PM UTC· resolved Apr 28, 2026, 05:54 PM UTC
- identified Apr 28, 2026, 03:05 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 28, 2026, 03:41 PM UTC
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
- monitoring Apr 28, 2026, 04:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 28, 2026, 05:54 PM UTC
Instance rates have returned to normal levels, and affected connectors are now syncing successfully. Incident Summary Description: We identified an issue with Qualtrics connections where syncs were failing with a "Ticket export failed" error. Timeline: The issue began on April 28, 2026 at 11:30 AM UTC and was resolved at 4:10 PM UTC. Cause: The failures were caused by an issue with the Ticket Export endpoint on the Qualtrics side, leading to sync disruptions. More details: https://status.qualtrics.com/incidents/wj65y7rwfx2j Resolution: The issue was resolved once Qualtrics fixed the problem on their end.
Major April 28, 2026 Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired" 13h 46m Microsoft Lists, SharePoint
Started Apr 28, 2026, 01:10 AM UTC· resolved Apr 28, 2026, 02:57 PM UTC
- identified Apr 28, 2026, 09:50 AM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 28, 2026, 09:51 AM UTC
Fivetran's OAuth app secret key has expired, and the team is working on creating new secret key credentials to fix the issue.
- monitoring Apr 28, 2026, 09:52 AM UTC
A new secret key credential has been created to resolve the issue. Syncs are now recovering, and we are monitoring the results.
- monitoring Apr 28, 2026, 10:26 AM UTC
We have updated all the regions with the new secret keys and will continue to monitor the connections.
- resolved Apr 28, 2026, 02:57 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 SharePoint and Microsoft Lists connections which resulted in syncs failing with a "Authentication failed: The client secret or certificate has expired" error. Timeline: This issue began on 2026-04-27 at 22:20:00 UTC and was resolved on 2026-04-28 at 09:30:00 UTC Cause: The issue occurred due to Microsoft OAuth app credentials expiration.Due to this internal workflows failed to rotate the secret keys. Resolution: A fix has been implemented to update these secrets.
Minor April 27, 2026 3rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changes 7h 21m Amazon Selling Partner
Started Apr 27, 2026, 08:38 AM UTC· resolved Apr 27, 2026, 04:00 PM UTC
- identified Apr 27, 2026, 08:35 AM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 27, 2026, 08:38 AM UTC
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.
- monitoring Apr 27, 2026, 12:15 PM UTC
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.
- resolved Apr 27, 2026, 04:00 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 Amazon Selling Partner connections which resulted in syncs re-scheduling due to the rate limits on the GET_SALES_AND_TRAFFIC_REPORT. Timeline: This issue began on 2026-04-24 at 09:00:00 UTC and was resolved on 2026-04-27 at 14:15:00 UTC. Cause: We are experiencing the rate limits issue from the third party causing our connectors to reschedule for the GET_SALES_AND_TRAFFIC_REPORT. Resolution: A fix has been implemented to skip the tables associated with this report and allowing the connections for a successful sync.
Minor April 26, 2026 3rd Party: Multiple Quickbooks connections sync failed due to source maintenance 2m QuickBooks
Started Apr 26, 2026, 07:00 AM UTC· resolved Apr 26, 2026, 07:02 AM UTC
- identified Apr 26, 2026, 07:00 AM UTC
The issue has been identified and we are working to resolve it.
- resolved Apr 26, 2026, 07:02 AM UTC
Incident Summary: Description: QuickBooks connections were failing due to the source-side maintenance window. Timeline: April 25, 2026, from 9:00 PM to 11:30 PM PT Cause: Source side maintenance Resolution: Automatically resolved after the maintenance window is over.
Minor April 25, 2026 3rd Party: Multiple Twitter Ads connections failing due to 500 errors 14h 35m X Ads
Started Apr 25, 2026, 10:55 PM UTC· resolved Apr 26, 2026, 01:30 PM UTC
- identified Apr 25, 2026, 10:55 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 26, 2026, 12:09 AM UTC
We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.
- identified Apr 26, 2026, 05:48 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 26, 2026, 12:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 26, 2026, 01:30 PM UTC
Incident Summary: Description: Multiple Twitter Ads connectors failed due to the Twitter Ads API returning persistent server errors (HTTP 500) on reporting endpoints. Timeline (UTC): Started at 25.04.2026 21:00 and Resolved 26.04.2026 11:50 Cause: The Twitter Ads API experienced an outage, returning repeated HTTP 500 Internal Server errors on the stats reporting endpoint (POST URI https://ads-api.twitter.com/12/stats/jobs/accounts/). Resolution: Deployed a fix/workaround that enables the connector to gracefully handle HTTP 500 errors from the Twitter Ads API. Affected accounts are now skipped with a customer-facing warning on the connector dashboard, sync progress is preserved for successful accounts, and skipped data is automatically retried on the next sync.
Minor April 24, 2026 3rd Party: Sync start delays caused by Azure outage in East-US-2 region 4h 14m General Services
Started Apr 24, 2026, 06:35 PM UTC· resolved Apr 24, 2026, 10:50 PM UTC
- identified Apr 24, 2026, 06:35 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 24, 2026, 06:58 PM UTC
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 Apr 24, 2026, 08:47 PM UTC
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 Apr 24, 2026, 09:49 PM UTC
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.
- resolved Apr 24, 2026, 10:50 PM UTC
Syncs have returned to normal and Azure looks to have completed the rollout of their fix. Azure will have a post mortem posted to their status page for the root cause of this incident: https://azure.status.microsoft/en-us/status
Notice April 23, 2026 3rd Party: Some Recharge connections are intermittently failing with 502 errors –
Started Apr 23, 2026, 06:00 PM UTC· resolved Apr 23, 2026, 06:00 PM UTC
- resolved Apr 23, 2026, 08:04 PM UTC
We have observed that instance rates have returned to normal levels, and the affected connectors are now syncing successfully. Incident Summary Description: We identified an issue with Recharge connections, where syncs were failing with a 502 error. Timeline: The issue began on 2026-04-23 at 15:45 UTC and was resolved at 17:38 UTC. Cause: The failures were caused by the intermittent unavailability of the Recharge API, leading to sync disruptions. More details are available on the recharge's status page: https://status.getrecharge.com/incidents/cbz3mcgf2lx5 Resolution: The issue was resolved automatically once the Recharge API resumed normal operation
Minor April 23, 2026 3rd Party: Some ServiceTitan connections are intermittently failing with an HTTP 500 Error –
Started Apr 23, 2026, 06:00 PM UTC· resolved Apr 23, 2026, 06:00 PM UTC
- resolved Apr 23, 2026, 07:46 PM UTC
Description: We identified an issue affecting ServiceTitan connectors, which resulted in syncs failing with an HTTP 500 error. Timeline: This issue began on 2026-04-23 at 17:55 UTC and was resolved on 2026-04-23 at 18:34 UTC. Cause: The failures were due to a temporary service outage on ServiceTitan’s end, disrupting sync processes. Resolution: The issue was resolved once ServiceTitan deployed a fix on their end
Minor April 23, 2026 Fivetran: Some syncs are failing starting at 8AM Pacific time. 2h 19m General Services
Started Apr 23, 2026, 05:20 PM UTC· resolved Apr 23, 2026, 07:40 PM UTC
- identified Apr 23, 2026, 05:20 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring Apr 23, 2026, 05:20 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 23, 2026, 07:00 PM UTC
In the last hour, we have observed sync failure rates drop to normal rates. We are continuing to monitor.
- resolved Apr 23, 2026, 07:40 PM UTC
We have resolved this incident.
Minor April 21, 2026 3rd Party: Multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453) 5h 24m X Ads
Started Apr 21, 2026, 10:00 PM UTC· resolved Apr 22, 2026, 03:25 AM UTC
- identified Apr 21, 2026, 10:00 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring Apr 22, 2026, 12:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 22, 2026, 03:25 AM UTC
This incident has been resolved. We have observed that error rates have returned to normal levels, and the service is operating as expected. Incident Summary Description: We identified an issue affecting multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453) Timeline: The issue began on 2026-04-21 20:43 UTC and was resolved on 2026-04-22 02:23 UTC. Cause: X API started to fail report GZIP file authenticated download requests. Resolution: Authentication has been removed from GZIP file download requests.
Minor April 21, 2026 3rd Party: Apple App Store Connectors are failing with `Reporter is currently unavailable` 10m General Services
Started Apr 21, 2026, 04:30 AM UTC· resolved Apr 21, 2026, 04:41 AM UTC
- identified Apr 21, 2026, 04:30 AM UTC
The issue has been identified and we are working to resolve it.
- monitoring Apr 21, 2026, 04:30 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 21, 2026, 04:41 AM UTC
We have resolved this incident. Incident Summary Description: We identified an issue affecting Apple App Store connections, which were failing with the error: “Unknown failure. This request can not be processed right now Reporter is currently unavailable.” Timeline: The issue began on April 20th at 22:45 UTC and was resolved on April 21st at 01:20 UTC. Cause: The sync failure was caused by an intermittent issue on the third-party side. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.
Notice April 16, 2026 Fivetran: Hybrid deployment syncs are delayed –
Started Apr 16, 2026, 06:00 PM UTC· resolved Apr 16, 2026, 06:00 PM UTC
- resolved Apr 17, 2026, 12:58 AM UTC
This incident has been resolved. Incident Summary Description: We identified an issue where connectors using the Hybrid Deployment agent were unable to schedule new sync jobs. Timeline: This issue began on 2026-04-15 18:30 UTC and was resolved at 2026-04-16 23:20 UTC. Cause: The issue was caused by a recent code change. Resolution: The changes have been reverted, and the HD Agents affected will require a restart. During the restart, the latest update will be automatically applied, resolving the issue and preventing recurrence. Steps to restart your agent: For Docker and Podman deployments: ./hdagent.sh stop ./hdagent.sh start For Kubernetes deployments: 1. Get the HD Agent pod: kubectl get pod -n -l app.kubernetes.io/name=hd-agent 2. Kill the pod, which will force it to restart and pull the latest image kubectl delete pod
Minor April 14, 2026 3rd Party: Some Twitter Ads connections are failing due to a null primary key exception 7h 21m X Ads
Started Apr 14, 2026, 04:40 PM UTC· resolved Apr 15, 2026, 12:01 AM UTC
- identified Apr 14, 2026, 04:40 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 14, 2026, 07:21 PM UTC
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.
- monitoring Apr 14, 2026, 10:48 PM UTC
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.
- resolved Apr 15, 2026, 12:01 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 Twitter Ads which resulted in syncs failing with a "Null primary key found" error. Timeline: This issue began on 2026-04-14 at 16:30 UTC and was resolved at 23:30 UTC. Cause: Twitter API started returning null values in a primary key field (segment) for some reports, causing sync failures. Resolution: Twitter resolved the issue within the source: https://devcommunity.x.com/t/x-api-service-outage/262778 A hotfix was deployed by Fivetran to prevent further failures by skipping keys where the primary key was not present.