Fivetran

3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to URI is not absolute error with HTTP 500 Response

Minor Impact Monitoring Ongoing April 11, 2026

Incident Lifecycle

Identified Identified Monitoring

Incident Timeline

Monitoring
A fix has been implemented and we are monitoring the results.
Apr 11, 2026 at 1:14 PM UTC
Identified
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"
Apr 11, 2026 at 1:08 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Apr 11, 2026 at 11:55 AM UTC
Was your business affected by this Fivetran outage?
Set up instant alerts for Fivetran — be the first to know about outages via email, Slack, Teams, or Discord.
Set Up Alerts → View Fivetran History

Similar Fivetran Incidents

3rd Party: Sync failures due to Bad Authentication data (code 215) error Minor Apr 11, 2026 3rd Party: Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable" error Minor Apr 10, 2026 Transformation jobs are failing with "UnsatisfiedDependencyException" error Minor Apr 10, 2026 Fivetran : Few Amazon Selling partner connections are failing for the all_listings_report Minor Apr 8, 2026 3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) error Minor Apr 7, 2026