Twitter API Status

Streaming and Historical Endpoints Irregularity
Incident Report for Twitter
This incident was resolved at 04:18 UTC on February 12th.

We identified that this irregularity prevented a small percentage of cards from being hydrated on the way out the door, which also prevented the Tweets containing those cards from delivering via our streaming endpoints or the Replay and Historical PowerTrack APIs.

While we do recommend for you to use the premium or enterprise Search APIs to backfill the Tweets that you may have missed from 02/11/2020 17:00 UTC through 02/12/2020 04:17 UTC, we do not have any operators that you can use to easily identify the Tweets that you may have missed. Our apologies for the inconvenience.
Posted Feb 12, 2020 - 05:05 UTC
We are continuing to work on a fix for this issue.
Posted Feb 12, 2020 - 04:29 UTC
We have identified that this irregularity preventing some Tweets that include cards - including all polls - are not delivering via our enterprise, standard, and Labs streaming endpoints, not including the Compliance Firehose. Some of these Tweets that didn't deliver via the streaming endpoints may not deliver via the Historical PowerTrack API or the PowerTrack Replay API either.

We are still working to identify which other cards types were affected and are working on implementing a fix.
Posted Feb 12, 2020 - 04:14 UTC
Our investigations suggest that this irregularity is affecting more than just our Enterprise volume streams products. In addition to the Enterprise PowerTrack, Firehose Decahose, and Language Firehoses, this irregularity is affecting the Enterprise Historical PowerTrack and Replay API, Labs filter/stream and sample/stream endpoints, and standard filter/stream and sample/stream endpoints.

We are still investigating the issue. More details to come.
Posted Feb 12, 2020 - 02:44 UTC
The Streaming Twitter data team is currently investigating an instability in streaming delivery for some endpoints, including the Firehose API, that may have prevented some Tweets or enrichments from delivering. This irregularity started around 17:00 UTC on February 11th. We will provide an update as soon as we have more information.
Posted Feb 12, 2020 - 02:16 UTC
This incident affected: Enterprise Volume Streams & PowerTrack, Enterprise and Premium Historical APIs, Ads API, and Twitter Developer Labs.