Use Cases
Software Products MSPs Schools Development & Marketing DevOps Agencies Help Desk
 
Internet Status Blog Pricing Log In Try IsDown for free now

Outage in Fivetran

3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) error

Resolved Minor
April 07, 2026 - Started about 17 hours ago - Lasted about 7 hours
Official incident page

Incident Report

Summary AI Generated

Fivetran's Twitter Ads and Twitter Organic connections experienced sync failures for 6.9 hours due to HTTP 503 (Service Unavailable) errors from Twitter's API endpoints. The issue was caused by Twitter's '/stats/jobs/accounts/' endpoint returning service unavailable errors, preventing data synchronization. Fivetran resolved the incident by deploying a hotfix that handles 503 errors and implements retry logic for failed endpoints.

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

Need to monitor Fivetran outages?

  • Monitor all your external dependencies in one place
  • Get instant alerts when outages are detected
  • Create a public or private status page for your customers
  • One place for your team to see all your services
Latest Updates ( sorted recent to last )
RESOLVED about 10 hours ago - at 04/07/2026 11:17PM

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 503 (Service Unavailable)" error.

Timeline:
This issue began on 2026-03-07 at 15:00 UTC and was resolved at 23:00 UTC.

Cause:
The Reddit 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 retry failed endpoints.

MONITORING about 10 hours ago - at 04/07/2026 10:47PM

The hotfix to handle 503 errors and attempt retries on failed endpoints has been deployed. We have confirmed a significant drop in sync failures as a result and will continue monitoring for any further failures.

IDENTIFIED about 11 hours ago - at 04/07/2026 09:50PM

A hotfix will be deployed to handle 503 errors from the Twitter API and to skip failing endpoints after several retries.

We are still waiting for an update from X regarding the issue:
https://devcommunity.x.com/t/503-error-while-requesting-12-stats-jobs-accounts-accountid/262061

IDENTIFIED about 16 hours ago - at 04/07/2026 05:23PM

We’ve logged an issue with the Twitter support team and will share updates shortly.
Link: https://devcommunity.x.com/t/503-error-while-requesting-12-stats-jobs-accounts-accountid/262061

IDENTIFIED about 16 hours ago - at 04/07/2026 05:18PM

We have identified that the '/stats/jobs/accounts/' endpoint is returning HTTP 503 (Service Unavailable), impacting syncs.

IDENTIFIED about 17 hours ago - at 04/07/2026 04:30PM

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

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6020 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook