When does the routing change for gemini-omni-1.1-flash take effect? (Not a shutdown)
According to Google Gemini API's page, last checked 2026-11-17, a change in routing for gemini-omni-1.1-flash takes effect on 3 December 2026 (2026-12-03); this is a change in routing, not a shutdown. Google Gemini API's stated replacement is "gemini-omni-1.2-flash".
Facts from the vendor page
| ID | gemini-omni-1.1-flash |
|---|---|
| Vendor | Google Gemini API |
| Kind | model: Gemini Omni Flash |
| Routing change date | (3 December 2026) |
| Stated replacement | gemini-omni-1.2-flash |
| Vendor note | Not an endpoint removal: effective December 3, 2026, the endpoint automatically routes API requests to gemini-omni-1.2-flash. |
| Source | Google Gemini API's page, read on |
See this entry in the full table · All Google Gemini API dates · All dates in December 2026
What to do
- Find where your code uses it: open the free checker with gemini-omni-1.1-flash filled in, then paste your own code or config. It runs in your browser and what you paste is never sent anywhere.
- If your code uses an alias instead of a dated or versioned ID, check the vendor page for what the alias will point to. Pin a dated or versioned ID where you need behaviour to stay the same.
- Test the stated replacement against your own cases before the date, and compare the results with what you get now.
- The vendor page is the authority, and dates can change. Open Google Gemini API's page before you act.
Other entries from Google Gemini API with dates near this one
The Migration pack ($9, one-time) puts every date in the table into your calendar and a check into your CI.