Requesty

Time to first token by provider · August 2026

Sference had the fastest median time to first token among major providers in August 2026 at 55 ms. The median major provider took 1.33 s.

Median and p90 time to first token, median total response time, and median output tokens per second, for streamed successful requests per provider.

Data through August 31, 2026Updated November 11, 2026
This is the permanent snapshot for August 2026. See the latest month (October 2026)

Median time to first token, August 2026

Source: Requesty production gateway
  • Sference55 ms
  • Alibaba200 ms
  • Nebius542 ms
  • OpenAI547 ms
  • Azure608 ms
  • DeepSeek857 ms
  • DeepInfra930 ms
  • Fireworks1.19 s
  • Vertex (Claude)1.33 s
  • TensorX1.35 s
  • Novita1.40 s
  • xAI1.47 s
  • Mistral1.55 s
  • Anthropic1.60 s
  • Bedrock1.74 s

Key findings

  1. 01Fastest median TTFT: Sference at 55 ms, then Alibaba at 200 ms.
  2. 02Highest median output speed: Vertex (Gemini) at 192 tokens per second.
  3. 03Fastest median full streamed response: Alibaba at 1.07 s.
  4. 04Novita moved the most since July 2026: median TTFT went from 3.71 s to 1.40 s (-2.31 s).

Median time to first token by month

0 ms939 ms1.88 s2.82 s3.76 sMay 26Jun 26Jul 26Aug 26Sference, Jul 26: 46 msSference, Aug 26: 55 msAlibaba, May 26: 424 msAlibaba, Jun 26: 2.04 sAlibaba, Jul 26: 1.78 sAlibaba, Aug 26: 200 msNebius, May 26: 819 msNebius, Jun 26: 928 msNebius, Jul 26: 463 msNebius, Aug 26: 542 msOpenAI, May 26: 2.33 sOpenAI, Jun 26: 3.48 sOpenAI, Jul 26: 923 msOpenAI, Aug 26: 547 msAzure, May 26: 548 msAzure, Jun 26: 618 msAzure, Jul 26: 689 msAzure, Aug 26: 608 msDeepSeek, May 26: 875 msDeepSeek, Jun 26: 847 msDeepSeek, Jul 26: 834 msDeepSeek, Aug 26: 857 ms
SferenceAlibabaNebiusOpenAIAzureDeepSeek

What changed since July 2026

  • Novita3.71 s → 1.40 s (-2.31 s)
  • Alibaba1.78 s → 200 ms (-1.58 s)
  • xAI970 ms → 1.47 s (+500 ms)
  • OpenAI923 ms → 547 ms (-376 ms)
  • Anthropic1.96 s → 1.60 s (-362 ms)

What to do about it

  • Compare providers on the same model in /rankings before switching. Provider medians mix many models.
  • If p90 matters more than the median, use latency-based routing across providers for the same model.

Latency routing sends each request to the provider that is currently fastest for that model.

Read about latency routing

Data

ProviderMedian TTFTp90 TTFTMedian totalMedian tokens/sStreamed shareOrganizations (band)
Sference55 ms142 ms1.80 s152.70074.24%500+
Alibaba200 ms4.54 s1.07 s110.20033.76%100-499
Nebius542 ms3.20 s2.22 s130.70023.46%500+
OpenAI547 ms4.31 s3.63 s69.90013.71%500+
Azure608 ms1.64 s1.98 s52.80054.69%500+
DeepSeek857 ms1.45 s9.21 s38.70050.46%500+
DeepInfra930 ms3.83 s3.19 s73.60027.53%500+
Fireworks1.19 s3.71 s4.67 s88.30034.53%500+
Vertex (Claude)1.33 s3.08 s5.80 s77.70044.49%500+
TensorX1.35 s5.31 s4.96 s80.20028.96%500+
Novita1.40 s2.95 s25.3 s13.10042.45%500+
xAI1.47 s3.40 s9.67 s44.6009.93%100-499
Mistral1.55 s10.4 s3.01 s117.80020.15%500+
Anthropic1.60 s3.37 s7.27 s59.60024.35%500+
Bedrock1.74 s3.30 s6.08 s80.40030.02%500+
Vertex (Gemini)1.94 s9.17 s3.91 s192.4005.08%500+
NVIDIA2.05 s14.0 s8.48 s60.70066.86%500+

17 rows published. Rows below the floors are withheld.

Questions this answers

Which LLM API has the lowest latency?
Sference had the fastest median time to first token among major providers in August 2026 at 55 ms. The median major provider took 1.33 s.
What is the median time to first token for LLM providers?
Sference had the fastest median time to first token among major providers in August 2026 at 55 ms. The median major provider took 1.33 s.
Which provider streams the most tokens per second?
Sference had the fastest median time to first token among major providers in August 2026 at 55 ms. The median major provider took 1.33 s.
How long does a full streamed LLM response take?
Sference had the fastest median time to first token among major providers in August 2026 at 55 ms. The median major provider took 1.33 s.

Method and definitions

  • Time to first token and tokens per second are measured on streamed, successful requests only, with the same formulas /rankings uses. Tokens per second counts visible output tokens after the first token, with a 250 ms floor on decode time and at least 20 output tokens.
  • A provider needs at least 500 streamed successes in the month for latency to be published. Only providers with at least 0.5% of published traffic are shown.
  • A row is published only when it has at least 20 requests, at least 5 distinct organizations, and no single organization above 80% of its traffic. These are the same floors /rankings uses. Rows below the floors are withheld, not estimated.
  • Only shares, rates, medians and organization bands are published. Absolute request, token and spend totals stay private.
TTFT:
Time from the gateway sending the request to the first streamed token from the provider.
p90:
90% of requests were faster than this.
Total:
Time from the gateway sending the request to the last streamed token.

Per-model numbers with the same definitions are on /rankings, refreshed weekly.

Caveats

  • Latency depends on the model mix. A provider serving mostly small models will look faster than one serving large reasoning models.
  • Reasoning models think before the first visible token, which raises TTFT.

Revision history and other months

Cite and reuse

Free to reuse under CC BY 4.0. Credit "Requesty Data" and link to this page. Cite the month URL so the numbers you quote stay fixed.

APA
Click to copy
BibTeX
Click to copy
CSV
Click to copy