Is databricks-gemini-2-5-flash deprecated?

Q: Is databricks-gemini-2-5-flash deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2026-10-02, reported by a third-party catalog. The identifier still resolves today.

RETIRING IN 16 DAYS

Sunset scheduled for 2026-10-02, reported by a third-party catalog. The identifier still resolves today.

state=dying sunset=2026-10-02 days_remaining=16 severity=critical sources=litellm evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-16 03:02Z

databricks/databricks-gemini-2-5-flash

Vendor: databricks. Tracked by 1 of 5 sources.

What each source reports

**endpoint** = the provider's own machine-readable API, the strongest evidence. **provider docs** = the provider's own documentation, read by a model — first-party content, inferred reading. Unlabelled rows are third-party catalogs. Where sources disagree both values are shown rather than silently reconciled.
Source	ID	Context	Max out	In $/Mtok	Out $/Mtok	Sunset
litellm	databricks/databricks-gemini-2-5-flash	1,048,576	65,535	$0.30002	$2.49998	2026-10-02

Change history

Severity	Change	What	Detected
low	modified	databricks/databricks-gemini-2-5-flash: capabilities gained anthropic_thinking_payload	2026-09-13
critical	deprecated	databricks/databricks-gemini-2-5-flash: deprecation announced for 2026-10-02 — in 26 days	2026-09-06
critical	deprecated	databricks/databricks-gemini-2-5-flash: retires 2026-10-02 (in 26 days)	2026-09-06
low	modified	databricks/databricks-gemini-2-5-flash: capabilities gained prompt_caching	2026-08-26
info	repriced	databricks/databricks-gemini-2-5-flash: cache_read_price_per_mtok n/a to $0.03/Mtok	2026-08-26