diff --git a/apps/app-handover-guide.html.md b/apps/app-handover-guide.html.md
index 8687731903..c7b7ff5571 100644
--- a/apps/app-handover-guide.html.md
+++ b/apps/app-handover-guide.html.md
@@ -51,7 +51,6 @@ or go to the App Settings page in your Dashboard, click Move app, pick the new o
     - **Postgres** **(unmanaged and managed):** Moving Postgres databases across orgs is not supported. You’ll need to spin up a new Fly Postgres app in the target org and restore from a volume snapshot. Or you can use `pgloader` to migrate the data. 
     - **Upstash Redis:** This is tied to an org’s private network. You’ll need to provision a new DB in the new org. 
     - **Tigris buckets:** You’ll have to delete the old Tigris bucket, recreate it in the new org, and copy the data over (try `s3sync`). Don’t forget to reset your app’s secrets. 
-    - **Sentry and other extensions**: Be sure to create fresh ones in the new org and reconfigure the app to use them.
 
 ### Summary
 
diff --git a/blueprints/cell-based.html.md b/blueprints/cell-based.html.md
index 7700190cf6..ab99fbb04c 100644
--- a/blueprints/cell-based.html.md
+++ b/blueprints/cell-based.html.md
@@ -220,8 +220,7 @@ likely make use of one or more of the following:
    addresses many problems, it doesn't help deal with logs that are missing due
    to application or network problems.  Consider having applications emit a
    heartbeat, and write monitoring software that looks for missing heartbeats
-   and reports them as issues.  [Sentry](https://fly.io/docs/monitoring/sentry/)
-   can help here.
+   and reports them as issues.
  * While applying updates when all of the services for a single Machine are
    self contained is an easier problem then upgrading potentially
    interdependent services running live in production, it does come at a cost:
diff --git a/getting-started/migrate-from-heroku.html.md b/getting-started/migrate-from-heroku.html.md
index a2cb73c55a..7c9845bf2c 100644
--- a/getting-started/migrate-from-heroku.html.md
+++ b/getting-started/migrate-from-heroku.html.md
@@ -307,7 +307,7 @@ Once DNS propagates, Fly automatically provisions an SSL certificate.
 | Heroku Scheduler | Use cron in your app, or a separate "cron" process |
 | Papertrail | `fly logs` built-in, or add a log drain |
 | SendGrid | Keep using SendGrid (just use API key) |
-| New Relic | `fly extensions sentry` or keep using New Relic |
+| New Relic | Keep using New Relic (just use license key) |
 | S3 / Bucketeer | `fly storage create` (Tigris) or keep using S3 |
 | Elasticsearch | Deploy Elasticsearch as a Fly app, or use a hosted service |
 | Memcached | Use Redis instead (`fly redis create`) |
diff --git a/monitoring/sentry.html.md b/monitoring/sentry.html.md
index 40cf7e6d1c..37c5f2bc60 100644
--- a/monitoring/sentry.html.md
+++ b/monitoring/sentry.html.md
@@ -6,23 +6,15 @@ redirect_from: /docs/reference/sentry/
 date: 2025-07-21
 ---
 
-[Sentry](https://sentry.io/) is a developer-first application monitoring platform that helps you identify and fix software problems before they impact your users. Through our partnership with Sentry, each of your Fly organizations can claim a year’s worth of [Team Plan](https://sentry.io/pricing) credits.
-
-## Set up Sentry for your Fly.io app
-
-In your project source directory, run the following command:
-
-```
-fly ext sentry create
-```
+<div class="warning icon">
+**Heads up**: Provisioning new Sentry projects through Fly.io (`fly ext sentry create`) is no longer available. Existing projects keep working, and this page sticks around for the people using them. Need error tracking on a new app? [Sign up with Sentry directly](https://sentry.io/signup/) and set your `SENTRY_DSN` as an app secret.
+</div>
 
-This command will:
+[Sentry](https://sentry.io/) is a developer-first application monitoring platform that helps you identify and fix software problems before they impact your users. Through our former partnership with Sentry, organizations that provisioned Sentry through Fly.io received a year’s worth of [Team Plan](https://sentry.io/pricing) credits.
 
-- Create a Sentry account using your Fly.io user email
-- Create a Sentry organization linked to your Fly.io organization
-- Set the `SENTRY_DSN` secret in your app
+## Access your Sentry project
 
-Once this is complete, your app will have the `SENTRY_DSN` environment variable available at runtime. Most Sentry SDKs will automatically pick this up and begin sending events.
+Apps provisioned through Fly.io have the `SENTRY_DSN` secret set, so the environment variable is available at runtime. Most Sentry SDKs will automatically pick this up and begin sending events.
 
 You can open the Sentry dashboard for your app by running:
 
@@ -36,7 +28,7 @@ To start sending events to Sentry, you’ll need to instrument your app with the
 
 ## Sentry Plan details
 
-Your organization receives one year of Sentry’s Team plan, which includes monthly:
+Your organization received one year of Sentry’s Team plan, which includes monthly:
 
 - 50k errors
 - 100k [performance units](https://sentry.io/changelog/2023-5-9-introducing-performance-units/)
diff --git a/security/org-roles-permissions.html.md b/security/org-roles-permissions.html.md
index 34d2eeb6c6..aa3e14d0b4 100644
--- a/security/org-roles-permissions.html.md
+++ b/security/org-roles-permissions.html.md
@@ -32,7 +32,7 @@ Admins have all the permissions of Members, plus a few critical ones:
 
 Use the admin role sparingly. Admins can burn the place down—on purpose or by accident.
 
-**Note**: For billing and user permission details for our extension partners (e.g. Tigris, Sentry, etc.) please check with the vendor directly.
+**Note**: For billing and user permission details for our extension partners (e.g. Tigris) please check with the vendor directly.
 
 ### Quick Comparison