Z.ai: GLM 4.6 Performance
Compare measured TTFT, TTFB, throughput, uptime, and route health for Z.ai: GLM 4.6 across TrustedRouter providers using metadata-only production probes.
z-ai/glm-4.6
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), time-to-first-byte (TTFB), effective throughput, and success rate for Z.ai: GLM 4.6. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime, and no prompt or output content is stored.
| Provider | p50 TTFT | p95 TTFT | p50 TTFB | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|---|
| atlas-cloud | 1364 ms | 2042 ms | 1364 ms | — | 100.00% | — | 2 |
| deepinfra | 1511 ms | 2834 ms | 1511 ms | — | 100.00% | — | 2 |
| venice | 2211 ms | 3431 ms | 2211 ms | — | 100.00% | — | 5 |
| zai | 3522 ms | 3942 ms | 3521 ms | — | 100.00% | — | 4 |
Full provider & model leaderboard.
7 routes.
More routes give the auto router more room to fail over around provider 429 and 5xx responses.
Gateway overhead is measured separately.
Public status separates TLS/health overhead from full model latency so slow LLMs do not inflate the router metric.
Metadata rollups.
Status samples store latency, outcome, provider, model, route, cost, and region metadata only.
View public status or inspect provider routes.