These are measured numbers, not a marketing range. Every tweet Xanguard delivers is timed from the moment X says it was posted to the moment it first reaches our servers. This page publishes the result for all paid-plan accounts and refreshes every hour. Last update: 20 Sep 2026 21:00 UTC.
Tweet detection latency, paid plans
| Window | Tweets measured | p25 | Median (p50) | p90 | p95 | p99 |
|---|---|---|---|---|---|---|
| Last 24 hours | 12,563 | 208 ms | 263 ms | 362 ms | 435 ms | 900 ms |
| Last 7 days (16 Sep 2026 to 20 Sep 2026) | 60,167 | 204 ms | 262 ms | 374 ms | 461 ms | 921 ms |
| Share of tweets detected | Last 24 hours | Last 7 days |
|---|---|---|
| In under 500 ms | 96.9% | 96.1% |
| In under 1 second | 99.2% | 99.1% |
How we measure
- Start of the clock: the creation time X embeds in every tweet ID, to the millisecond.
- End of the clock: the first moment that tweet arrives on a Xanguard server.
- Sample: every tweet delivered for accounts tracked on paid plans (Tweet Alerts and the B2B API). Nothing is hand-picked, and we publish p95 and p99, not only the best case.
- Excluded: arrivals later than 10 minutes, which are recoveries after an outage rather than live detections. The free plan is not included because it runs on a slower cycle.
- Not included: the last hop to you. Telegram delivery typically adds 0.1 to 0.3 seconds. WebSocket transit depends on where your server is.
You can verify this yourself. Every B2B event carries both created_at (when X says the tweet was posted) and received_at (when we detected it), so your own logs show the same latency we publish here. The raw figures behind this page are also available as /speed.json.
Why a median and not a record
A single fastest detection says little about what you will get on a normal day. The median tells you what half of all tweets beat, and p95 and p99 tell you how bad the slow ones are. If you trade on tweets, the tail matters as much as the median, which is why all of them are on this page.
Want to check it on an account you care about? The Telegram bot tracks one account for free, and paid plans start at $19 a month for 10 accounts.
Frequently Asked Questions
Over the last 7 days, the median time from a tweet being posted to Xanguard detecting it was 262 ms on paid plans. 96.1% of tweets were detected in under 500 ms and 99.1% in under one second, measured across 60,167 tweets. The figures on this page refresh every hour from production data.
The time between the timestamp X assigns to the tweet when it is posted and the first moment that tweet reaches a Xanguard server. It covers every tweet delivered for accounts on paid plans. It does not include the final hop to your Telegram chat or WebSocket client. Telegram delivery typically adds 0.1 to 0.3 seconds.
No. The numbers on this page are for paid plans. The free plan uses a slower checking cycle and is meant for trying the product on one account.