Latency
What our own load tests measured. A guide, not a promise.
Measured on production code on 30 and 31 October 2026, from the client side.
| endpoint | p50 | p95 | test |
|---|---|---|---|
| Profile | 1.14 s | 4.51 s | 40 requests per second |
| Profile and profile videos, 60/40 mix | 1.63 s | 6.87 s | 56 requests per second |
| Keyword search, pages 1 to 3 | 3.9 s | 8.9 s | 90 pages, one request at a time |
| Audience | about 37 s | 3 creators |
Caveats
- Under load past our running capacity, profile p95 rose to 23.6 s while more capacity started.
- Search was measured one request at a time. Its p95 includes a 2 s gap between pages.
- An endpoint with nothing running must start first, which took about 70 s for search.
- Followers and following are not live, so they are not measured.
Plan for the tail: set your client timeout above 180 seconds and run requests in parallel rather than in a long serial loop.