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 4, 2026, 03:05 UTCLast 24 hours
Sep 3, 2026, 03:05 UTC to Sep 4, 2026, 03:05 UTCLast 7 days
Aug 28, 2026, 03:05 UTC to Sep 4, 2026, 03: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 | 100 ms | 126 ms | 196 ms | 100 | 95 ms | 117 ms | 206 ms | 372 |
 CZ πΆ BNB@cz_binance: Open on X | 103 ms | 115 ms | 302 ms | 6 | 154 ms | 165 ms | 217 ms | 69 |
 toly πΊπΈ@toly: Open on X | 153 ms | 157 ms | 183 ms | 4 | 152 ms | 170 ms | 225 ms | 88 |
 Ansem πποΈ@blknoiz06: Open on X | 91 ms | 109 ms | 263 ms | 91 | 90 ms | 103 ms | 247 ms | 414 |
 Ozzy | ε₯₯ε
Ή πΊπΈπ¨π³πͺΆ@meadgod: Open on X | 114 ms | 139 ms | 334 ms | 14 | 90 ms | 102 ms | 234 ms | 131 |
 Binance@binance: Open on X | 175 ms | 268 ms | 751 ms | 14 | 166 ms | 201 ms | 377 ms | 167 |
 The White House@whitehouse: Open on X | 93 ms | 122 ms | 694 ms | 33 | 87 ms | 115 ms | 719 ms | 186 |
 Robinhood@robinhoodapp: Open on X | 107 ms | 186 ms | 392 ms | 4 | 107 ms | 136 ms | 323 ms | 28 |
 Solana@solana: Open on X | 121 ms | 158 ms | 241 ms | 41 | 140 ms | 164 ms | 256 ms | 274 |
 BNB Chain@bnbchain: Open on X | 141 ms | 192 ms | 310 ms | 21 | 143 ms | 176 ms | 310 ms | 142 |
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.