Description

## Motivation Currently the **peer.decentraland.org** domain receives more than **2x** the amount of HTTP requests than the actual Load Balancer at **peer-lb.decentraland.org** (in charge of distributing the traffic across the catalyst network). This is caused by several external services targeting directly this server URL and not leveraging the catalyst network. As a result if there is a problem with this node, all services depending on it and consuming data from there will face problems too and, on the other hand, this node is using a lot of extra resources in order to respond to those requests. ### HTTP requests qty in 1 week received by Host - January 2022 | Host | Requests | | -------------------------------------------- | ---------------------- | | peer.decentraland.org | 160.89M | | peer-lb.decentraland.org | 75.5M | | peer-eu1.decentraland.org | 20.39M | | peer-ap1.decentraland.org | 15.35M | | peer-wc1.decentraland.org | 11.39 | ## Proposal - Change the current Catalyst server domain name from **peer.decentraland.org** to **peer-ec2.decentraland.org**. - Make **peer.decentraland.org** be the Load Balancer while also keeping **peer-lb.decentraland.org** (as DNS CNAME). These 2 Domains will distribute the requests in the Catalysts network. ## Impact - Everything will keep working as it is. - The change will be transparent, no updates will be required in external services or apps - Higher Availability and Security for any App depending on the Catalysts Servers - All services hitting **peer.decentraland.org** will end up leveraging the decentralized network, avoiding potential failures - When doing an HTTP request to **peer.decentraland.org** or **peer-lb.decentraland.org**, the request will be distributed across the Catalyst Servers - The Catalyst with the new domain name **peer-ec2.decentraland.org** will receive an equitative amount of HTTP requests, releasing a lot of HW resources from that node and with that it will better serve the users connected to it.