Twitter API latency benchmarks
How fast twitterapi.io answers, from our own logs over a 7-day window in 2026: stream pushes reach subscribers with a median of 265 ms, and a user profile lookup takes a median of 117 ms on our servers.
median stream push, all deliveries
of @elonmusk's tweets delivered within 500 ms
median server-side time, user profile lookup
Stream push latency
The Twitter stream pushes new tweets from the accounts you monitor to your endpoint. We time each delivery from the moment the tweet was created to the moment our server sent it to you.
| Sample | Median | p90 | Within 500 ms |
|---|---|---|---|
| All deliveries to subscribers | 265 ms | not published | more than half |
| @elonmusk tweets | 182 ms | 237 ms | 98% |
Delivery time varies by account. Some tweets can take longer; we're working on making delivery consistently fast for every monitored account.
Method · Per delivery: our server's send time minus the tweet's creation time (decoded from the tweet ID), over a 7-day window in 2026. Network time from our server to your endpoint is not included.
REST endpoint response times
Server-side processing time for five main read endpoints, p50 (median) and p90. The bar runs from p50 (dot) to p90 on a log scale.
- User profilep50 117 ms · p90 216 ms
- Tweets by IDp50 601 ms · p90 ~4.0 s
- Followersp50 905 ms · p90 1.45 s
- Advanced searchp50 981 ms · p90 1.85 s
- User timelinep50 1.25 s · p90 2.4 s
| Endpoint | p50 | p90 |
|---|---|---|
| User profile/twitter/user/info | 117 ms | 216 ms |
| Tweets by ID/twitter/tweets | 601 ms | ~4.0 s |
| Followers/twitter/user/followers | 905 ms | 1.45 s |
| Advanced search/twitter/tweet/advanced_search | 981 ms | 1.85 s |
| User timeline/twitter/user/last_tweets | 1.25 s | 2.4 s |
Method · Server-side processing time inside our application, successful (HTTP 200) responses only, over a 7-day window in 2026. Network time between you and our servers is not included, so the time you see end to end will be higher.
Measure it from your own server
curl can print the total time of one request. Run it a few times from the machine that will call the API; the result includes your network path, so expect it to sit above the server-side numbers.
curl -s -o /dev/null -w "total %{time_total}s\n" \
-H "x-api-key: $TWITTERAPI_IO_API_KEY" \
"https://api.twitterapi.io/twitter/user/info?userName=jack"Need a key for the header? Get an API key from the dashboard. How many requests per second you can send is on the rate limits page.
What a read costs next to the official X API
Speed is half the comparison; the other half is what each read costs. The official X API bills reads pay-per-use, per resource returned:
| Read | Official X API | twitterapi.io |
|---|---|---|
| Read one post (tweet) | $0.005 | $0.00015 ($0.15 per 1,000 tweets) |
| Read one user profile | $0.010 | $0.00018 ($0.18 per 1,000 profiles) |
Per post read that is about 33x less ($0.005 / $0.00015). Official prices are from X's own X API pricing page, checked in 2026; that route also needs an X developer account. Our full rate card is on the pricing page.
Try the numbers on your own workload.
Pay as you go, no subscription required. Point a monitor at the stream or time a few REST calls with the command above.
Get your API key