3rd Party: Few Taboola connections are failing with the 404 for /campaigns/ endpoint

Incident Report for Fivetran

Resolved

This incident has been resolved. We’ve confirmed that sync rates have returned to normal, and all affected Taboola connections are syncing successfully.

Incident Summary
Description:
Some Taboola connector syncs were failing due to intermittent 404 errors returned by the Taboola API.

Timeline:
This issue began on 30 January 2026 at 01:30 PM UTC and was resolved on 30 January 2026 at 06:40 PM UTC.

Cause: Multiple Taboola API endpoints intermittently returned 404 errors, which caused sync failures.

Resolution: The Taboola support team identified and resolved the issue on their end. As an additional long-term solution, we deployed a Hotfix to improve retry handling for 404 responses. With these changes in place, syncs have resumed successfully, and connections are operating normally.
Posted Jan 30, 2026 - 20:48 UTC

Update

The Taboola support team has confirmed and resolved an issue on their end that caused intermittent 404 errors across multiple API endpoints.

As a long-term solution, we’ve also deployed a Hotfix to improve retry handling for 404 errors. Syncs have resumed successfully, and affected connections are operating normally. We’ll continue to monitor for stability.
Posted Jan 30, 2026 - 20:25 UTC

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Jan 30, 2026 - 18:00 UTC

Update

We’ve identified an issue with the Taboola connector, where multiple API endpoints began intermittently returning 404 errors starting around 13:30 UTC, causing some syncs to fail.
Our team is increasing retry handling to prevent sync failures and is actively monitoring the situation.
Posted Jan 30, 2026 - 16:15 UTC

Identified

The issue has been identified and we are working to resolve it.
Posted Jan 30, 2026 - 15:20 UTC
This incident affected: Marketing connectors (Taboola).