Fivetran Outage History

Fivetran is up right now

Pingoru has recorded 102 incidents for Fivetran: 102 in the last 12 months and 0 in the last 90 days.

Source: status.fivetran.com

102incidents recorded
102last 12 months
0last 90 days
12 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Fivetran in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20263194 of 720 (13%)
May 202626366 of 744 (49%)
June 2026748 of 720 (7%)
July 202637 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 592 (0%)

Incidents, newest first

Minor April 11, 2026 3rd Party: Twitter Ads and Twitter Organic connector sync failures due to Bad Authentication data (code 215) error 3h 51m X Ads

Started Apr 11, 2026, 10:45 PM UTC· resolved Apr 12, 2026, 02:36 AM UTC

  1. identified Apr 11, 2026, 10:45 PM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Apr 11, 2026, 11:18 PM UTC

    Connectors are failing with a “Bad Authentication data” error (code 215) while fetching successful async job results.

  3. monitoring Apr 12, 2026, 12:07 AM UTC

    A fix has been implemented, and we are monitoring the results.

  4. resolved Apr 12, 2026, 02:36 AM UTC

    This incident has been resolved. Incident Summary Description: Twitter API started returning a Bad Authentication data error (code 215) while fetching successful async job results. Timeline: Impact start time around April 11th, 9:30 PM UTC to April 11th 01:57 UTC Cause: 3rd party error on Twitter side Resolution: We have implemented a workaround that skips the problematic endpoints for problematic accounts when this error occurs, and connectors are now back to normal.

Read the full incident report →

Minor April 11, 2026 3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to URI is not absolute error with HTTP 500 Response 2h 53m X Ads

Started Apr 11, 2026, 11:55 AM UTC· resolved Apr 11, 2026, 02:48 PM UTC

  1. identified Apr 11, 2026, 11:55 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Apr 11, 2026, 01:08 PM UTC

    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"

  3. monitoring Apr 11, 2026, 01:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 11, 2026, 02:48 PM UTC

    Incident Summary. Description: Twitter API started returning Internal Server Error with code 500 when we try to fetch reports. Timeline: Impact start time around April 10th 21:54:44 UTC to April 11th 12:47:37 UTC Cause: 3rd party error on twitter side Resolution: We have implemented a workaround for this by skipping reports for problematic accounts and connectors are back to normal.

Read the full incident report →

Minor April 10, 2026 Fivetran: Transformation jobs are failing with "UnsatisfiedDependencyException" error 1h 11m Transformations

Started Apr 10, 2026, 12:34 AM UTC· resolved Apr 10, 2026, 01:45 AM UTC

  1. identified Apr 10, 2026, 12:20 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Apr 10, 2026, 12:34 AM UTC

    We are actively working on a fix for this issue. This issue is currently impacting dbt core and Quickstart transformations

  3. monitoring Apr 10, 2026, 12:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 10, 2026, 01:45 AM UTC

    This incident has been resolved. Incident Summary Description: We identified an issue where dbt core and Quickstart transformation jobs are failing with "UnsatisfiedDependencyException" error. Timeline: The issue began on April 10, 2026 at 00:40 UTC and was resolved on April 10, 2026 at 01:30 UTC. Cause: The issue was caused by a recent code change made to the transformation. Resolution: Engineering identified the root cause and reverted the recent changes. After deploying the revert, the transformation resumed normal operation.

Read the full incident report →

Minor April 8, 2026 Fivetran: Fivetran : Few Amazon Selling partner connections are failing for the all_listings_report 3h 2m Amazon Selling Partner

Started Apr 08, 2026, 12:50 PM UTC· resolved Apr 08, 2026, 03:52 PM UTC

  1. identified Apr 08, 2026, 12:50 PM UTC

    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

  2. monitoring Apr 08, 2026, 02:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 08, 2026, 03:52 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 failing with a "Cannot invoke "com.fivetran.platform.interfaces.connector.SharedContext.safeFileBufferFactory()" because "this.sharedContext" is null" error. Timeline: This issue began on April 8, 2026 at 11:00 AM UTC and was resolved on April 8, 2026 at 2:30 PM UTC. Cause: A bug has been introduced on our end due to which we started hitting context being null error . Resolution: A fix has been implemented on our end to mitigate the issue.

