Kimi K3
moonshotai/kimi-k3
Compare with Kimi K2.7 Code, Kimi K2.6, Kimi K2.5
Compare its 14 providers · Incident RSS
Showing only the digitalocean provider · show all 14
CompareKimi K3
| State | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
DigitalOceandigitalocean | Healthy | 99.87% | 99.34% | 99.30% | 99.30% | 3.13s | 41.7s | 22 tps | 1.0M | $2.85 / $14.25 |
- DigitalOcean99.87%Healthy24h 99.34%
- 7d
- 99.30%
- 30d
- 99.30%
- p50
- 3.13s
- p99
- 41.7s
- Throughput
- 22 tps
- Context
- 1.0M
- $/Mtok
- $2.85 / $14.25
digitalocean
Measured 3m ago. Latency and throughput are OpenRouter's rolling 30-minute windows.
Price history
Input $/Mtok
Step line — each recorded price holds until the next change.
Output $/Mtok
Step line — each recorded price holds until the next change.
History
Availability
Axis starts at 90% so small differences stay visible; it expands to 0 when an endpoint falls below.
Time to first token
Logarithmic axis — the fleet spans two orders of magnitude. P50 is OpenRouter's rolling 30-minute window.
Throughput
Median tokens per second.
Daily availability
Half a year, one cell per UTC day.
Feb
Mar
Apr
May
Jun
Jul
Aug
Mon
Wed
Fri
worst hour ≥ 95%90–95%< 90%no data
Colour by worst endpoint-hour of each UTC day · 3 days with data, 3 with at least one endpoint-hour below 90%.