diff --git a/docs/api/rpc/introduction.md b/docs/api/rpc/introduction.md
index 2a98d7bbbb..ba81f8e54f 100644
--- a/docs/api/rpc/introduction.md
+++ b/docs/api/rpc/introduction.md
@@ -18,6 +18,8 @@ There are multiple [RPC providers which you can choose from](./providers.md). Th
 
 ## Node Snapshots
 
+⚠️ **FREE SNAPSHOT SERVICE BY FASTNEAR WILL BE DEPRECATGED STARTING JUNE 1ST, 2025. We strongly recommend all node operators to use [Epoch Sync](https://near-nodes.io/intro/node-epoch-sync) when possible.**
+
 If you're looking for node snapshots  in order to set up a validator node or RPC, you can download the latest NEAR blockchain state from:
 
 - [Allnodes](https://www.publicnode.com/snapshots#near)
diff --git a/docs/data-infrastructure/lake-framework/running-near-lake/run-near-lake.md b/docs/data-infrastructure/lake-framework/running-near-lake/run-near-lake.md
index 61cd055c1c..09cb8f70a7 100644
--- a/docs/data-infrastructure/lake-framework/running-near-lake/run-near-lake.md
+++ b/docs/data-infrastructure/lake-framework/running-near-lake/run-near-lake.md
@@ -100,33 +100,9 @@ After the network is synced, you should see logs of every block height currently
 Whenever you run NEAR Lake for any network except localnet you'll need to sync with the network.
 This is required because it's a natural behavior of `nearcore` node and NEAR Lake is a wrapper
 for the regular `nearcore` node. In order to work and index the data your node must be synced
-with the network. This process can take a while, so we suggest to download a fresh backup of
-the `data` folder and put it in you `--home-dir` of your choice (by default it is `~/.near`)
+with the network. 
 
-:::tip
-Running your NEAR Lake node on top of a backup data will reduce the time of syncing process
-because your node will download only the data after the backup was cut and it takes reasonable amount time.
-:::
-
-All the backups can be downloaded from the public S3 bucket which contains latest daily snapshots:
-
-You will need [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html) to be installed in order to download the backups.
-
-### Mainnet
-
-```
-$ aws s3 --no-sign-request cp s3://near-protocol-public/backups/mainnet/rpc/latest .
-$ LATEST=$(cat latest)
-$ aws s3 --no-sign-request cp --no-sign-request --recursive s3://near-protocol-public/backups/mainnet/rpc/$LATEST ~/.near/data
-```
-
-### Testnet
-
-```
-$ aws s3 --no-sign-request cp s3://near-protocol-public/backups/testnet/rpc/latest .
-$ LATEST=$(cat latest)
-$ aws s3 --no-sign-request cp --no-sign-request --recursive s3://near-protocol-public/backups/testnet/rpc/$LATEST ~/.near/data
-```
+While snapshot-based syncing was previously the recommended default, we now recommend [Epoch Sync](https://near-nodes.io/intro/node-epoch-sync) —a faster, more lightweight method that allows a node to catch up from genesis without downloading a large state snapshot.
 
 ## Running NEAR Lake as an archival node
 
@@ -152,7 +128,7 @@ The syncing process in archival mode can take a lot of time, so it's better to d
 and put it in your `data` folder. After that your node will download only the data after the backup was cut and it
 takes reasonable amount time.
 
-All the backups can be downloaded from the public [S3 bucket](https://near-nodes.io/intro/node-data-snapshots) which contains the latest daily snapshots.
+All the backups can be downloaded from the public [S3 bucket](https://docs.fastnear.com/docs/snapshots/mainnet#archival-mainnet-snapshot) provided by FastNEAR.
 
 See [this link](https://near-nodes.io/archival/run-archival-node-with-nearup) for reference
 
diff --git a/docs/protocol/network/networks.md b/docs/protocol/network/networks.md
index 42c70c589e..cd0e96b3be 100644
--- a/docs/protocol/network/networks.md
+++ b/docs/protocol/network/networks.md
@@ -17,7 +17,7 @@ NEAR Protocol operates on several networks each operating with their own indepen
 - Status: `https://rpc.mainnet.near.org/status`
 - [ [NearBlocks Explorer](https://nearblocks.io) ]
 - [ [Wallet](https://wallet.near.org) ]
-- [ [Data Snapshots](https://near-nodes.io/intro/node-data-snapshots) ]
+- [ [Epoch Sync](https://near-nodes.io/intro/node-epoch-sync) ]
 
 ## Testnet {#testnet}
 
@@ -26,7 +26,7 @@ NEAR Protocol operates on several networks each operating with their own indepen
 - Status: `https://rpc.testnet.near.org/status`
 - [ [Explorer](https://testnet.nearblocks.io) ]
 - [ [Wallet](https://testnet.mynearwallet.com/) ]
-- [ [Data Snapshots](https://near-nodes.io/intro/node-data-snapshots) ]
+- [ [Epoch Sync](https://near-nodes.io/intro/node-epoch-sync) ]
 
 ## Localnet {#localnet}