Read the full incident report →

Notice April 7, 2026 3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) error –

Started Apr 07, 2026, 11:30 PM UTC· resolved Apr 07, 2026, 11:30 PM UTC

  1. resolved Apr 08, 2026, 08:38 PM UTC

    This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connectors are syncing successfully. Incident Summary Description: We identified an issue with Twitter Ads and Twitter Organic connections, which resulted in sync failures with an "HTTP 503 (Service Unavailable)" error. Timeline: This issue began on 2026-04-07 at 15:00 UTC and was resolved at 23:00 UTC. Cause: The Twitter Ads API '/stats/jobs/accounts/' endpoint started returning HTTP 503 (Service Unavailable) errors. Resolution: A hotfix was deployed to handle 503 errors, as well as to retry failed endpoints.

Read the full incident report →

Notice April 7, 2026 3rd Party: Delay in log delivery in customer's external log due to an issue with our external logging services –

Started Apr 07, 2026, 04:30 AM UTC· resolved Apr 07, 2026, 04:30 AM UTC

  1. resolved Apr 07, 2026, 10:24 AM UTC

    This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue with our external logging services which resulted in delay in log delivery in customer's external log. Timeline: This issue began on 2026-04-07 at 07:50 UTC and was resolved on 2026-04-07 at 10:00 UTC. Cause: An outage in the external logging API caused a buildup of log messages in our internal queue, impacting external logging services. Resolution: This issue has been resolved on the third-party end and our instances are returned to normal.

Read the full incident report →

Minor April 4, 2026 3rd Party: Awin connection syncs are failing with 500 internal server error for transaction endpoint 5h 5m Awin

Started Apr 04, 2026, 08:05 AM UTC· resolved Apr 04, 2026, 01:10 PM UTC

  1. identified Apr 04, 2026, 08:05 AM UTC

    The issue has been identified as originating from the source side and we are working to resolve it.

  2. identified Apr 04, 2026, 08:44 AM UTC

    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.

  3. monitoring Apr 04, 2026, 10:52 AM UTC

    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.

  4. resolved Apr 04, 2026, 01:10 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 Awin connections which resulted in syncs failing with a 500 internal server error for Transaction endpoint. Timeline: This issue began on 2026-04-04 at 06:40 AM UTC and was resolved on 2026-04-04 at 10:00 AM UTC. Cause: This was determined to be a source-side issue. Resolution: We’ve implemented a workaround by skipping the Transaction endpoint sync, and the connections are now syncing successfully. We’ve also reached out to Awin Support for more details on these failures. Once the issue on the source side is resolved, the Transaction table will automatically resume syncing data. Additionally, the Transaction table runs a weekly override re-sync, so any skipped data will be backfilled during that process.

Read the full incident report →

Notice April 2, 2026 3rd Party: Snapchat Ads connections failing with "SSLHandshakeException" –

Started Apr 02, 2026, 07:00 PM UTC· resolved Apr 02, 2026, 07:00 PM UTC

  1. resolved Apr 02, 2026, 07:29 PM UTC

    This incident has been fully resolved. Error rates have returned to normal levels, and all affected connections are now running successfully. Incident Summary Description: We identified an issue where Snapchat Ads connection syncs were intermittently failing with the error "javax.net.ssl.SSLHandshakeException" Timeline: The issue began on April 2nd at 17:55 UTC and was resolved by 18:20 UTC. Root Cause: The failures were caused by an intermittent SSL validation issue on the source side affecting the Snapchat API endpoint. Resolution: No action or code changes were required from our end. The issue resolved automatically once the Snapchat API resumed normal operation.

Read the full incident report →

Minor April 2, 2026 Fivetran: SQL Server TELEPORT and Epic CSA Connector POTENTIAL Failures Due to Unsupported Type in VIEW tables 3h 37m SQL Server, Epic Clarity

