diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt
index 90cc14258c5..c4ba2c00ff9 100644
--- a/src/content/cre/llms-full-go.txt
+++ b/src/content/cre/llms-full-go.txt
@@ -16573,7 +16573,7 @@ Last Updated: 2026-05-11
   sidebar to switch to the TypeScript version.
 </Aside>
 
-This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
+This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.
 
 The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.
 
diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt
index eb161e22acb..f63f5974f4d 100644
--- a/src/content/cre/llms-full-ts.txt
+++ b/src/content/cre/llms-full-ts.txt
@@ -16500,7 +16500,7 @@ Last Updated: 2026-05-11
   sidebar to switch to the Go version.
 </Aside>
 
-This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
+This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.
 
 The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.
 
diff --git a/src/content/cre/reference/clf-migration-go.mdx b/src/content/cre/reference/clf-migration-go.mdx
index 194a3a6eebb..58fff8472fa 100644
--- a/src/content/cre/reference/clf-migration-go.mdx
+++ b/src/content/cre/reference/clf-migration-go.mdx
@@ -17,7 +17,7 @@ import { Aside } from "@components"
   sidebar to switch to the TypeScript version.
 </Aside>
 
-This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
+This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.
 
 The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.
 
diff --git a/src/content/cre/reference/clf-migration-ts.mdx b/src/content/cre/reference/clf-migration-ts.mdx
index d09bae921f8..a8a3b782095 100644
--- a/src/content/cre/reference/clf-migration-ts.mdx
+++ b/src/content/cre/reference/clf-migration-ts.mdx
@@ -17,7 +17,7 @@ import { Aside } from "@components"
   sidebar to switch to the Go version.
 </Aside>
 
-This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **August 12, 2026**.
+This guide is for developers with production [Chainlink Functions (CLF)](/chainlink-functions) subscriptions migrating their requests to the [Chainlink Runtime Environment (CRE)](/cre) before mainnet shutdown on **September 1, 2026**.
 
 The majority of CLF use cases involve fetching off-chain data over HTTP and returning it to a consumer contract. That maps cleanly to a CRE workflow: a trigger (Cron, HTTP, or EVM Log) → an HTTP fetch → a signed report written on-chain to an `IReceiver` consumer.
 
diff --git a/src/features/chainlink-functions/common/cre-callout.mdx b/src/features/chainlink-functions/common/cre-callout.mdx
index 57b7854c50e..b9dc29a4cbe 100644
--- a/src/features/chainlink-functions/common/cre-callout.mdx
+++ b/src/features/chainlink-functions/common/cre-callout.mdx
@@ -1,8 +1,8 @@
 import { Aside } from "@components"
 
-<Aside type="caution" title="Chainlink Functions is shutting down on August 12, 2026">
-  Chainlink Functions will stop processing requests after **August 12, 2026**. Migrate your workflows to the
-  [Chainlink Runtime Environment (CRE)](/cre) before this date to avoid service interruption.
+<Aside type="caution" title="Chainlink Functions sunsets Sept 1, 2026 (testnet: June 2, 2026)">
+  Migrate to the [Chainlink Runtime Environment (CRE)](/cre), which does everything Functions does and [more →](/cre).
+  Migrate your existing subscriptions before these dates to avoid service disruption.
 
 See the [CLF to CRE migration guide](/cre/reference/clf-migration) for a full concept mapping and code examples.