CloudFlare is only showing data from DNS queries to their 1.1.1.1 service. Twitter also happened to introduce rate limits at the same time Threads was released.

CloudFlare is only showing data from DNS queries to their 1.1.1.1 service. Twitter also happened to introduce rate limits at the same time Threads was released. While the article isn't saying it directly, it seems to be implying that Threads is causing this dip in requests, when in reality the majority of Twitter users are now making fewer requests to the website due to rate limits. Another point in the article suggests also that the large number of Threads users were never Twitter users in the first place. So how could Threads have caused such a massive drop in Twitter DNS queries? > 'Threads is being touted by Meta executives as a more positive “public square” for communities “that never really embraced Twitter.”'