Resolved -
Streaming data is now delivering on time, as expected. For the next ~3 weeks, requests to the Search endpoints (enterprise, premium and v2) may only return ~99% of Tweets created between February 24th ~18:00 UTC - March 3rd 19:00 UTC.
Mar 4, 16:56 UTC
Update -
While streaming products should now be operating as expected, we are continuing to monitor the impact of Tweets served by historical endpoints such as the Search API. At this point, we know there are some Tweets that will not be returned by queries covering the impacted period (Feb 24 - March 3). The team is working to remedy this situation. We will provide further updates as they become available.
Mar 4, 01:16 UTC
Monitoring -
As of March 3rd 23:19 UTC, the re-streaming of data is now complete. As long as your app remained connected to the stream(s) during this time, Tweets would have eventually been delivered (albeit delayed). You should no longer experience delivery of delayed data through the stream(s).
Mar 3, 23:59 UTC
Identified -
We've identified an issue with approximately 1% of Tweet create events that occurred between February 24th ~18:00 UTC - March 3rd 19:00 UTC. These events were potentially not delivered via streaming connections and REST API requests that serve Tweets. We are in the process of replaying these events through the streaming endpoints, so you may see some data delivered that is up to 7 days old. For historical endpoints like the Search API, queries that cover the period February 24 - March 3 will no longer have potentially missing Tweets after re-streaming of the data is complete.
Mar 3, 23:34 UTC