Started Apr 02, 2026, 05:45 PM UTC· resolved Apr 02, 2026, 09:22 PM UTC

  1. identified Apr 02, 2026, 05:45 PM UTC

    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

  2. identified Apr 02, 2026, 06:37 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Apr 02, 2026, 09:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 02, 2026, 09:22 PM UTC

    This incident has been resolved. Incident Summary Description: We identified an issue affecting the SQL Server (Teleport) and Epic CSA connectors, where syncs were failing with the following error: java.lang.IllegalArgumentException: No enum constant com.fivetran.integrations.sql_server.connector.schema.SqlServerType.SYSNAME Timeline: The issue began on April 2, 2026, at 15:07 UTC and was resolved on April 2, 2026, at 20:49 UTC. Cause: A recent deployment introduced an issue impacting views in the Epic CSA and SQL Server (Teleport) connectors. Resolution: The deployment was rolled back, and a hotfix was applied, restoring normal operations.

Read the full incident report →

Minor April 2, 2026 3rd Party: Multiple Twitter Ads connections are failing with an HTTP 500 Internal Server Error 7h 11m X Ads

Started Apr 02, 2026, 10:29 AM UTC· resolved Apr 02, 2026, 05:40 PM UTC

  1. identified Apr 02, 2026, 10:20 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Apr 02, 2026, 10:29 AM UTC

    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.

  3. monitoring Apr 02, 2026, 02:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Apr 02, 2026, 02:51 PM UTC

    A fix has been implemented and the connections are recovering from the failure. We'll continue to monitor the results.

  5. resolved Apr 02, 2026, 05:40 PM UTC

    We have resolved this incident.

Read the full incident report →

Minor April 1, 2026 3rd Party: Some Reddit Ads connections are failing with an HTTP 500 Internal Server error 3h 49m Reddit Ads

Started Apr 01, 2026, 07:30 PM UTC· resolved Apr 01, 2026, 11:19 PM UTC

  1. identified Apr 01, 2026, 07:30 PM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Apr 01, 2026, 07:50 PM UTC

    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.

  3. monitoring Apr 01, 2026, 10:26 PM UTC

    The issue has been resolved from Reddit and a hotfix has also been released to avoid sync failures due to 500 errors. We will continue monitoring for any further failures.

  4. resolved Apr 01, 2026, 11:19 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 Reddit Ads which resulted in syncs failing with a "HTTP 500 (Internal Server Error)" error. Timeline: This issue began on April 1st at 16:00 UTC and was resolved on the same day at 21:30 UTC. Cause: The Reddit Ads API started returning 500 failures to connector requests. Resolution: The 500 errors were resolved source-side and a hotfix has been implemented to catch similar failures in the future.

Read the full incident report →

Minor April 1, 2026 3rd Party: Some GitHub connections are intermittently failing with the error "No server is currently available to service your request" –

Started Apr 01, 2026, 01:30 PM UTC· resolved Apr 01, 2026, 01:30 PM UTC

  1. resolved Apr 01, 2026, 04:13 PM UTC

    This incident has been resolved. We observed error rates returning to normal levels, and all affected connections are now running successfully. Incident Summary Description: We identified an issue where GitHub connection syncs were intermittently failing with the error: "No server is currently available to service your request." Timeline: The issue began on April 1st at 10:00 UTC and was resolved by 13:00 UTC. Cause: The failures were caused by intermittent unavailability of the GitHub API, which led to sync disruptions. Resolution: The issue was resolved automatically once the GitHub API resumed normal operation.

Read the full incident report →

Minor March 31, 2026 Fivetran: Few Pipedrive connections are failing with the Null exception. 1h 6m Pipedrive

Started Mar 31, 2026, 03:40 PM UTC· resolved Mar 31, 2026, 04:47 PM UTC

  1. identified Mar 31, 2026, 03:40 PM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring Mar 31, 2026, 04:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 31, 2026, 04:47 PM UTC

    Description: We identified an issue affecting the Pipedrive connection, which resulted in syncs failing with Null exception: Cannot invoke "java.time.temporal.Temporal.until(java.time.temporal.Temporal, java.time.temporal.TemporalUnit)" because "startInclusive" is null Timeline: This issue began on March 31, 2026 at 11:06 UTC and was resolved on March 31, 2026 at 16:20 UTC. Cause: A configuration issue impacted existing connections. Resolution: Applied a fix to improve handling and prevent the issue.

