Kimi K2 & Kimi K3 Series Deprecation, Shutdown Dates & Migration Guide
Runs locally in your browser — 0 bytes uploaded
Synced 2026-11-12 UTC · 23 variants · 3 ecosystems
Track confirmed UTC deprecation and shutdown dates for Kimi K2 & Kimi K3 Series (Moonshot AI) across AWS Bedrock, Azure OpenAI, Moonshot AI. Preview kimi-k2-0905-preview → kimi-k3 upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.
Tracked Variants
23
Earliest Upcoming EOL
2027-01-26
Recommended Upgrade
kimi-k3
Ecosystems Covered
AWS Bedrock, Azure OpenAI, Moonshot AI
1. Quick .env & SDK Snippet Replacement Matcher
Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.
Replacement Diff Preview (kimi-k2-0905-preview → kimi-k3)
# MOONSHOT_MODEL: kimi-k2-0905-preview -> kimi-k3 [RETIRED]
- MOONSHOT_MODEL="kimi-k2-0905-preview"
+ MOONSHOT_MODEL="kimi-k3"
# AZURE_OPENAI_DEPLOYMENT: Kimi-K2.5 -> kimi-k3.1-pro [DEPRECATED · EOL 2027-01-26]
- AZURE_OPENAI_DEPLOYMENT="Kimi-K2.5"
+ AZURE_OPENAI_DEPLOYMENT="kimi-k3.1-pro"2. Cross-Ecosystem Kimi K2 & Kimi K3 Series Lifecycle Matrix (23)
Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.
| Model ID | Provider | Calculated Status | Confirmed Shutdown (UTC) | Vendor Lifecycle | Replacement & Migration | Source |
|---|---|---|---|---|---|---|
Kimi-K2.5 |
Azure OpenAI | DEPRECATED (75d) | 2027-01-26in 75d | Preview | Docs ↗ | |
moonshot.kimi-k2-thinking |
AWS Bedrock(Moonshot AI) | DEPRECATED (138d) | 2027-03-30in 138d | LegacyDep: 2026-09-30ap-northeast-1, ap-south-1, ap-southeast-2, sa-east-1, us-east-1, us-east-2, us-west-2 | Docs ↗ | |
moonshotai.kimi-k2-thinking |
AWS Bedrock(Moonshot AI) | DEPRECATED (138d) | 2027-03-30in 138d | LegacyDep: 2026-09-30ap-northeast-1, ap-south-1, ap-southeast-2, sa-east-1, us-east-1, us-east-2, us-west-2 | Docs ↗ | |
Kimi-K2.6 (2026-04-20) |
Azure OpenAI | DEPRECATED (155d) | 2027-04-16in 155d | Preview | Docs ↗ | |
Kimi-K2.7-Code (2026-06-12) |
Azure OpenAI | DEPRECATED (155d) | 2027-04-16in 155d | Preview | Docs ↗ | |
Kimi-K3.1-Pro (2026-11-04) |
Azure OpenAI | DEPRECATED (357d) | 2027-11-04in 357d | GA | Docs ↗ | |
kimi-k2.6 |
Moonshot AI | DEPRECATED | Not announced | DeprecatedDep: 2026-11-01 | Docs ↗ | |
kimi-k2.7-code |
Moonshot AI | DEPRECATED | Not announced | DeprecatedDep: 2026-11-01 | Docs ↗ | |
kimi-k2.7-code-highspeed |
Moonshot AI | DEPRECATED | Not announced | DeprecatedDep: 2026-11-01 | Docs ↗ | |
kimi-k2-0711-preview |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-k2-0905-preview |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-k2-thinking |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-k2-thinking-turbo |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-k2-turbo-preview |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-k2.5 |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-latest |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
kimi-thinking-preview |
Moonshot AI | RETIRED | Not announced | Retired | Docs ↗ | |
moonshotai.kimi-k2.5 |
AWS Bedrock(Moonshot AI) | ACTIVE | No EOL | Active | — | — |
moonshotai.kimi-k3 |
AWS Bedrock(Moonshot AI) | ACTIVE | No EOL | Active | — | — |
moonshotai.kimi-k3.1 |
AWS Bedrock(Moonshot AI) | ACTIVE | No EOL | Active | — | — |
kimi-k3 |
Moonshot AI | ACTIVE | No EOL | Active | — | — |
kimi-k3.1-pro |
Moonshot AI | ACTIVE | No EOL | Active | — | — |
kimi-k3.1-pro-highspeed |
Moonshot AI | ACTIVE | No EOL | Active | — | — |
AWS Bedrock regional scope applies across 7 tracked regions (ap-northeast-1, ap-south-1, ap-southeast-2, sa-east-1, us-east-1, us-east-2); verify regional inference prefixes (us., eu., apac., global.) before cutover.
3. Production Migration Checklist (kimi-k2-0905-preview → kimi-k3)
Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:
- Inventory pinned model IDs: Search repositories and deployment manifests for
MOONSHOT_MODEL,moonshot/LiteLLM routes, and dated snapshot strings in the Kimi K2 & Kimi K3 Series family (9 deprecated, 8 retired, 6 active variants tracked). - Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against
kimi-k3, then compare input, output, and cached token rates in DevToken. - Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated Kimi K2 & Kimi K3 Series identifiers cannot re-enter production.
4. Related Moonshot AI & Ecosystem Migration Guides
Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:
GPT-4o mini
DEPRECATED (63d)GPT-4o
DEPRECATED (63d)GPT-4.1 & GPT-4.1 mini / nano
DEPRECATED (63d)GPT-4 Turbo
RETIREDGPT-4 (0613 / 32k / Vision)
RETIRED5. Kimi K2 & Kimi K3 Series Deprecation & Upgrade FAQ
Is Kimi K2 & Kimi K3 Series deprecated or retired across AWS Bedrock, Azure OpenAI, Moonshot AI?
LLMEOL tracks 23 Kimi K2 & Kimi K3 Series variants across AWS Bedrock, Azure OpenAI, Moonshot AI: 9 deprecated with scheduled shutdowns, 8 retired past their UTC EOL date, and 6 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.
What is the recommended replacement model when migrating off kimi-k2-0905-preview?
The primary recommended upgrade target for kimi-k2-0905-preview is kimi-k3. Always test prompt formatting, max output tokens, and tool schemas on kimi-k3, and compare token pricing in DevToken before switching production traffic.
How can I replace kimi-k2-0905-preview in .env and LiteLLM configs safely?
Paste your MOONSHOT_MODEL assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.