timetobail
My stack

Cloud SQL · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Cloud SQL for MySQL 8.0?

Time to Bail · Boarding pass

FromCloud SQL for MySQL 8.0
ToYour pick

Act. You can stay.

From January 1, 2027, MySQL 8.0 instances pay $0.07 per vCPU per hour extra. Upgrade to stop the fee.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Paid extended support starts
Time left
77days
Status
Act

Cloud SQL for MySQL 8.0 costs extra from January 1, 2027

Cloud SQL moves MySQL 8.0 into paid extended support on January 1, 2027, and PostgreSQL 14 on February 1, 2027. The fee is added per vCPU per hour.

What to do before January 1

Tick steps as you go. Your progress stays in this browser.

  1. List your instances and versions

    In the console, open Cloud SQL and check the database version of each instance and replica.

  2. Test a newer major version on a clone

    Make a clone, upgrade it and run your app against it first.

  3. Upgrade before the fee starts

    Upgrade MySQL 8.0 before January 1, 2027 and PostgreSQL 14 before February 1, 2027.

Facts we checked

Facts and their sources
Paid extended support startsJanuary 1, 2027[1]
VersionMySQL 8.0[1]
Extended support endsMySQL 8.0: July 1, 2029[1]
PostgreSQL alsoPostgreSQL 14 starts paid extended support February 1, 2027 (ends February 1, 2030)[1]
Who is enrolledAll instances on end-of-life MySQL and PostgreSQL major versions[1]
Extra fee in the first two years (Iowa)$0.07 per vCPU per hour[2]
Extra fee from the third year (Iowa)$0.14 per vCPU per hour[2]
High availability vCPUs, first two years$0.14 per vCPU per hour[2]
Committed use discountsDo not apply to extended support prices[2]
Read replicasCharged at the same rate as stand-alone instances[2]
PricesDepend on the region of the instance[2]
Instances still on MySQL 8.0Pay the extra fee from January 1, 2027[1]

Sources

Check it yourself. Every fact above links here.

  1. Cloud SQL database versions and version policies Google Cloud · primary · checked Oct 13
  2. Cloud SQL pricing Google Cloud · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Cloud SQL for MySQL 8.0? Act. You can stay. From January 1, 2027, MySQL 8.0 instances pay $0.07 per vCPU per hour extra. Upgrade to stop the fee.

On our scale this is Act: change a setting or plan before the date. You can stay.

Cloud SQL moves MySQL 8.0 into paid extended support on January 1, 2027, and PostgreSQL 14 on February 1, 2027. The fee is added per vCPU per hour.

Here are the facts we checked:

  • Paid extended support starts: January 1, 2027 (Google Cloud)
  • Version: MySQL 8.0 (Google Cloud)
  • Extended support ends: MySQL 8.0: July 1, 2029 (Google Cloud)
  • PostgreSQL also: PostgreSQL 14 starts paid extended support February 1, 2027 (ends February 1, 2030) (Google Cloud)
  • Who is enrolled: All instances on end-of-life MySQL and PostgreSQL major versions (Google Cloud)
  • Extra fee in the first two years (Iowa): $0.07 per vCPU per hour (Google Cloud)
  • Extra fee from the third year (Iowa): $0.14 per vCPU per hour (Google Cloud)
  • High availability vCPUs, first two years: $0.14 per vCPU per hour (Google Cloud)
  • Committed use discounts: Do not apply to extended support prices (Google Cloud)
  • Read replicas: Charged at the same rate as stand-alone instances (Google Cloud)
  • Prices: Depend on the region of the instance (Google Cloud)
  • Instances still on MySQL 8.0: Pay the extra fee from January 1, 2027 (Google Cloud)

You can stay on Cloud SQL. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Google Cloud is the main source for this page. Cloud SQL has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Instances still on MySQL 8.0: Pay the extra fee from January 1, 2027.

The date to remember is January 1, 2027. Make the change before then.

What to do before January 1

  1. List your instances and versions. In the console, open Cloud SQL and check the database version of each instance and replica.
  2. Test a newer major version on a clone. Make a clone, upgrade it and run your app against it first.
  3. Upgrade before the fee starts. Upgrade MySQL 8.0 before January 1, 2027 and PostgreSQL 14 before February 1, 2027.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Cloud SQL for MySQL 8.0 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product