# Gemini 3.7 and 3.5 Flash are auto-routed: see what answered

URL: https://infro.io/blog/gemini-3-7-and-3-5-flash-are-auto-routed-see-what-answered
Author: INFRO Editorial (https://infro.io/blog/editorial)
Publisher: INFRO
Published: 2026-10-31
Last modified: 2026-10-31
Last reviewed: 2026-10-31 (next review due 2026-11-30)
Topic: Routing and reliability
Format: Brief

> Google redirects gemini-3.7-flash to gemini-3.8-flash and gemini-3.5-flash to gemini-3.6-flash, so the model string in your code no longer says what answered [^changelog]. Compare requested and served model ids per request, watch output tokens and latency, and pin a replacement once you have tested it.

Key takeaways:
- On Oct 8, 2026 Google deprecated gemini-3.7-flash and gemini-3.5-flash, but both endpoints keep answering and are redirected to gemini-3.8-flash and gemini-3.6-flash.
- Your code, config and error rate can look unchanged while a different model answers, so log the requested and the served model id side by side.
- Google says 3.8 Flash can use more tokens on long, multi-step tasks, so check output tokens and latency before the cost forecast.
- Pin an explicit replacement for any workload with schema-sensitive output, a latency budget or a cost forecast, and let low-risk traffic follow the redirect.

## What Google changed on October 8

The October 8 release notes deprecate two models. `gemini-3.7-flash` is replaced by `gemini-3.8-flash`, and `gemini-3.5-flash` is replaced by `gemini-3.6-flash`. Both are no longer selectable in Google AI Studio, and API requests to the old names are routed automatically to the replacement.[1] The deprecation table says the same thing in other words: the endpoint is not shutting down, and it routes to the replacement.[2]

So there is no error and no 404, and no shutdown date to put in a calendar. Your code still sends `gemini-3.7-flash`, and a different model answers.

| You send | Google routes it to | Source |
| --- | --- | --- |
| `gemini-3.7-flash` | `gemini-3.8-flash` | Release notes, Oct 8[1] |
| `gemini-3.5-flash` | `gemini-3.6-flash` | Release notes, Oct 8[1] |

Table: Redirects as documented. The notes say to update the model string; for 3.5 Flash they name `gemini-3.8-flash` as an alternative to 3.6.

Google's 3.7 Flash guide now carries a deprecation caution at the top and describes the model as automatically routed to 3.8 Flash.[3]

## Detect which model answered

Treat the model string in your code as a request, not as evidence. Three places can tell you what was served.

1. **The response.** Log the model identifier your SDK returns next to the one you sent, and alert when they differ. The pages read here do not say whether a redirected response reports the requested or the served id, so test it with a few calls first. If it echoes your request, this check cannot see the redirect.
2. **Your gateway or request log.** A log that records the model per request lets you group by it. INFRO's request log records the model, the selected connection, timings, usage and estimated provider cost, and `GET /v1/requests` can sort by slowest or costliest.[4]
3. **Behaviour.** If ids are ambiguous, the redirect shows up as a step change in output tokens per request and in latency at the same timestamp.

```python
import logging

log = logging.getLogger("llm.model")

def check_served(requested: str, response) -> None:
    served = getattr(response, "model", None)
    if served is None:
        log.warning("no model id on response; requested=%s", requested)
    elif served != requested:
        log.warning("model differs: requested=%s served=%s", requested, served)
```

On INFRO, the traffic-changes finding "model answered by a new snapshot" fires when a model id the provider had not reported in the previous 14 days carries at least 20% of today's successful requests and at least 50 of them. It is evaluated per provider connection and needs 7 days of reported ids first.[5] It works from the ids the provider reports, so it shares the caveat above. It reads request metadata and not answers, so it cannot say whether quality changed.[5]

## What shifts when the redirect lands

**Output length.** Google says Gemini 3.8 Flash can use more tokens on longer, complex tasks by design: it takes smaller reasoning steps, calls tools iteratively and verifies its work. Its advice is to lower the reasoning effort for everyday tasks, or to use 3.6 Flash, which remains supported.[6] The default thinking level is medium.[6] INFRO's output-tokens signal fires on a rise of at least 15% and at least 20 tokens.[5]

**Latency.** More reasoning and more tool calls usually mean longer responses, though no latency figures were confirmed for this article. INFRO flags p95 latency or time to first token up at least 25% and at least 300 ms for two days running.[5] Check your timeouts and streaming deadlines against the new numbers.

**Cost.** Rates are the provider's list rates, billed by Google to your account. 3.6 Flash is listed at $1.50 per 1M input tokens and $7.50 per 1M output tokens, against $9.00 output for 3.5 Flash.[7] 3.8 Flash is $0.75 and $3.75 through December 31, 2026, then $1.50 and $7.50 from January 1, 2027.[6]

> **Example: Illustrative: the step-up on a redirected workload**
> Suppose a workload produces 100M output tokens a month on 3.8 Flash. At the introductory rate that is $375; at the January rate it is $750, before any change in tokens per request. The volume is made up; the rates are Google's list rates above. A 20% rise in output tokens per request adds 20% to each figure.

**Parameters.** Google's 3.6 guide says its models require removing the deprecated sampling parameters (`temperature`, `top_p`, `top_k`) and prefilled model turns.[7] The pages read do not say how the redirect treats a request that still sends them, so check your error rate and test one call that does.

## Pin a replacement or ride the redirect

Riding the redirect is fine for low-risk traffic: drafts, internal tools, anything without a strict schema or a latency budget. Pin when any of these is true:

- [ ] The output feeds a parser or a structured-output schema.
- [ ] You have a p95 or time-to-first-token budget.
- [ ] A cost forecast assumed the old model's tokens per request.
- [ ] You need the same model in staging and production.
- [ ] You want a change to happen when you approve it, not when Google moves a name.

Pinning means naming the replacement yourself: `gemini-3.6-flash` for 3.5 Flash traffic, `gemini-3.8-flash` or 3.6 Flash for 3.7 Flash traffic. Run the same prompts on both, compare output tokens, latency and your own quality checks, then switch. Pinning a model name does not freeze it forever; see [alias versus snapshot](https://infro.io/blog/model-aliases-vs-pinned-snapshots) for what a name can still do, and the [price-step article](https://infro.io/blog/gemini-price-doubling-re-forecast-before-1-december-and-1-january) before you forecast January.

## Questions

### Will gemini-3.7-flash or gemini-3.5-flash stop working?

Not on a stated date. Google's deprecation table lists no shutdown date for either, and says the endpoints are not shutting down and route automatically [2]. The same page warns that listed dates are the earliest possible and that exact dates come with advance notice.

### Does the redirect report the old or the new model name in the response?

The pages read for this article do not say. Send a handful of test requests, log the model identifier your SDK returns, and compare it with the model you sent before building detection on that field.

## Sources

1. Release notes (October 8, 2026 entries) — Google AI for Developers. https://ai.google.dev/gemini-api/docs/changelog (accessed 2026-10-31)
2. Gemini deprecations — Google AI for Developers. https://ai.google.dev/gemini-api/docs/deprecations (accessed 2026-10-31)
3. What's new in Gemini 3.7 Flash — Google AI for Developers. https://ai.google.dev/gemini-api/docs/whats-new-gemini-3.7 (accessed 2026-10-31)
4. Request traces — INFRO Docs. https://infro.io/docs/observability/traces (accessed 2026-10-31)
5. Traffic changes — INFRO Docs. https://infro.io/docs/observability/traffic-changes (accessed 2026-10-31)
6. What's new in Gemini 3.8 Flash — Google AI for Developers. https://ai.google.dev/gemini-api/docs/whats-new-gemini-3.8 (accessed 2026-10-31)
7. What's new in Gemini 3.6 Flash and 3.5 Flash-Lite — Google AI for Developers. https://ai.google.dev/gemini-api/docs/whats-new-gemini-3.6 (accessed 2026-10-31)