Z.ai: GLM 5 Performance
TrustedRouter performance signals and provider route posture for Z.ai: GLM 5.
z-ai/glm-5
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 5. 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 |
|---|---|---|---|---|---|---|---|
venice
|
2241 ms | 3141 ms | 2241 ms | — | 100.00% | — | 3 |
gmi
|
2549 ms | 3299 ms | 2549 ms | — | 100.00% | 1 unsupported_route |
3 |
zai
|
2618 ms | 3643 ms | 2618 ms | — | 100.00% | — | 2 |
atlas-cloud
|
— | — | — | — | 0.00% | — | 1 |
digitalocean
|
— | — | — | — | 0.00% | — | 3 |
Full provider & model leaderboard.
13 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.