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

Update timeline

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.