Requests to Twitter API v2 endpoints should now be operational.
Replay is now available for recovery of data during the affected time period: 15:15 - 16:38 UTC April 17, 2021
Posted Apr 17, 2021 - 19:00 UTC
At the current time, connections to PowerTrack and Firehose should be available and delivering all data, operating as expected.
Affected timeframe between 15:27 - 16:40 UTC April 17, 2021.
Replay is not yet available for recovery for missing data.
Posted Apr 17, 2021 - 17:54 UTC
Customers may experience connection issues or volume drops on Firehose and Powertrack since 16:00 UTC today. We are continuing to investigate.
Replay is not yet available for data recovery.
Requests to Twitter API v2 endpoints may experience 5XX issues at this time.
Posted Apr 17, 2021 - 16:56 UTC
We are investigating reported issues with PowerTrack connections. At this time, we recommend keeping active connections to PowerTrack continuing to reconnect to PowerTrack with normal reconnection logic. We will update here as we have new information.
Posted Apr 17, 2021 - 14:59 UTC
The Twitter data team is investigating a possible system irregularity currently affecting all Twitter API v2 endpoints starting at 2021-04-17 12:00 UTC. The presence and scope of any developer impact has not been determined at this time, but we will provide an update as soon as we know more.
Posted Apr 17, 2021 - 13:00 UTC
This incident affected: Enterprise Volume Streams & PowerTrack, Enterprise and Premium Historical APIs, v2 streaming Tweets endpoints, v2 RESTful Tweets endpoints, and v2 RESTful users endpoints.