Read the full incident report →

Minor March 30, 2026 3rd Party: Multiple Twitter Ads and Twitter Organic Connections Failing with error "HTTP 503 Service Unavailable" 19h 24m X Organic, X Ads

Started Mar 30, 2026, 10:00 PM UTC· resolved Mar 31, 2026, 05:25 PM UTC

  1. identified Mar 30, 2026, 05:55 PM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 30, 2026, 06:09 PM UTC

    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

  3. identified Mar 31, 2026, 03:56 AM UTC

    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.

  4. identified Mar 31, 2026, 11:56 AM UTC

    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.

  5. monitoring Mar 31, 2026, 03:54 PM UTC

    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

  6. resolved Mar 31, 2026, 05:25 PM UTC

    This incident has been resolved. We have observed that error rates have returned to normal levels, and the Twitter Organic and Twitter Ads services are operating as expected. Incident Summary Description: We identified an issue affecting multiple Twitter Organic and Twitter Ads connections, which were failing with the error: “HTTP 503 Service Unavailable.” Timeline: The issue began on March 30th at 00:00 UTC and was resolved on March 31st at 16:30 UTC. Cause: The X API stopped returning rate limit information in the response headers. This caused Twitter Organic and Twitter Ads connections to encounter 429 errors, leading to sync failures. Resolution: X has resolved their API issue. Additionally, we deployed a hotfix to ensure that if the source hits account-level rate limits and does not return response headers, it will no longer cause sync failures. Instead, the connections will be automatically rescheduled.

Read the full incident report →

Notice March 30, 2026 3rd Party: Criteo Connection Sync Failures due to the 503 and 504 errors. –

Started Mar 30, 2026, 10:15 AM UTC· resolved Mar 30, 2026, 10:15 AM UTC

  1. resolved Mar 30, 2026, 10:43 AM UTC

    Description: We identified an issue affecting the Criteo connector, which resulted in syncs failing with 503 Service Unavailable and 504 Gateway Time-out errors. Timeline: This issue began on March 30, 2026 at 08:17 UTC and was resolved on March 30, 2026 at 09:17 UTC. Cause: The failures were caused by an outage on the third-party side, as confirmed on their official status page. https://status.criteo.com/incidents/dj24tx2vf4w3 Resolution: The issue was resolved after third-party restored their services. Syncs resumed normal operation once the upstream outage was mitigated.

Read the full incident report →

Minor March 26, 2026 Fivetran: OAuth Authentication Issues Affecting Multiple Connections 1h 7m General Services

Started Mar 26, 2026, 04:05 PM UTC· resolved Mar 26, 2026, 05:12 PM UTC

  1. identified Mar 26, 2026, 04:05 PM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring Mar 26, 2026, 05:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 26, 2026, 05:12 PM 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 with the OAuth Authentication that is affecting multiple connections, resulting in a 404 error. Timeline: The issue began on 26/03/2026 at 09:09 UTC and was resolved on 26/03/2026 at 16:42 UTC. Cause: During an ingress upgrade, an error caused OAuth callback requests to return HTTP 404 responses. This led to authentication failures for connections relying on OAuth. Resolution: The change was reverted, which restored normal OAuth functionality for Fivetran connections.

Read the full incident report →

Notice March 26, 2026 Fivetran: Intermittent REST API requests timeouts. –

Started Mar 26, 2026, 10:00 AM UTC· resolved Mar 26, 2026, 10:00 AM UTC

  1. resolved Mar 26, 2026, 02:00 PM UTC

    Incident Summary Description: We identified an issue where some Fivetran REST API requests were timing out. Timeline: The issue began on 26/03/2026 at 10:17 UTC and was resolved on 26/03/2026 at 12:05 UTC. Cause: The issue was caused by resource constraints in our infrastructure, causing timeouts when resources were unavailable. Resolution: We have increased resource limits to mitigate the issue, and we are not seeing connection failures after that change.

