Users
Operationalp50
570 ms
p95
763 ms
Success
100%
p50 latency, last 24 h
90 days agoToday
API status, measured live.
Response times and success rates of the TwittrAPI API, measured on real calls and updated every minute.
Incident notices and the changelog are posted on Telegram.
All systems operational
Last 15 minutes, all read endpoints. Updated just now.
p50
1,080 ms
p95
2,486 ms
Success
99.95%
p50 latency, last 24 h
90 days agoToday
By endpoint group
Tweets
Operationalp50
889 ms
p95
1,521 ms
Success
100%
p50 latency, last 24 h
90 days agoToday
Search
Operationalp50
1,357 ms
p95
2,756 ms
Success
99.91%
p50 latency, last 24 h
90 days agoToday
Lists
Operationalp50
716 ms
p95
1,140 ms
Success
100%
p50 latency, last 24 h
90 days agoToday
Communities
Not enough datap50
–
p95
–
Success
–
p50 latency, last 24 h
Not enough calls in the last 24 h
90 days agoToday
Trends
Not enough datap50
–
p95
–
Success
–
p50 latency, last 24 h
Not enough calls in the last 24 h
90 days agoToday
Other
Not enough datap50
–
p95
–
Success
–
p50 latency, last 24 h
Not enough calls in the last 24 h
90 days agoToday
OperationalDegradedOutageNo data / too few calls
What is measured
Numbers come from real customer calls through the API gateway, not from synthetic probes. Latency is the time the gateway waits for the upstream answer (p50 = median, p95 = 95 % of calls were faster), taken from successful calls.
Success rate counts 2xx responses and 404 (a deleted tweet or unknown user is a correct answer) as success, and 5xx responses and timeouts as failures. Client errors such as a missing key, bad parameters or rate limits are left out, as are write actions (/client/*, /premium/*).
The banner covers the last 15 minutes. A group is degraded below 99 % success or with a p95 above 8 s, and down below 90 %. Periods with fewer than 20 calls show no value. Data refreshes every minute. Daily history starts from the day the status feed was switched on.
Payments
- Polygon top-ups (USDT, USDC)Operational
- Tron top-ups (USDT)Operational
- Litecoin top-upsOperational
Delayed: top-ups on that network are credited later than usual. Down: they are not being credited at the moment and are credited automatically once the connection is back.