Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Fivetran

3rd Party: Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable" error

Resolved Minor
April 10, 2026 - Started 6 days ago - Lasted about 17 hours
Official incident page

Incident Report

Summary AI Generated

Fivetran's Twitter Ads and Twitter Organic connectors experienced sync failures for 17 hours due to the Twitter API returning HTTP 429 and 503 errors. The issue affected data synchronization from Twitter services, causing connectors to fail when attempting to retrieve data. Fivetran resolved the incident by deploying a hotfix that better handles API errors from Twitter and skips endpoints that continue to fail after retries.

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

Trusted by 1,000+ teams

The Status Page Aggregator with Early Outage Detection

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

Start Free Trial
  • No credit card
  • 14-day trial
  • 2-minute setup
IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 5 days ago - at 04/10/2026 09:09PM

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 Twitter Ads and Twitter Organic connectors which resulted in syncs failing with a "HTTP 503 Service Unavailable" error.

Timeline:
This issue began on 2026-04-10 at 04:00 UTC and was resolved at 20:30 UTC.

Cause:
The Twitter API started returning 429 and 503 errors when making requests for data.

Resolution:
A fix was deployed to better handle both errors from the Twitter API.

MONITORING 5 days ago - at 04/10/2026 07:58PM

A hotfix has been implemented, and affected connections are recovering. We are continuing to monitor results.

IDENTIFIED 5 days ago - at 04/10/2026 06:51PM

We're rolling out fixes to handle 429 and 503 errors more effectively. Endpoints that continue to fail after retries will now be skipped to ensure smoother syncs.

IDENTIFIED 5 days ago - at 04/10/2026 12:21PM

We are continuing to work on a fix for this issue.

IDENTIFIED 6 days ago - at 04/10/2026 09:59AM

The issue has been identified as originating from the third-party end, where the accounts endpoint is intermittently failing.

We are implementing a fix to address this, ensuring the exception is now properly detected and managed. We are continuing to monitor the situation closely.

IDENTIFIED 6 days ago - at 04/10/2026 06:09AM

There are no updates from Twitter on their status page: https://docs.x.com/status

We are looking into potential workarounds to address these failures and will provide further updates as soon as more information is available.

IDENTIFIED 6 days ago - at 04/10/2026 04:15AM

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 · 6320 services available

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