Read the full incident report →

Minor March 26, 2026 Fivetran: PostgreSQL Connections Using RDS Proxy Are Failing with the Error: The source database does not support a provided lock_timeout parameter 2h 27m General Services, Google Cloud SQL for PostgreSQL, PostgreSQL

Started Mar 26, 2026, 05:43 AM UTC· resolved Mar 26, 2026, 08:10 AM UTC

  1. identified Mar 26, 2026, 06:20 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 26, 2026, 06:24 AM UTC

    We have identified the root cause of the current errors as a recent code change. Our engineering team is currently developing a fix to restore full service.

  3. monitoring Mar 26, 2026, 08:10 AM UTC

    We have released a fix to resolve the identified issues. Affected services are beginning to recover, and we are closely monitoring the system to ensure continued stability.

  4. resolved Mar 26, 2026, 08:10 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 with the PostgreSQL Connections Using RDS Proxy Failing with the Error: The source database does not support a provided lock_timeout parameter Timeline: The issue began on 26/03/2026 at 05:40 UTC and was resolved on 26/03/2026 at 07:45 UTC. Cause: The issue was caused by a recent code change introducing a bug from Fivetran. Resolution: The bug was fixed and the connection services were restored.

Read the full incident report →

Minor March 26, 2026 Fivetran: Fivetran REST API Failing with 404 Errors 3h 49m Fivetran API

Started Mar 26, 2026, 04:35 AM UTC· resolved Mar 26, 2026, 08:25 AM UTC

  1. identified Mar 26, 2026, 04:35 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 26, 2026, 05:47 AM UTC

    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.

  3. identified Mar 26, 2026, 06:47 AM UTC

    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.

  4. monitoring Mar 26, 2026, 07:05 AM UTC

    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.

  5. resolved Mar 26, 2026, 08: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 with the Fivetran REST API that caused certain endpoint calls to fail with a 404 error. Timeline: The issue began on 25/03/2026 at 14:04 UTC and was resolved on 26/03/2026 at 06:55 UTC. Cause: The issue was caused by a recent change on our end. Resolution: The change was reverted, restoring normal API functionality.

Read the full incident report →

Minor March 26, 2026 3rd Party: Multiple Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable" 10h 10m X Ads

Started Mar 26, 2026, 03:30 AM UTC· resolved Mar 26, 2026, 01:40 PM UTC

  1. identified Mar 26, 2026, 03:30 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 26, 2026, 04:09 AM UTC

    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.

  3. identified Mar 26, 2026, 05:56 AM UTC

    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.

  4. identified Mar 26, 2026, 08:35 AM UTC

    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.

  5. monitoring Mar 26, 2026, 10:40 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Mar 26, 2026, 11:41 AM UTC

    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

  7. resolved Mar 26, 2026, 01:40 PM 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 with the multiple Twitter and Twitter Ads connections, which are failing with the error "HTTP 503 Service Unavailable". Timeline: The issue began on 26/03/2026 at 01:00 UTC and was resolved on 26/03/2026 at 14:30 UTC. Cause: A third-party issue caused Twitter and Twitter_Ads connections to fail. Resolution: X (Twitter) has fixed their API.

Read the full incident report →

Minor March 25, 2026 Fivetran: Multiple connectors under the BigQuery destination are failing with a "GCS_BG_STORAGE" error. 1h 38m Destinations

Started Mar 25, 2026, 01:20 AM UTC· resolved Mar 25, 2026, 02:59 AM UTC

  1. identified Mar 25, 2026, 01:20 AM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring Mar 25, 2026, 01:37 AM UTC

    Connections syncing to BigQuery destinations are impacted due to an internal configuration error. The issue has now been resolved, and we are monitoring sync.

  3. resolved Mar 25, 2026, 02:59 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 causing sync failures, with multiple connectors in the BigQuery destination failing due to a "GCS_BG_STORAGE" error. Timeline: This issue began on March 25, 2026, at 00:18 UTC and was resolved on March 25, 2026, at 01:49 UTC. Cause: Connections syncing to BigQuery destinations are impacted due to an internal configuration error. Resolution: The necessary steps were taken to resolve the internal configuration issue, after which instance rates returned to normal and the affected connectors resumed syncing successfully.

