Twitter search scrapes failing with ScraperException: blocked (404) (or non-200 status code (404))

[JustAnotherArchivist]

Twitter scrapes may fail with blocked (404) (or, on older versions, non-200 status code (404)).

Before filing an issue about this, please confirm that:

• you are using the latest version of snscrape, and
• you are not using a proxy or VPN, and
• you are not using a cloud computing provider such as AWS or GCP, and
• you can run the same search query successfully in a browser (in a private window/without prior cookies) from the same machine.

If all four are true, please proceed with filing a bug report including a debug log and confirmation of the above. If any of these four things is not true, do not file an issue; it indicates an IP ban, and there is nothing I or snscrape can do about that. If your issue is missing confirmation, it will be closed with a reference to this.