TL;DR: X blocks search from every datacenter IP range. Your scraper isn't broken — your IP is. Here are the 4 approaches that still work, with code.
If you've built a Twitter scraper in the last few months, you've probably seen this: same code, worked yesterday, 404 Not Found today. No error message. No rate-limit headers. Just 404s.
It's not your code. X (Twitter) returns 404 for SearchTimeline requests from virtually every datacenter IP range — AWS, GCP, Azure, Hetzner, OVH, and even carrier CGNAT ranges. The endpoint works fine from a residential ISP and fails from a VPS with the exact same headers, cookies, and TLS fingerprint.
Let me walk through what still works in 2026, from easiest to hardest.
Option 1: Profile data — free, no browser, no login
Here's something most people miss: x.com serves profile pages server-rendered to logged-out visitors. No API key, no headless browser, no cookies.…