Fivetran Status

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 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.

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.

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.

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

Resolved: 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.

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 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

Resolved: We have resolved this incident.

Monitoring: A fix has been implemented and the connections are recovering from the failure.

We'll continue to monitor the results.

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

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.

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

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 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.

Monitoring: 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.

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.

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

Resolved: This incident has been resolved.

Incident Summary

Description: We identified an issue causing delays in log delivery to customers’ external logging systems.

Timeline: The issue began on April 1, 2026, at 00:20 UTC and was resolved on April 1, 2026, at 02:40 UTC

Cause: An outage in the external logging API “Splunk Log” caused a buildup of log messages in our internal queue, impacting both Splunk log delivery and other external logging services.

Resolution: We deployed a fix to prevent delays to other logging services. The issue has also been resolved on Splunk’s end.

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.

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

Resolved: 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.

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

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.

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.

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

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

Resolved: 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.

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.