Read the full incident report →

Minor March 24, 2026 3rd Party: Mixpanel connections sync failing with Socket Timeout Error – Mixpanel

Started Mar 24, 2026, 05:30 AM UTC· resolved Mar 24, 2026, 05:30 AM UTC

  1. identified Mar 24, 2026, 05:30 AM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring Mar 24, 2026, 05:30 AM UTC

    The issue was caused by an intermittent issue on the third-party side, which was resolved automatically, and we are monitoring the sync.

  3. resolved Mar 24, 2026, 05:30 AM UTC

    We have resolved this incident. Description: We identified an issue where multiple Mixpanel connections are failing their sync with a socket timeout error due to an issue on the third-party side. Timeline: Incident Start: 2026-03-23 at 18:50 UTC Incident End: 2026-03-23 at 19:15 UTC Cause: The issue 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.

Read the full incident report →

Minor March 23, 2026 Fivetran: Some Box Connections are failing with HTTP "429 Too Many Requests" errors 3h 29m Box

Started Mar 23, 2026, 08:10 PM UTC· resolved Mar 23, 2026, 11:40 PM UTC

  1. identified Mar 23, 2026, 08:10 PM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring Mar 23, 2026, 08:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 23, 2026, 11:40 PM UTC

    Description: Some Box connections unexpectedly failed their sync runs, but recovered on subsequent runs. Timeline: Incident Start: 2026-02-23 at 16:30 UTC Incident End: 2026-02-23 at 18:00 UTC Cause: The issue appears to be caused by a temporary error in our credential handling service, but we are continuing to investigate this post incident resolution. Resolution: The App Store Connect Reporter is now available, and syncs are succeeding normally.

Read the full incident report →

Minor March 22, 2026 3rd Party: Some itunes_connect Connections Failing Due to Intermittent Apple App Store Connect Reporter Unavailability 1h General Services

Started Mar 22, 2026, 07:40 AM UTC· resolved Mar 22, 2026, 08:40 AM UTC

  1. identified Mar 22, 2026, 07:40 AM UTC

    We identified an issue with the itunes_connect Connections where sync is failing with the "Unknown failure" error.

  2. resolved Mar 22, 2026, 08:40 AM UTC

    Description: We identified an issue with Apple App Store Connect that caused sync failures due to intermittent unavailability of the App Store Connect Reporter. Timeline: This issue began on 22 March 2026 at 06:17 UTC and was resolved on 22 March 2026 at 07:14 UTC. Cause: The issue was caused by a temporary API failure on the App Store Connect side. Resolution: The App Store Connect Reporter is now available, and syncs are succeeding normally.

Read the full incident report →

Minor March 21, 2026 3rd Party: Snowflake Downtime Causing Sync Failures Across Multiple Connections Using Snowflake as Destination 53m Destinations, General Services

Started Mar 21, 2026, 09:37 AM UTC· resolved Mar 21, 2026, 10:30 AM UTC

  1. identified Mar 21, 2026, 07:05 AM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 21, 2026, 07:07 AM UTC

    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/

  3. monitoring Mar 21, 2026, 07:30 AM UTC

    Snowflake has reported recovery for US regions, and we are monitoring to ensure all syncs return to normal. More details: https://status.snowflake.com/

  4. monitoring Mar 21, 2026, 09:38 AM UTC

    We are continuing to monitor to ensure all syncs return to normal. More details: https://status.snowflake.com/

  5. resolved Mar 21, 2026, 10:30 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 where multiple connection syncs under the Snowflake destination are failing due to a Snowflake Downtime. Timeline: This issue began on 21-03-2026 at 05:26:30 UTC and was resolved on 21-03-2026 at 06:17:30 UTC. Cause: External Snowflake incident affecting the impacted AWS region(s), leading to elevated Snowflake exceptions and downstream sync failures. Resolution: The issue was resolved on the Snowflake side, and connections are now syncing successfully

Read the full incident report →