The data refreshes hourly. We measure from the X post's publication timestamp to the first time it reaches a TweetStream server.
Current X/Twitter measurements
The cards include qualifying posts from every monitored account. The table breaks out up to ten accounts individually.
Data through Sep 13, 2026, 05:05 UTCLast 24 hours
Sep 12, 2026, 05:05 UTC to Sep 13, 2026, 05:05 UTCLast 7 days
Sep 6, 2026, 05:05 UTC to Sep 13, 2026, 05:05 UTCServer detection is not customer delivery
The percentiles above end when a TweetStream server first receives the post. On non-Ultra plans, eligible X/Twitter posts can arrive up to 50 ms later than with Ultra Speed priority delivery.
Results by account
See the same measurements for each account.
| Account | Last 24 hours | Last 7 days | ||||||
|---|---|---|---|---|---|---|---|---|
| p25 | p50 median | p95 | Samples | p25 | p50 median | p95 | Samples | |
 Elon Musk@elonmusk: Open on X | 91 ms | 94 ms | 163 ms | 32 | 99 ms | 142 ms | 260 ms | 283 |
 CZ ๐ถ BNB@cz_binance: Open on X | 123 ms | 138 ms | 162 ms | 4 | 143 ms | 157 ms | 238 ms | 39 |
 toly ๐บ๐ธ@toly: Open on X | 168 ms | 189 ms | 272 ms | 53 | 145 ms | 168 ms | 235 ms | 247 |
 Ansem ๐๐๏ธ@blknoiz06: Open on X | 79 ms | 91 ms | 196 ms | 51 | 87 ms | 101 ms | 243 ms | 258 |
 Ozzy | ๅฅฅๅ
น ๐
ฟ๏ธ@meadgod: Open on X | 91 ms | 100 ms | 320 ms | 11 | 89 ms | 99 ms | 260 ms | 133 |
 Binance@binance: Open on X | 194 ms | 217 ms | 571 ms | 13 | 173 ms | 207 ms | 333 ms | 125 |
 Cobie@cobie: Open on X | 91 ms | 93 ms | 154 ms | 5 | 96 ms | 102 ms | 148 ms | 101 |
 Robinhood@robinhoodapp: Open on X | 87 ms | 87 ms | 87 ms | 1 | 96 ms | 152 ms | 191 ms | 21 |
 The White House@whitehouse: Open on X | 78 ms | 83 ms | 243 ms | 20 | 82 ms | 102 ms | 675 ms | 218 |
 ๅธๅฎBinanceๅ่ฏญ@binancezh: Open on X | 351 ms | 351 ms | 351 ms | 1 | 193 ms | 260 ms | 367 ms | 71 |
Download the data
Open the live report and measurement details as JSON, or download them as CSV.
How it is measured
Measurement
We measure from an X post's publication time to its first receipt at a TweetStream server.
Reading percentiles
p25, p50 and p95 show how quickly 25%, 50% and 95% of posts were detected. Lower is faster.
These figures measure server detection only. They do not include customer WebSocket receipt or execution latency.
Detection time can vary from one post to the next as platform load and other conditions change.
Your client's location affects the network path after TweetStream receives a post. Measure WebSocket receipt from your own host.