diff --git a/apps/www/_blog/2023-04-14-supabase-studio-2.0.mdx b/apps/www/_blog/2023-04-14-supabase-studio-2.0.mdx
index 54a253ffa75..9c13bb1b8a0 100644
--- a/apps/www/_blog/2023-04-14-supabase-studio-2.0.mdx
+++ b/apps/www/_blog/2023-04-14-supabase-studio-2.0.mdx
@@ -23,7 +23,6 @@ Here's the birds-eye-view:
   <li>[**Foreign key Selector**](#item-one): look up a row in reference table</li>
   <li>[**Postgres Roles**](#item-one): manage your Postgres roles and privileges</li>
   <li>[**Database Webhooks**](#item-one): database triggers for Edge Functions</li>
-  <li>[**Network Restrictions**](#item-one): Block access from specified IP ranges</li>
   <li>[**Table/View definitions**](#item-one): View SQL definitions for tables and views</li>
   <li>[**API Autodocs**](#item-one): view auto-generated docs right from the Table Editor</li>
   <li>[**Support for many tables**](#item-one): Table Editor now supports 1000s of tables</li>
@@ -125,12 +124,6 @@ The Roles page got a huge revision, making it easy for you to manage access cont
 
 We've wanted to improve the webhooks interface for a long time, and we've finally gotten to it. We now have full support for editing your webhooks, and you can now select an edge function to call instead of having to pass in a url. We're happy to roll this very common request out to the community.
 
-## Network Restrictions
-
-[need a screenshot]
-
-A new add-on for you to configure restrictions on the IP ranges that are allowed to connect to your Postgres database. With network restrictions, you're able to control exactly who has access to your data. Read more in the Docs.
-
 ## Table/View definitions
 
 ![Logs UI](/images/blog/lw7-studio/definitions.png)