Requesty

Time to first token by provider · June 2026

Azure had the fastest median time to first token among major providers in June 2026 at 618 ms. The median major provider took 1.49 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 June 30, 2026Updated November 11, 2026
This is the permanent snapshot for June 2026. See the latest month (October 2026)

Median time to first token, June 2026

Source: Requesty production gateway
  • Azure618 ms
  • DeepSeek847 ms
  • Vertex (Claude)1.25 s
  • xAI1.29 s
  • Mistral1.35 s
  • Fireworks1.36 s
  • DeepInfra1.62 s
  • Anthropic1.96 s
  • Novita1.97 s
  • Bedrock2.07 s
  • Vertex (Gemini)2.63 s
  • OpenAI3.48 s

Key findings

  1. 01Fastest median TTFT: Azure at 618 ms, then DeepSeek at 847 ms.
  2. 02Highest median output speed: Vertex (Gemini) at 154 tokens per second.
  3. 03Fastest median full streamed response: Azure at 1.15 s.
  4. 04OpenAI moved the most since May 2026: median TTFT went from 2.33 s to 3.48 s (+1.15 s).

Median time to first token by month

0 ms368 ms737 ms1.10 s1.47 sMay 26Jun 26Azure, May 26: 548 msAzure, Jun 26: 618 msDeepSeek, May 26: 875 msDeepSeek, Jun 26: 847 msVertex (Claude), May 26: 1.14 sVertex (Claude), Jun 26: 1.25 sxAI, May 26: 899 msxAI, Jun 26: 1.29 sMistral, May 26: 861 msMistral, Jun 26: 1.35 sFireworks, May 26: 1.33 sFireworks, Jun 26: 1.36 s
AzureDeepSeekVertex (Claude)xAIMistralFireworks

What changed since May 2026

  • OpenAI2.33 s → 3.48 s (+1.15 s)
  • Novita2.40 s → 1.97 s (-424 ms)
  • xAI899 ms → 1.29 s (+395 ms)
  • DeepInfra1.24 s → 1.62 s (+375 ms)
  • Bedrock2.39 s → 2.07 s (-319 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)
Azure618 ms1.61 s1.15 s90.40073.26%100-499
DeepSeek847 ms1.50 s5.17 s46.50014.72%100-499
Vertex (Claude)1.25 s2.99 s4.76 s88.00071.03%100-499
xAI1.29 s6.73 s10.9 s30.2009.09%100-499
Mistral1.35 s8.69 s3.36 s76.40016.87%100-499
Fireworks1.36 s6.91 s5.04 s112.20082.50%100-499
DeepInfra1.62 s6.73 s8.86 s26.80014.49%100-499
Anthropic1.96 s3.64 s6.24 s80.50055.09%500+
Novita1.97 s4.93 s8.69 s42.4004.06%100-499
Bedrock2.07 s6.43 s5.92 s85.30033.48%500+
Vertex (Gemini)2.63 s15.0 s3.39 s154.3007.02%500+
OpenAI3.48 s15.3 s5.82 s104.1008.21%500+

12 rows published. Rows below the floors are withheld.

Questions this answers

Which LLM API has the lowest latency?
Azure had the fastest median time to first token among major providers in June 2026 at 618 ms. The median major provider took 1.49 s.
What is the median time to first token for LLM providers?
Azure had the fastest median time to first token among major providers in June 2026 at 618 ms. The median major provider took 1.49 s.
Which provider streams the most tokens per second?
Azure had the fastest median time to first token among major providers in June 2026 at 618 ms. The median major provider took 1.49 s.
How long does a full streamed LLM response take?
Azure had the fastest median time to first token among major providers in June 2026 at 618 ms. The median major provider took 1.49 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